Human Translation Guideline

In this task, you will be providing translations from a source string into a specific language variant.
It is important that you are native in the target language and fluent in the source language.

A high quality translation must be carried through by delivering the intent of the source text, using
language that is natural, grammatically correct and polished formatting.

You are not allowed to use Machine Translation(Google, Papago, Bing,...etc) since this project is an
HT(Human Translation) project. Use of Machine Translation or high similarities between submitted
translations and Machine Translations may serve as grounds for immediate termination of contract.

In this task, two translations per a source string are required.

When two translations are required, the first must be the most common wording and the second must be
a variation of the first that is more than just re-ordering of words or minor differences.

(You should fill in both columns: translation1 and 2.

However, in case there is no possible second translation that would be fairly common wording, leaving
translation 2 column blank of 10% or less of source sentences in each file is permitted.)

In this task, make sure that the marks and emojis in the translated text should be the same as in
the source text.
Additional marks and explanations in the translated string that are not in the source string are
NOT accepted.

Please mark the following checkboxes if there are any of the options applied to the source string:

● Source string is not in the expected language: Mark this checkbox when the source is in a
language rather than the expected one(translation is not required).

● Source is garbled: Mark this checkbox when the source is totally garbled, - such as
“klñafjgljkalkjoriajtljalkgtjaljg”- and translation is not possible at all.

● Source is nonsensical: Mark this checkbox when the source makes no sense but a word-by-
word translation can be provided(translation is required).

● Source has typos or spelling errors: Mark this checkbox when the context has typo but
translation can be provided(translation is required).

*You don’t have to distinguish the options for errors strictly. Just select one error type per a
source string which looks most appropriate.
*If you can translate the original text word-by-word, even if it looks a little awkward in the whole
string, you can proceed with the translation without selecting the error type.
* For two cases translation is not required, ( “source string is not in the expected language”,
“source is garbled”) payment will not be made.

You can refer to the examples of incorrect errors’ selection below.

MTPE Guideline

MTPE: Machine Translation Post Editing

This task is for post-editing, which is the process whereby humans amend machine-generated translation
to achieve an acceptable final product. It is important that you are native in the target language and fluent
in the source language.

This task provides both source strings and machine-translated target strings. You are expected to edit the
machine-translated target strings for accuracy and fluency.

We plan to conduct similarity verification, and may request revisions if the similarity level compared to
machine-generated translation is too high. Therefore, even if the machine translation is good, please
paraphrase it in your own words.
Please edit each MT sentence, unless it is too short to be expressed differently.

MT Post Editing Standards

● For phrases with fewer than 5 words, a minimum of 25% modification is required.
● For phrases with 5 or more words, a minimum of 90% modification is required.

For example, if there are 500 source strings with five or more words in one batch, at least 450 MT strings
have to be post edited.

:
In this task, make sure that the marks and emojis in the translated text should be the same as in
the source text.
Additional marks and explanations in the translated string that are not in the source string are
NOT accepted.

Please mark the following checkboxes if there are any of the options applied to the source string:

● Source string is not in the expected language: Mark this checkbox when the source is in a
language rather than the expected one(translation is not required).

● Source is garbled: Mark this checkbox when the source is totally garbled, - such as
“klñafjgljkalkjoriajtljalkgtjaljg”- and translation is not possible at all.

● Source is nonsensical: Mark this checkbox when the source makes no sense but a word-by-
word translation can be provided(translation is required).

● Source has typos or spelling errors: Mark this checkbox when the context has typo but
translation can be provided(translation is required).

*You don’t have to distinguish the options for errors strictly. Just select one error type per a
source string which looks most appropriate.
* For two cases translation is not required, ( “source string is not in the expected language”,
“source is garbled”) payment will not be made.

*If you can translate the original text word-by-word, even if it looks a little awkward in the whole string, you
can proceed with the translation without selecting the error type.
General Translation Guidelines and Examples
* The General Translation Guidelines apply to both Human Translation Tasks and MTPE
Tasks.

This section provides our general translation guidelines. These might undergo revisions from time to
time. In addition, specific batches/files that are to be translated might come with amendments to these
generic guidelines.

1. Meaning of Second Translation

This point only applies to tasks with a second translation.

The first translation should be a translation with the most commonly used expressions.
The second translation should use different expressions by rephrasing the first translation's sentence
order or expressions so that the meaning of the original can be conveyed.
Make every attempt to provide a meaningful diversity in second translation and not just change the
articles or other minor changes.
If two translations are almost identical with only slight word changes ,just like the example below, it is hard
to say it is a second translation.
eg. you are → you're or The fox → A fox are not meaningfully diverse.

