Full Document Translation and QA

This task will be performed in the Full_Document_Translation_SourceToTarget * Webapp. Just click on QA Actions > START. Let us know if you have problems finding it:

• Please click “Guideline” button on webapp to read the guideline carefully.
• The purpose of reviewing includes:
  1. Make the translation correct. Please don’t just correct a simple error in existing translation, please review each translation carefully.
  2. Select the error category correctly and fairly.
  3. Make sure the domain is correct.
• When reviewing, reviewers need to take the context into consideration according to the CONTEXT part in the Instruction(P3-P4).
• Gender disambiguation: you should correctly disambiguate the gender of entities like pronouns based on the words/phrases they refer to.
• Abbreviation disambiguation: if an abbreviation referring to previous words/phrases in the context does not have a correspondence in the target language, you should expand it.
• Omission (ellipsis): some languages omit words/phrases that can be inferred from the context. Depending on the target language, these omitted words/phrases need to be explicitly stated, which requires inferring them from the context.
• Discourse connectives: correctly translate discourse structures connected by discourse connectives.
• Consistency (lexical cohesion): translate different occurrences of words and phrases consistently e.g.names and expressions.
• Sense disambiguation (polysemy): words/phrases with multiple meanings should be disambiguated to the correct sense based on the context.
• Speaker linguistic context (Deixis): use context to correctly translate words whose interpretation depends on the linguistic context indicating the speaker identity, place or time.
• Paragraph Structure: The paragraph structure of the source extract should be preserved in the translation. For example, if the source consists of two paragraphs, the translation should be, too. Sentence Structure within each paragraph can be adapted as appropriate so the translation forms a natural coherent unit with well-defined structure, keeping the meaning of the source.

IMPORTANT: This is the layout you will face when entering the webapp. You need to revise the entire segment. You will have detailed information in the guidelines.

In case you are sure the text cannot be revised, click on “Source can’t be Translated” and a pop-up message with the following radio buttons will appear. You will need to select all the options why the source cannot be translated.

• A. The source string is not in the expected language: This checkbox should be used for all cases where the source string is in the wrong language.
• B. Bad source: completely garbled: You will need to mark this button whenever you have sequence like “sdkdjgbvsdhnfkjgbesf” that has no sense at all.
• C. Bad source: completely nonsensical: Use this option when the text is composed by real word but have no sense altogether, like “to it see done if three use”.
• D. Source does not form a coherent unit with well-defined structure: Use this button when the structure of the text to translate is not coherent. Find further information in the examples section of the guidelines.

In addition, when you click on submit, another pop-up message appears, and you can select one of the two following options if applicable to that particular hit:

• A. Source has typos or spelling errors: This checkbox should be used in all cases where the source contains typos or spelling mistakes that are clearly unintentional. Translate the sentence as you would normally do and correct any errors you see from the source in your translation, since your translation must be free of typos/spelling mistakes.
• B. Source is missing context: This box should be marked when the source still has ambiguous word(s) and need more context in order to provide an accurate translation.

In case you face a hit with content you do not feel comfortable with or if it is too advanced in a particular topic for you to translate it confidently, please kindly click on “SKIP HIT”.

IMPORTANT: In case you find any hit that has some empty content, please check if the reason is because the hit is marked as “nonsensical” or “non-coherent”. If that is the case, it is important if the linguists in charge of the QA can first do a check on the text in case the original translator was wrong. If you believe it is not translatable as well, please submit as is (do not skip the hit, just submit it). If you believe it makes sense and that it can be translated, please skip it and let us know the Hit ID so it will be returned the content to the translation pool and will be reworked.

Please keep in mind that Machine Translation usage is strictly forbidden, and its use will result in removal from the project and lack of payment.

It is absolutely forbidden to work with more than one OneForma tab opened in the browser. The system will detect this practice and penalize the user. Failure to follow this rule may lead to serious issues in the final file and penalizations. Only one tab can be open at the same time.

Our expected review productivity for QA is 850 words per hour. It’s not a mandatory requirement. But if your productivity is very low, we will have to remove you from the review team.

Please ensure, that you've completed all certifications to get access to the project:

• Translation_Certification_Guidance _Source_TO_Target *
• ISAAC_LanguageProficiencyTest_Grammar_EN-US
• ISAAC_LanguageProficiencyTest_Reading_EN-US
• ISAAC_LanguageProficiencyTest_Grammar_Target
• ISAAC_LanguageProficiencyTest_Reading_Target

* Source stays for source language
* Target stays for target language

How to find Certifications

Full Document Translation v.2.1
Specific Language conventions
Payment information

In case of linguistic doubts or questions about the linguistic instructions, do not hesitate to contact your Project Manager.