Alchemy Translations

Open https://desk.oneforma.com/index.php
Use the login and password from your Project Manager to sing in.

Before taking the task, please note:

1. Make sure to carefully refer to the Style Guides and instructions for Human Translation.
2. The source will require two translations.
3. Slang language should be localized appropriately into the target language.
4. In the target text, please keep the emoji and special marks same as those in the source text.
5. Please follow the instructions to translate the names.
6. Do not add comments or use () to add annotations..
7. Translations should be accurate and following idiomatic and grammatical rules in Target Language.
8. Please beware of typos and make sure you follow the spellchecker before delivering any string.
9. Kindly avoid the use of line breaks in the translated text.
   

IMPORTANT: If you detect any misbehavior in the tool (i.e. spelling checker not working, slowness, emojis not present in source, source blank), please report us immediately. Your support and communication is very important for this task.

Instructions for the translation stage
o Once you receive your account details and log in OneForma, Please check and make sure the hit name of the WebApp and the number are matches what you can see.

Then click on Actions > START

1. The source will require two translations. This is one of the main changes. Although the project requires two translations you will only see one textbox so the same hit can be translated by two different resources. The first time you translate a hit you will have the following layout:

So you just need to provide the translation in the Proposed translation textbox.

If you translate a sentence that has been previously translated by another resource or by yourself (because you can translate one sentence and after some time get the same source to translate), you will see the following layout:

In this case the Translation from first translator will be blocked and can only be used for reference. You need to provide a second translation in the Proposed Translation textbox.

Following with the general guidelines it’s forbidden to provide an identical second translation: you won’t be able to submit it and you’ll get a pop-up message warning about it.

2. Two new radio buttons have been added next to the usual option “The source is not in the expected language”.

If you doubt or for some reason cannot translate the hit, you can skip the line. In this case, you should indicate one of the reasons at the top:

• The source string is not in the expected language
• The source string is not translatable
• Bad source: completely nonsensical. If you click this option, you need to provide a translation word by word. Otherwise, you won’t be able to submit the string.
• Bad source: completely garbled. If you click this option, the translation textbox will become grey and you won’t be able to provide a translation. You will just need to click submit. You will need to use this button whenever you have sequence like “sdkdjgbvsdhnfkjgbesf” that has no sense at all. If you have just symbols, emojis… please do not click this option. You need to write them in Translation 1 exactly the same as source and leave the translation 2 in blank

Futher instructions how to use radio buttons, please read here: HOW TO USE RADIO BUTTONS

3. 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.

4. 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.

–> Next topic –> ISAAC_MTPE - How to translate on Oneforma