- Extracting the user interface elements
A localization engineer analyzes the program source to locate all translatable elements and prepare them for translation. A typical application includes many types of text elements —strings, menus, commands, and dialog boxes?but also bitmaps, icons, and even sound or video clips. During the analysis, we also verify that there is no "hard coding" left, that all the interface elements have been separated from the code, and that any concatenation is clearly marked.
- Rebuilding the original interface
During the analysis, we rebuild the entire user interface to verify that all the elements are available. We also verify that the installation module and all other on-line elements have been considered (demo versions, on-line samples and tutorials).
- Building pseudo-translated application
Software localization usually takes place during the last stage of the development, when the original product is undergoing final revisions. To verify that all internationalization guidelines have been followed, we can quickly produce a pseudo-translated version of the user interface. This version is tested by the QA division to locate potential problems and address them before they affect the localization process.
- Preparing the translation kit
Each element of the user interface is prepared according to the tools that will be used by the translators. Translation memories are applied to the text elements to leverage existing translations and increase the consistency between different products from the same family.
- Translating the user interface
Our software translators use industry-standard terminology and client specific glossaries to achieve a high level of acceptance within the target market. During the translation process, they work with the engineering team to ensure that the locale conventions are followed.
1 2