Translation
- or -
Post a project like this$$
- Posted:
- Proposals: 58
- Remote
- #3171129
- Expired
2337053550217314686884677375291162912418043993497219535254979133394694
Description
Experience Level: Intermediate
Hi there! Need translators and/or proofreaders for the following languages: Armenian, Arabic, Azerbaijani, Chinese (both simplified and traditional), Spanish, Estonian, Persian, French, German, Hindi, Indonesian, Italian, Japanese, Korean, Norwegian, Portuguese, Swedish, Turkish, Ukrainian, Urdu and Uzbek. Translated portions should be proofread, untranslated portions should be translated. I will select as many freelancers for this job as will be required.
There are roughly 980 words or so in each translation. Find the current translations attached as an archive to this job. Please:
1. Use the en.yaml file as the source of truth for the translations/proofreading (some translations are missing in the corresponding language files but are present in the en.yaml file)
2. Don't translate/proofread the commands (e.g. "/help") but do translate/proofread the commands descriptions (e.g. "Shows this message \U0001F631").
3. Use *single* space
4. Don't add unnecessary spaces (e.g. " / help")
5. Use an em dash (i.e. "—" and not "-") where appropriate
6. Try to keep yaml files valid (though don't stress about it much, I can fix it)
7. Use right-to-left unicode modifiers in the beginning of all lines in case you need it
8. Use `\n` for new lines
Please, reply to this posting with:
1. How much time will it take to translate/proofread (for all languages you can handle separately)
2. What languages you can translate/proofread for this project
3. How much it will cost to translate/proofread (for all languages you can handle separately)
There are roughly 980 words or so in each translation. Find the current translations attached as an archive to this job. Please:
1. Use the en.yaml file as the source of truth for the translations/proofreading (some translations are missing in the corresponding language files but are present in the en.yaml file)
2. Don't translate/proofread the commands (e.g. "/help") but do translate/proofread the commands descriptions (e.g. "Shows this message \U0001F631").
3. Use *single* space
4. Don't add unnecessary spaces (e.g. " / help")
5. Use an em dash (i.e. "—" and not "-") where appropriate
6. Try to keep yaml files valid (though don't stress about it much, I can fix it)
7. Use right-to-left unicode modifiers in the beginning of all lines in case you need it
8. Use `\n` for new lines
Please, reply to this posting with:
1. How much time will it take to translate/proofread (for all languages you can handle separately)
2. What languages you can translate/proofread for this project
3. How much it will cost to translate/proofread (for all languages you can handle separately)
Valentine M.
0% (0)Projects Completed
-
Freelancers worked with
-
Projects awarded
0%
Last project
6 May 2024
Italy
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
Hi Valentine,
you mentioned there is an attachment?! Can you please double-check? Thanks!
cheers,
Agnes
971801
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies