Alchemy Translations

* SOURCE TEXT CHECKBOXES
* TRANSLATION GUIDELINES
* MOST FREQUENT ERRORS IN MT OUTPUT
* WEBAPP GUIDELINES
* GENERAL QUALITY GUIDELINES
* QUALITY CRITERIA
* VIEW PERFORMANCE AND COUNTER-FEEDBACK

AIM: populate a Machine Translation engine for ISAAC. You will perform Machine Translation Post-Editing (MTPE) of content into multiple languages and this will be used to train an MT engine and produce automatic translations.
TASK DESCRIPTION: this task provides both a source and a suggested target. Source cannot be edited. The resulting translation must be accurate, fluent, and read naturally in the target language. Avoid literal translations. Read your new target sentence on its own and double check that it sounds as though a native speaker said/wrote that sentence.
TARGET LANGUAGES: the only target languages requested and allowed in this project are the ones listed below. Make sure you translate into the correct target language and flavor (example: Latin American Spanish is not allowed, Canadian French is not allowed, etc.)

CHEATING BEHAVIORS: cheating behaviors are strictly prohibited and will be punished with immediate removal/ban from the project. The affected wordcount and the additional cost of the rework will be deducted from the PO. Examples include (but are not limited to):

- DO NOT use Machine Translation (no matter if edited or not) or any other input from MT engines (like Google Translate, Bing Translator, Deepl, etc.) to provide translations. All edits should come from human translators.
- DO NOT translate into the wrong target language (for example, do not translate into South American Spanish as the project only has Spain Spanish as target language).
- DO NOT use any kind of script, automation, browser add-in, or other third-party tools.
- DO NOT retain the source and/or the target for translation memory purposes or any other use case.
- DO NOT apply random nonsensical changes to the MT just for the sake of editing it. For example in cases where the translation differs just in capitalization, or punctuation, or in a synonym, or when the translation contains the explanation of the source content, etc.
- DO NOT apply unreasonable omissions (like translating only the first part of the sentence)
- DO NOT mark error categories during review without fixing the translation. If there is an error, you must both select the error category and fix the target.

ANY OTHER cheating behavior from other circumstances or scenarios not explicitly mentioned here that may jeopardize the project and the cooperation with the customer is also extremely prohibited.
FINAL EXPECTED QUALITY: HUMAN QUALITY. Translated strings should retain the meaning of the source and express it as fluently as possible, as a native speaker of the target language would do.
TEAM MEMBERS: Translations will be provided by native speakers of target language who are fluent in source language and will be accurate and in compliance with the project translation Guidelines below.
CONTENT: general news, newspapers, instant messages or comments in social networks, strings extracted from news programs, medical publications, finance, and business documents, or concerning sports, travel, shopping, etc. Sometimes, the customer will attach context for reference. If available, this will be visible in the webapp. Otherwise, assume there is no further reference or context than the string itself. Focus on each string individually, and do not try to find how the strings are related with one another; probably, they are not related at all.

NEXT TOPIC ⇒ SOURCE TEXT CHECKBOXES