For diversity in translation, the following methods can be used:

● In the second translation, you can use synonyms or make grammatical differences to write the
translation differently.
● Please write in various ways other than using synonyms.
○ e.g. Acceptable translations would look like:
Translation 1: “Marca is really dumb”
Translation 2: “Marca is so stupid”
2. Language Variants
Don't add a new translation from a different variant to the expected target such as Swiss German
(de_CH) for German (de_DE).

● Christmas tree → 圣诞树 - correct for Chinese (China Mainland, zh_CN)

● Christmas tree → 耶誕树 - this translation is only used in Taiwan or Hong Kong.

● Bicycle → 自行车 - correct for Chinese (China Mainland, zh_CN)

● Bicycle → 脚踏車 - this translation is only used in Taiwan

*Do not mix Simplified Chinese and Traditional Chinese.

3. Consistent Format
The format of the text should be consistent across source and target languages unless the target
language has a pre-defined syntax. See also the section “Names and numbers”.
● 123 → 123 (O) / one hundred and twenty-three (X)

4. Synonyms / Different meanings / Polysemic Words

A word may be either a verb or noun in the target language and/or have different meanings. Try to
use the most common meaning if a source word / phrase has multiple meanings.

● (EN) Rat→ (ZH) Tr 1: 鼠 / Tr 2: 叛徒

● (ES) Rata → (EN) Tr 1: rat / Tr 2: penny pincher

In the first example above, 'Rat' has two meanings, 1. Mouse( 小人) 2. Traitor, but "mouse" as an animal is more
commonly used.
Likewise, For words with multiple meanings, please write the most commonly used meaning in the
Translation 1 Column.
5. Known Entities
Popular entities should be formatted as they are branded in the region of the target language.

● America's Got Talent → translated as the TV show and not the phrase itself.
→ (JA) アメリカズ・ゴット・タレント
→ (ZH) 美国达人秀
● United Nations (UN)
→ (KO) 국제연합 (유엔)
→ (JA) 国際連合(国連)
→ (ZH) 联合国
→ (Es) Naciones Unidas (NU)

Translate business names / Apple product names as-is with proper capitalization.

(transliteration is needed when it is possible)

● Facebook / facebook

→ (EN) Facebook

→ (JA) フェイスブック

→ (ZH) 脸书
● ebay / eBay

→ (EN) eBay

→ (JA) イーベ

→ (ZH) 易贝

App names / podcasts / song titles / other media: Keep well-known brand names in the most common
language if there is no accepted translation

● Skype → Skype

If there is not a culturally relevant movie title / podcast title translation, keep the original source text. Song
lyrics/titles: If there is an adaptation that is more familiar to the target locale translate it.

● twinkle, twinkle, little star

→ (KO) 반짝 반짝 작은 별
 → (ZH) 一闪一闪小星星

→ (JA) キラキラ星

→ (ES) Estrellita, ¿dónde estás?

6. Retain the meaning of the source sentence in the translated version, and use the
context of the original source sentence.

Provide more a translation of the meaning rather than a “word by word” style translation. Depending on
the context a bag in German can be “eine Tasche” or “eine Tüte” (a paper/plastic bag) → please use the
translation expected from the context.

7. Unclear text
If the meaning is clear (despite minor grammatical/spelling issues), we would still appreciate a
translation. Along with this translation, please check the option, “Source has typos or spelling errors”.

The source data will likely have misspellings and abbreviations. Leave the source text as is but for the
translations try to fix any misspellings and disambiguate abbreviations
● nighkmare → (ES) pesadilla
● how r u → (ES) cómo estás
● (ES) perrrito → puppy
● (ES) ¿Para k quieres saber eso? → Why are you curious about that?

If something like “finger of fish love” is not clear, please try to provide a word for word translation and
check the “Source is nonsensical” option. If a word for word translation is impossible, skip the task.

If the input text is completely in another language (not the announced source language) please skip
this sentence (do not translate) and mark “Source string is not in the expected language”.

8. Style and Formality General Guidelines

Translate using informal language by default i.e. as if you are writing a Tweet.
However, if the source sentence contains a level of formality, please try to carry over the
formality/politeness level from source to target language.
 1) When Source Sentence Contains a Level of Formality

- Some languages (e.g. French, Spanish, German) have some levels of formality based on
the audience (politeness). If the source sentence contains a level of formality, please try
to carry over the formality/politeness level from source to target language.

2) NOTE

- Do not use the level of formality which would be unnatural in the context of the sentence.
- Use informal language for vulgar or offensive content.
● I love your ass → translate it in an informal way, for example “deinen” instead of
“Ihren” in German

3) When Source Sentence Does Not Provide a Level of Formality

- If the source sentence does not provide a level of formality (e.g. English) please
translate with an informal style by default. Polite/Formal language can be used only in
cases where it is more appropriate for the given source sentence in the specific context.
- If using ‘polite’ words is not common or expected, it’s fine to omit them. e.g. “please”.

9. Gender
1) If the source sentence has a specific gender,
- it should be translated into the same gender in the target language.

2) If the source language doesn't support a specific gender,

- you need to choose one in the target language, for e.g pronouns in English → German/Spanish, choose a
random gender. Don't always choose male or female.

● I’m glad → (ES) Estoy contenta

● I’m tired → (ES) Estoy cansado

10. Numbers
1) keep numbers as is (keep the “same style”).
- This means written-out numbers in the source sentence should be translated into written-out
numbers in the target language and Arabic numerals in the source sentence can be transferred
as Arabic numerals to the target sentence.
● 123 → 123

- Please stick to this rule even if it might be unusual/rare to use written-out numbers instead of
Arabic numerals in the target language.
● two plus two equals four
→ (DE) zwei plus zwei ist gleich vier

→ (ES) dos más dos son cuatro

2) Number Formats
- Any formatting of the numbers, for e.g thousand separators can be modified to fit the target
language.
● English → German, “123,000” should be translated to “123.000”.

3) Dates Formats

- Dates can be formatted based on the target language but remaining close to the source format as

possible.

● English → French/Spanish, “02/10/2015” should be translated to “10/02/2015”.

4) Currency Symbols

- Symbols can be converted providing any quantities do not change.

● $125 Dinner → (DE) 125 $ Abendessen or 125 USD Abendessen.

5) Weights & Measures

- Don’t convert units even if the target language uses different metric systems.
● 6 inches → 15.24cm(X), 6 inch(O)
● 75 Fahrenheit → 25℃ (X), 75℉ (O)
11. Proper Names
ONLY localize names, places, et al when they are appropriate to localize.

1) Personal Names

-Transliteration(translation by sound) is needed when it is possible.

● Chris had a meal

→ (ES) Chris comió

→ (ZH) 克里斯吃饭了

2) Location / City Names

-It can be appropriate to localize location / city names.

● I went to Italy last week

→ (DE) Ich war in Italien letzte Woche

→ (ZH) 我上星期去意大利了

● I live in New York

→ (ES) Vivo en Nueva York

12. Punctuation and capitalization

1) Punctuation Marks
- Preserve all punctuation as much as possible. If the source sentence includes several question
marks, exclamation marks, dots etc. please copy this punctuation as is into the target.
● Hello..... → (ES) Hola…..

- However, if the punctuation in the target language is different from that of the source sentence
, please follow the punctuation of the target language.
● How are you? → ES) ¿Cómo estás?
● Period of English (.) → period of Chinese (。)

The title of the book : 《》 is used in Chinese.

example
 The author of "The True Story of Ah Q" is Lu Xun.

→ (ZH) 《阿 Q 正传》的作者是鲁迅。

2) Emojis
- Please copy over emojis directly into the translations.
● I love this game �� → me encanta este juego ��
● pretty fun :) → muy divertido :)
● My 🏚️is red →Mi 🏚️es roja.
- Please copy incomplete emojis into the translations as well.
● Wer Lust hat soll mir einfach schreiben :- → If you feel like it, just write me :-

3) Capitalization

For general punctuation, use judgment based on the context.

- If the source is clearly multiple sentences and sounds very formal, it makes sense there to use
capital letters where appropriate and include periods or question marks.
- If the source has enough intentional punctuation, correct any incorrect or missing ones.
- However, if the text is very casual with a lot of emojis or context appropriate for social media,
adding in proper punctuation would not be ideal, including capitalization.
- Less formal text should not have capitalization fixed, since it can be a person’s style to omit
them.

13. Idioms
A literal word-by-word translation of an idiom is not acceptable if the meaning of the source string gets
lost. In this context, some idioms can be especially challenging to translate, and a literal word-by-word
translation may not be acceptable.
1) Translate base on the meaning of source text
● I’m just pulling your leg → (KO) 장난 한 번 해 본 거야
● You have to follow the recipe to a T
→ (ES) Tienes que seguir la receta exactamente
● (ZH) 他是个笑面虎 → He says one thing and means another
 2) Please replace it with the idiom of the cultural area of the target language.
● When life gives you lemons, make lemonade → (ES) Al mal tiempo, buena cara
● He was beating around the bush → (ES) Él está andando por las ramas
● (ZH) 情人眼里出西施 → Beauty is in the eye of the beholder.

14. Repeated word(s)

If the source text has repeated words that do not seem to serve any purpose in the intended meaning,
please do not include the extra words in the translation.
● I I went I went to the park → (ES) Fui al parque.

15. Filler words

Do not include filler words in the translations unless they are deliberate interjections that are part of the
text.

1) Translate filler words

- when filler words in the source sentence are deliberate interjections that are part of the text.
● Oh I see ← Interjection; try to include and equivalent to “Oh” in the translation

2) Do not translate filler words

- if they are not deliberate interfection.
● My weekend was um uh not too bad ← Filler words; do not include “um uh”

3) Please use your best judgment based on the context provided when there is unsure of the
difference.
NB for British English translators
This is only for British English translators, so British English translators must click the link
below to check this notice carefully.

English(British) translation guide

Q&A
1. Translation of proper nouns and personal name
-Please follow the notation of the target language for proper nouns and personal names in the
original text.
-For words that do not have a notation, you can translate them according to the pronunciation.
● EN) Iron Man → (KO) 아이언 맨 / (JA) アイアンマン

2. If there are some words that are hard to be translated into the target language(ex.
EN 006, 04:38), can I leave them as it is?
-Yes, if the source text has those kinds of words, you can use them in the target text as they are
without translation.
( But please translate them as much as possible if it's translatable. )

3. What’s the criterion for “Error types”?

-The following list is the detailed criteria for the error types.
● Cases that don’t need to be checked for error type
○ Errors in word spacing
ex. (EN) Iloveyou / (ES) Tequiero
○ Typos or spelling errors under 3
ex. (EN) i wenp to thee shop / (KO) 나는 그 가개에 갓어 / (ES) Fui a esa tiendo.
○ Upper Cases and Lower Cases
ex. (EN) i loVe my ParentS / (ES) aMo a miS pAdreS
○ Omission of punctuation marks
 ex. (EN) Have you ever been to Korea / (KO)한국에 가본 적 있습니까
*But you need to check for error type when the sentence has over 3 typos or spelling errors.

4. Source text that has an unexpected language or is garbled

-You don’t have to translate that sentence. But the meaning of ‘Source is garbled’ is that it is
completely impossible to interpret and read the source text.
ex. WWW Hkaor peong doid;w
When the text doesn’t have any context and just has listed phrases or words that don’t have any
relevance, literal translation is needed.
ex. Full of action no reasons to inform two days late Brightness Rice

5. Is it compulsory to translate one source text into two versions? (HT Task)
-One source text must be translated into two versions. But only when the source sentence is hard
to translate, - ex. the source string is only composed of proper nouns so that it’s impossible to
create two versions - you can translate that sentence into one version.
(leaving translation 2 column blank of 10% or less of source sentences in each file is
permitted.)

6. If there is a case that one word has several meanings that are completely different,
would it be alright to translate it into the different meanings in translation 1 and 2?
Or should I retain the common meanings in both versions?
-If it is a homonym consisting of only words, it can be translated into different meanings in
translation 1 and 2.
-But If it is composed of sentences, you should consider the context and translate it accordingly.

7. Personal name

-Except for the names used as proper nouns, please follow the original text.
-However, in the case of Korean, Japanese, and Chinese, please translate the personal name
according to the pronunciation.

8. Proper noun
-If there are no local names such as brand name, product name, book title, movie title, song, etc.,
please translate them directly or according to the pronunciation.
9. Unfinished words and sentences

-If the sentence or words are not completely finished, translate them before the broken parts.
-However, if the words or sentence are broken because of typos, please infer and translate them
as much as possible.

10. Translation of sexual texts.

You need to translate all the texts even though they contain sexual things. Except for two cases
that we specified in the guideline, every text should be translated.

11. Procedures of Payments

-Payment will be issued on the 12th of the following month after the completion of the
internal inspection process after file submission.
(besides translators who are paid by Upwork, Alipay)
● If 12th is Saturday → paid on 11th

● If 12th is Sunday → paid on 13th

-Participants who quit midway will be considered to be of insufficient quality and will
therefore not be subject to payment.

*Notice
If you do not follow the instructions below, you might be asked to revise your translation.

● You have to translate the “check marked” source text .

(You can skip the translation in case of checking "skip")
● Don't input the original source into the translation column.
● Don't input the same translated sentence into translation1 and 2.
● When the 2nd translation is impossible, you can leave translation 2’s column blank.
● Don't write translation 2 first. Please fill the translation 1 column first.
● For sentences you checked ‘skip’, no payment will be made.