Localyzer Express Repository Translation

From Lingoport Wiki
Revision as of 21:47, 19 November 2020 by Olibouban (talk | contribs) (Initiating a translation from LocalyzerQA)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Once a repository have 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.

Localyzer Express Translate RebelOutfitter Config.JPG

Let's edit a source file, here strings.json under the en-US directory:

Localyzer Express Translate English Modification.JPG

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.

Localyzer Express Translate Returned Right Away.JPG

Let's look at one translation:

Localyzer Express Translate Returned French.JPG
  • Note: To review and Post Edit the translation, use LocalyzerQA

Initiating a translation from LocalyzerQA

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:

Localyzer Express Translate Add Russian.jpg


The 'Translate' button is visible and enabled when the configuration is valid.

Localyzer Express Translate Save Russian.JPG


Click on the Translate button: The resulting commit is clickable in the Translation Results

Localyzer Express Translated Russian.JPG


  • 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:

Localyzer Express Translate Russian in Repo.JPG