Differences

This shows you the differences between two versions of the page.

--- isaac_project:en:human_translation_instructions_v311:3_translation_guidelines [2023/11/15 13:34]
sergio
+++ isaac_project:en:human_translation_instructions_v311:3_translation_guidelines [2023/11/15 14:43] (current)
sergio
@@ Line 131: / Line 131: @@
 spelling errors. Spell checker is integrated in Oneforma and available directly in the webapp.
 To launch the check, click on this button in each string you want to check:
+{{ :isaac_project:en:human_translation_instructions_v311:img5_translation_guidelines.jpg?400 |}}
+__**GENDER**__: if the source sentence has a specific gender, it should be translated into the
+same gender in the target. If the source language doesn't support a specific gender and you
+need to choose one in the target language, for e.g. pronouns when translating from English
+into German, Spanish etc., choose a random gender. Do not always choose male or female. \\
+__**STYLE AND FORMALITY**__: if the source sentence contains a level of formality, try to
+replicate the same level of formality/politeness in the target unless this would be perceived
+as unnatural by the target audience. If the source sentence does not provide a level of
+formality (e.g. English), translate with an informal style by default, unless this would be
+perceived as unnatural by the target audience (like in Japanese, where formal is the more
+accepted form). \\
+__**POLITE WORDS**__: if using ‘polite’ words (like 'please') is not common or expected in the
+target, please omit them (this should not be considered an Omission error during review).
+SWEAR WORDS/VULGAR CONTENT: do not omit any parts of the source content and
+do not change the original tone of the sentence. If source contains swear words, politically
+incorrect expressions, vulgar comments, etc. please keep it in target as well by conveying
+the same meaning and tone. If you do not feel comfortable with the content of the string and
+do not want to translate it, feel free to skip the hit. \\
+__**NUMBERS**__: keep numbers as is (keep the “same style”). That means written-out numbers in the source should be translated into written-out numbers in the target and Arabic numerals (123) in the source should be transferred as Arabic numerals (123) in the target. Please stick to this rule even if it might be unusual/rare in the target
+language. Examples: \\
+▪ 123 → 123 \\
+▪ two plus two equals four → zwei plus zwei ist gleich vier \\
+__**THOUSAND/DECIMAL SEPARATOR**__: any formatting of the numbers, for e.g thousand and decimal separators needs to be modified to fit the target language. For example, given English to German translation, “123,000” should be translated to “123.000”. \\
+__**DATES**__: dates need to be formatted based on the target language but remaining close to
+the source format as much as possible. For example, given English to French translation,
+“02/10/2015” should be translated to “10/02/2015”. \\
+__**TIME**__: time indication/hours need to be formatted based on the target language but
+remaining close to the source format as much as possible. For example, given English to
+Italian translation, “5:30 PM” should be translated to “17:30”. \\
+__**CURRENCIES**__: currency names should be translated (not converted). For example, given
+English to Spanish translation, “8000 crowns” would be “8000 coronas”. “18 dollars” would
+be “18 dólares”. \\
+__**UNITS OF MEASUREMENT**__: **Never convert** units even if the target language uses
+different metric systems. Translation with converted units are not acceptable. Example: 75
+Fahrenheit should not change into 25 Celsius (75 F should be translated to 75 F). 6 inches
+should not change into 15.24 cm. \\
+__**SYMBOLS**__: symbols can be switched if one variant is more common in the target language.
+For example, given English to German translation, “$125 dinner” might be translated to “125
+USD Abendessen”. \\
+__**FORMATTING**__: The format of the source text should be maintained in the target languages
+unless target language has a pre-defined syntax. Example: “123” should be translated as
+“123” and not as “one hundred and twenty-three”. Example: “I am so happy!!!!!!!!!” should be
+translated by maintaining the same number of “!” in the target. \\
+__**PUNCTUATION AND CAPITALIZATION**__: preserve source punctuation/capitalization as
+much as possible (especially if the content is informal, like in chats, social media posts, etc.),
+consistent with common usages in the target language. For example, if the source sentence
+includes several question marks, explanation marks, dots etc. please copy this punctuation
+as is into the target. If the source sentence starts lowercase, do not start the target sentence
+uppercase. Please note that if the source has enough intentional punctuation, correct any
+incorrect or missing ones. \\
+{{ :isaac_project:en:human_translation_instructions_v311:img6_translation_guidelines.jpg?600 |}}
+However, some punctuation/capitalization adjustments may be needed in the target
+language for those cases where the source contains symbols that do not exist in the target
+or other grammar restraints. \\
+**Note**: be sure to type symbols such as quotation marks (e.g. “ ”) using the target language
+keyboard set. Avoid typing using other keyboard set that is not the target language one
+because this can lead to inconsistencies. \\
+{{ :isaac_project:en:human_translation_instructions_v311:img7_translation_guidelines.jpg?600 |}}
+__**EXCEPTION**__: when the source is clearly FORMAL, you should modify and adapt the
+punctuation to what is expected in the target language. Although most of the times we do not
+have the context of the strings, you can sometimes assume the nature of the source by the
+content, the style or the language used in it.  \\
+{{ :isaac_project:en:human_translation_instructions_v311:img8_translation_guidelines.jpg?600 |}}
+In case of doubts, if the source is ambiguous and you cannot clearly tell whether it’s
+formal/informal, please assume it is informal and preserve source punctuation/capitalization
+as much as possible. \\
+__**MENTIONS AND HASHTAGS**__: keep @mentions and #hashtags as in source. Example: I
+don't like @PapaJohn pizza #cardboard #evil → no me gusta la pizza de @PapaJohn
+#cardboard #evil \\
+__**CODE & TECHNICAL TEXT**__: links , html tags, development code, text usually in English
+wrapped with <>, {}, [] or other type of coding language should not be translated. The
+checkbox “garbled text” should be marked in these cases. Example: “<head>” “{top:-
+px;position:absolute;right }”, “xmlHttp.open("GET", true)”, etc. Additionally, there are other
+instances of text referring to a UI, a code, or an instruction where it does not need to be
+translated.  \\
+__**Example**__: text STOP to stop receiving message → translate everything except the word,
+“STOP” because this is a text message instruction where the word needs to be texted as is
+for the service to work correctly. \\
+__**TAGS**__: You might encounter tags (words surrounded by brackets) in the source text:
+[redacted_name], [redacted_address], [redacted_email], [redacted_id], [redacted_number],
+[redacted_url], [redacted_words], etc. You should treat tags as substitutes for the described
+word or phrase, and translate them according to the context. The tag should be present in
+the translation as it is; you should NOT translate tag contents. \\
+__Gendered articles__: Please note that some languages might require gendered articles before
+some tags, like the address tag. Please do not include a gendered article before the tag, you
+should treat the tag as if the gendered articles were included inside the tag. \\
+{{ :isaac_project:en:human_translation_instructions_v311:img9_translation_guidelines.jpg?400 |}}
+__**EMOJIS**__: copy emojis directly from source into the target. Do not change them, even if they
+are incomplete (like :-‘). If the source sentence uses an emoji to replace a word that is
+essential to the sentence meaning, then translate with the inferred word (without omitting the
+emoji). Example: “The is red” should be translated like if it were “The apple is red”. \\
+__**BUSINESS AND PRODUCT NAMES**__: keep business names and product names as-is
+with proper capitalization. Examples: Facebook → Facebook, ebay → eBay. Exception: if a
+company/product has been officially marketed in another country under a different name,
+you should use the official name for the target country. Examples: “Diet Coke” would be
+“Coca-Cola Light” in Italian; “Algida” would be “Frigo”, “Miko”, or “Eskimo” depending on the
+target country.  \\
+__**PROPER NAMES**__: proper names of people should NOT be changed unless they are
+historical names widely recognized in each language. Example: Columbus > Colón.
+Transliteration can be used as long as the names are the same as in source. Example for
+Serbian: "Shakespeare" > "Šekspir". Other names (e.g. names of places and languages)
+should be translated when the name is rendered differently in the source and target
+languages. For example, Warsaw in Polish should be Warszawa, Cologne in German should
+be Köln and Spain in Spanish should be España. \\
+__**APP NAMES**__: keep well known app names as in source if there is no official translation.
+Example: Skype → Skype \\
+__**NAMES OF LAWS, ACTS, ORGANIZATIONS**__: keep as in source the names of laws,
+acts, organizations, etc. that belong to a specific country. Example:  'Defense of Marriage
+Act'. For international organizations or international documents, i.e., 'Universal Declaration of
+Human Rights', please use the standard and approved translations for the target. \\
+__**MOVIE/BOOK/SONG/SHOW TITLES**__: if there is no official/culturally relevant translation
+for the title, keep the one in the source. If there is an official translation or adaptation that is
+more familiar to the target locale, please use that one. Example: “Harry Potter and the
+Philosopher’s Stone” should be translated into French as “Harry Potter à l'école des
+sorciers” because that was the title of the French version of the same book. “Twinkle,
+twinkle, little star” might be translated into Korean using the corresponding Korean-language
+song “반짝 반짝 작은 별”. \\
+__**QUERIES**__: If you have linguistic queries or doubts about the instructions, raise a ticket to
+our Query Management System Global Query (C837-Isaac projects) by selecting “HT” under
+the Isaac scope field. Do not raise tickets in Global Query for non-linguistic topics. If you
+have queries about workflow, rates, payments, or want to report a technical bug (not related
+to linguistic issues), reach out by email to the PMs. If you do not have an account or you
+cannot remember your username, reach out to the PMs by email. If you don’t remember the
+password, you can reset it from the login page. All answers provided outside this tool and by
+third parties/companies are neither official nor reliable for this project. \\
+NEXT TOPIC => [[isaac_project:en:human_translation_instructions_v311:4_webapp_guidelines|WEBAPP GUIDELINES]]

Alchemy Translations

User Tools

Site Tools

Differences

Page Tools