Translation and Review Guidelines

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. If you do not mention a contributor's username in a comment or issue, they will not be 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. There are several priority levels to chose from when creating an issue: Low: Minor and cosmetic changes to a source string. Normal: Typos, questions or changes affecting the meaning of a source string that may hinder translation. High: Significant issues with the localizability or coherence of the source string. Critical: Issues with the source string that might break the software.

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.

Punctuation, capitalization, double spaces and typos matter! These small details make a big difference in the end product. Individuals are less likely to trust a tool with a messy and inconsistent interface, even if the translation itself is correct. While you are translating and reviewing, make sure you pay attention to the little details and remain faithful to the English source (while still using correct grammar and style for your language).

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 filters to double check that your translations are consistent in terminology, style and tone.

Use the Suggestions tab in the web editor to view translations of other strings and resources in related projects. Translations of strings which are up to 60% the same will appear in this tab. Referencing these suggestions will help you maintain consistency across projects.

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.