A Typical Localization Process

Localization of your product is usually not as simple as translating only strings of code. Often there are resource files, such as video and audio, that need to be accounted for, and there are decisions throughout the process, namely what needs translating and what doesn’t. Related to this there are imports and exports of the code, or a build package, that come in and out of the translation database. This database is often where translators and others doing the localization of your product are working from.

All the while, translation memory and terminology databases are being updated with each review until a final package is exported, ready for testing and release.