Even though we are agile and ship content reliably in a two week cycle for the iOS and Android apps, every three weeks for the website and every day for PHP and GO back ends, we need a translation process that can follow suit accordingly.
This short introduction gives you a glance into our localization process: Below you see all steps. We look at the second step ‘content preparation’ in more detail. If you want to start with a general overview check the blog post on translation setup.
- Content generation
- Content preparation/pre-translation
- Content merge + translation (and review)
- Content deploy
- Content review and bugfixing
- Content testing (and bugfixing)
→Rinse and Repeat with additional deploys interspersed in between
As soon as we know what a new feature will be about, we think up exactly the wording that goes best to explain what the feature does, how to use it and what benefits it brings. Even before a developer starts to work on the implementation, we send the strings that act as source material for all translations into other languages to a clever tool. The tool enters the string in it’s very own code repository called ‘pre-translate’. All content from this repo gets continuously uploaded to our translation management system (TMS). Sometimes we have more than one pre-translate commit per day as several code platforms develop features in their own rhythm.
The TMS sends a notification to all translators that new content is available and they have the option to ask questions about the sentence, request a screenshot or more information. And thus translation starts and is finished in a flash because translation happens regularly whenever new content comes online.
The following chart shows that we do not upload very much content at once, but little bits and pieces continuously
When the developers merge the fully developed feature – including the source strings – into the app code later on, the finished translations are automatically propagated to the incoming strings. The strings can be matched easily, because the pre-translate content was already entered into the translation memory (TM) system.
An additional benefit is that all developers can check the pre-translate repository, in addition to their own code repositories, for already completed strings and copy wording from other platforms like React Native, Web, Android or iOS and use it in their app or section of code.
This helped us especially in the beginning of this process to ensure an identical wording across platforms as well as to generate cost savings.