Differences

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

--- isaac_project:en:mtpe:mtpe_full_instructions:contents:1_t_guide [2023/11/20 15:45]
sergio created
+++ isaac_project:en:mtpe:mtpe_full_instructions:contents:1_t_guide [2023/12/18 12:56] (current)
sergio
@@ Line 1: / Line 1: @@
+==== TRANSLATION GUIDELINES  ====
 **INCOMPLETE/TRUNCATED STRINGS**: if a string is incomplete in source, do not try to
 complete it in target; translate the part that appears in source with what would be the
@@ Line 76: / Line 79: @@
 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:mtpe:mtpe_full_instructions:contents:img5_isaac_project_mtpe_full_instructions.jpg |}}
+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:mtpe:mtpe_full_instructions:contents:img6_isaac_project_mtpe_full_instructions.jpg |}}
+**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:mtpe:mtpe_full_instructions:contents:img7_isaac_project_mtpe_full_instructions.jpg |}}
+{{ :isaac_project:en:mtpe:mtpe_full_instructions:contents:img8_isaac_project_mtpe_full_instructions.jpg |}}
+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:mtpe:mtpe_full_instructions:contents:img9_isaac_project_mtpe_full_instructions.jpg |}}
+**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).\\
+{{ :isaac_project:en:mtpe:mtpe_full_instructions:contents:img10_isaac_project_mtpe_full_instructions.jpg |}}
+**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 “반짝 반짝 작은 별”. \\
+**2 TRANSLATIONS REQUIRED**: for MTPE, we typically require one translation per
+source string. However, some batches/files will require two translations for each source
+string. if 2 translations are required: \\
+• They will be paid individually (if you provide both Translation1 and Translation2
+for the same source string, the source string will be paid twice). \\
+• Translation1 needs to be the most common. \\
+• It will be mandatory to provide 2 valid different translations of the same source
+string. Both translations need to maintain the original intent using different words,
+structures, and expressions, which means that Translation1 cannot be the same
+as or very similar to Translation2. Make every attempt to provide a good diversity
+in Translation2 and not just change the articles or other minor changes. Example:  \\
+o T1: I’m Ralf. \\
+o //T2 (valid): My name is Ralf// \\
+o T2 (not valid): I am Ralf \\
+• This diversity can come from using a different level of formality, translate into two
+sentences with different meanings (if the source text is ambiguous), use
+synonyms in the second translation or rephrase the sentence (syntactic
+difference). Please take all these possibilities for providing diversity into account
+and combine them. Do not always use the same criteria (for example do not
+always rephrase). Don't try to add a new translation from a different variant such
+as Swiss German for German (this would be a cheating behavior for wrong target
+language). __Hints and tips on how to provide valid 2nd translations are posted in
+the below section.__ \\
+• Centific will conduct checks to detect how similar Translation1 and Translation2
+are. If there is an indication that Translation1 and Translation2 are the same or
+too similar (only minimum variations applied), it will be considered a cheating
+behavior. \\
+• There are cases where it is not possible to provide a valid Translation2, and in
+these cases Translation2 should be omitted. For example when the source is
+made just by:  \\
+o a number or a price \\
+o a URL \\
+o an email address \\
+o a proper name \\
+o etc. \\
+• If only Translation1 has been provided, Centific will conduct checks to detect if the
+lack of Translation2 is justified. If there is an indication that the lack of Translation2 is
+not justified, the user who missed to translate it will be penalized in the QA. \\
+• If the task requires 2 translations but it is not possible to provide a valid Translation2,
+click the **SECOND TRANSLATION NOT POSSIBLE** button. This will indicate to the
+reviewers that there is only 1 possible translation for the provided source. \\
+**TIPS ABOUT 2ND TRANSLATIONS**: The 2nd translations should be considerably
+different. It’s not just a matter of changing the articles or the punctuation. You should really
+find a different way to say the same (without of course doing mistranslations, omissions,
+etc.). Please find here some tips about how to reach this diversity in the 2nd translations. \\
+•** Different levels of FORMALITY**: Due to their nature, some strings should have
+either an informal or a formal tone. For example, business reports will usually be
+formal, tweets will usually be informal. Vulgar and offensive contents will more likely
+have an informal tone too. This perception may change from language to language
+and the gold rule is to always avoid using a level of formality that would be
+unnatural in the context of the sentence for your language. However, if the source
+context is ambiguous enough to let you play with different levels of formality, you
+can use this to vary Translation1 from Translation2. For example:\\
+o Translation1: Votre enfant va impatiemment se rendre sur le site Internet
+www.loremipsum.com  \\
+o Translation2: Ton gamin s’éclatera sur www.loremipsum.com \\
+• **Different meaning for AMBIGUOUS sources**: Sometimes the source text is
+ambiguous and can be interpreted in different ways. You can use Translation1 and
+Translation2 to provide 2 different possible meanings of the same ambiguous
+source string. For example: \\
+o Source: Fred previously checked on this with the gas desk because Aquila
+indicated interest in buying out this contract. \\
+Here it is not clear whether “Fred” and “Aquila” are two people or two companies, so
+you can: \\
+o T1: translate as if they were both people names \\
+o T2: translate as if they were both company names \\
+• Different SINTAXES: Use different syntactic structures in Translation1 and
+Translation2. This doesn’t only mean change the word order, but literally using
+different grammar/syntactic structures. For example: \\
+o T1: I wish you all the best on your birthday \\
+o T2: Wishing you a happy birthday \\
+o T1: Quería saber si te gustaría ir a ver “American Beauty” con nosotros un
+día de estos \\
+o T2: ¿Te apetecería ir a ver con nosotros “American Beauty” algún día? \\
+• **Different TERMINOLOGY**: Terminology between Translation1 and Translation2
+can be changed, but please make sure you don’t change just one word, otherwise
+they would be too similar. For example: \\
+o Source: Manual coffee crafting competition (Atlanta) \\
+o T1: Gara di preparazione manuale del caffè (Atlanta) \\
+o T2: Competizione di Atlanta su come fare il caffè a mano \\
+• **Different GENDERS**: If the source language doesn't support a specific gender and
+it’s ambiguous, please use different genders for Translation1 and Translation2. For
+example: \\
+o Source: You are really funny. \\
+o T1: Sei molto simpatica. → This is feminine \\
+o T2: Ti trovo davvero simpatico. → This is masculine \\
+**UNACCEPTABLE 2ND TRANSLATIONS**: Examples of unacceptable 2nd translations,
+that will be considered cheating behaviors, include (but are not limited to):
+{{ :isaac_project:en:mtpe:mtpe_full_instructions:contents:img11_isaac_project_mtpe_full_instructions.jpg |}}
+**AMBIGUOUS/UNCLEAR SOURCE**: if the context is clear, keep the same meaning as
+source. But if the meaning of the source is ambiguous and the context is not clear, try
+searching the exact snippets in the Web to find a possible context or meaning. If there is no
+way to clarify the meaning, provide a translation based on your best judgment, even word by
+word if needed. If the project allows 2 translations for the same source, you can use them to
+put 2 different interpretations of the source. Do not mark the source as nonsensical if you
+can apply the phrase into a context where the words make sense. For example, “Rat” can be
+translated referring to the animal in Translation1 and with the meaning of “traitor” in
+Translation2. \\
+{{ :isaac_project:en:mtpe:mtpe_full_instructions:contents:img12_isaac_project_mtpe_full_instructions.jpg |}}
+**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 “MTPE”
+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:mtpe:mtpe_full_instructions:contents:2_most_errors|MOST FREQUENT ERRORS IN MT OUTPUT]]
+BACK TO => [[isaac_project:en:mtpe:mtpe_full_instructions:contents|MACHINE TRANSLATION POSTEDITING (MTPE) TRANSLATION v.3.1]]

Alchemy Translations

User Tools

Site Tools

Differences

Page Tools