Localyzer Express Repository Translation
Once a repository has been configured and the configuration has been validated and saved, translations may happen.
Commits trigger translations
In this example, RebelOutfitters has been configured for Chinese, French, German, Japanese, Korean, and a few more locales.
Let's edit a source file, here strings.json under the en-US directory:
Instead of Mediator, it is now Ambassador in English.
This triggered a translation for that one file, with that change, and the translations are returned quickly, here in less than 1 minute. This depends on how many words need to be translated.
Let's look at one translation:
- Note: To review and Post Edit the translation, use LocalyzerQA
Initiating a translation from Localyzer Express
Especially with a new configuration, you may want to initiate a translation. Let's add a new target locale to the Rebel Outfitters, Russian, and let's validate the new configuration:
- Note: See Localyzer Express Repository Configuration for more information on configuration.
The 'Translate' button is visible and enabled when the configuration is validated and then saved.
Click on the Translate button: The resulting commit is clickable in the Translation Results
- Note: The other locales already were fully translated, so only Russian was returned. Pseudo-localization and trackback (for use with LocalyzerQA) were also previously returned
Click on the 'commit' link to see the translated file(s) in the repository: