Difference between revisions of "Localyzer Express Repository Translation"
(→Commits trigger translations) |
(→Initiating a translation from LocalyzerQA) |
||
| Line 20: | Line 20: | ||
= Initiating a translation from 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: |
||
| + | [[File:Localyzer Express Translate Add Russian.jpg|center|500 px]] |
||
| + | |||
| + | * Note: See [[Localyzer Express Repository Configuration]] for more information on configuration. |
||
| + | |||
| + | The 'Translate' button is visible and enabled when the configuration is valid. |
||
| + | [[File:Localyzer Express Translate Save Russian.JPG]] |
||
| + | |||
| + | Click on the Translate button: |
||
Revision as of 21:40, 19 November 2020
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.
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 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:
- Note: See Localyzer Express Repository Configuration for more information on configuration.
The 'Translate' button is visible and enabled when the configuration is valid.
Click on the Translate button:
