Difference between revisions of "Localyzer Express Repository Translation"
(→Initiating a translation from LocalyzerQA) |
(→Initiating a translation from LocalyzerQA) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Once a repository |
+ | Once a repository has been configured and the configuration has been validated and saved, translations may happen. |
= Commits trigger translations = |
= Commits trigger translations = |
||
| Line 19: | Line 19: | ||
* Note: To review and Post Edit the translation, use LocalyzerQA |
* Note: To review and Post Edit the translation, use LocalyzerQA |
||
| − | = Initiating a translation from |
+ | = 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: |
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]] |
[[File:Localyzer Express Translate Add Russian.jpg|center|500 px]] |
||
| Line 25: | Line 25: | ||
* Note: See [[Localyzer Express Repository Configuration]] for more information on configuration. |
* 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]] |
||
| + | The 'Translate' button is visible and enabled when the configuration is validated and then saved. |
||
| − | Click on the Translate button: |
||
| + | [[File:Localyzer Express Translate Save Russian.JPG|center|500 px]] |
||
| + | |||
| + | |||
| + | |||
| + | Click on the Translate button: The resulting commit is clickable in the Translation Results |
||
| + | [[File:Localyzer Express Translated Russian.JPG|center|500 px]] |
||
| + | |||
| + | |||
| + | * 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: |
||
| + | [[File:Localyzer Express Translate Russian in Repo.JPG|center|500 px]] |
||
Latest revision as of 18:44, 11 March 2021
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:
