Translation and Review Guidelines: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
=Translation | =Translation and Review Tips= | ||
#'''Communicate with other translators and reviewers using [https://docs.transifex.com/translation/tools-in-the-editor#comments comments]''' if there is any confusion about a translation, terminology choices, or what the original source text means. '''Mention the contributor's name (@username) to make sure the relevant people are notified. | #'''Communicate with other translators and reviewers using [https://docs.transifex.com/translation/tools-in-the-editor#comments comments]''' if there is any confusion about a translation, terminology choices, or what the original source text means. '''Mention the contributor's name (@username) to make sure the relevant people are notified. | ||
#'''Create an [https://docs.transifex.com/translation/tools-in-the-editor#issues issue] if there is a fundamental problem with a string''' that impedes translation or needs to be changed. This will notify the developer and Localization Lab staff that there is a problem that needs to be resolved. | #'''Create an [https://docs.transifex.com/translation/tools-in-the-editor#issues issue] if there is a fundamental problem with a string''' that impedes translation or needs to be changed. This will notify the developer and Localization Lab staff that there is a problem that needs to be resolved. | ||
Revision as of 15:53, 6 November 2019
Translation and Review Tips
- Communicate with other translators and reviewers using comments if there is any confusion about a translation, terminology choices, or what the original source text means. Mention the contributor's name (@username) to make sure the relevant people are notified.
- Create an issue if there is a fundamental problem with a string that impedes translation or needs to be changed. This will notify the developer and Localization Lab staff that there is a problem that needs to be resolved.
- Pay attention to references to settings and buttons in other operating systems or pieces of software (i.e. iOS or Android) and be sure to use the translation used in those apps / operating systems.
Example: If the string refers to the Android OS "Settings", make sure the translations corresponds with the Android OS translation.
Similarly, if the app refers to "Settings" or "Send" etc. in its own interface, make sure the translation is the same across the application. - Use the glossary! Reference the glossary (and Concordance Search) to make sure you are using the correct terms. Input terms into the glossary as often as possible to help maintain consistency and quality of translations.
- Remember that the product name should not be translated or transliterated for this project unless you think it is necessary for users to understand, in which case you can follow the unique instructions for each on the projects.
- Read the "String Instructions" and "Developer Notes" for each string. They contain valuable information about how to translate the string.
- If a string is tagged as "notranslate" or "locked", do not translate the string. Copy the exact string from the original source.
- Use the "Concordance Search" and the search filter to double check that your translations are consistent in terminology, style and tone.
- Be aware of variables and placeholders! Make sure you maintain variables in the translated text, but feel free to move them around as necessary in your language's grammar.