At the beginning of the project, the localization manager and translators will familiarize themselves with your product. This process involves the following:
- We ask for a software build to install on our machine, or request access to the online version.
- We will ask you to fill out a Style Guide to find out, for example, details such as: is there a limit on string length; is there a principle governing how string keys are named; are there any strings and words that should not be translated, and how should the user be addressed, formally or informally?
- We determine whether you have a glossary, which is a list of terms with definitions, such as character names and the names of items in the game. If you don't have a glossary, we will help you draft a list of terms using special translation quality assurance tools and then decide which of the terms should be included.
- We will ask you to take screenshots of the software, if possible. Based on the screenshots, translators match the translated string with the real screen in which it is used.
- We create a project on an online platform and load the strings, screenshots, and glossary. Then we will invite translators to the project. We will ask them to familiarize themselves with the materials and try the software. We control project performance using a checklist.
The project manager will decide whether a user manual, glossary and screenshots are needed on a project basis.