Creating a translation file for a existing translation

This document will guide you through the process of creating a translation file for an existing solution. This example applies when you have a solution created with a translation and you want to update it with changes in translations or new lines to translate.

Requeriments

To carry out this user guide, you must have the following sections configured:

• Innova Online setup: You must filled Customer id. (Innova Online setup).
• Configure ISO-639-1 codes for languages: You must configure the ISO-639-1 codes or completed the Install wizard (Install wizard). In languages page exists the action Update ISO-639-1 codes. This action updates the ISO codes for languages automatically.

Process

One the system is set up you should execute the next steps for create a translation file for a existing solution.

Load translation file

This actions inserts the translations lines from a existing translation file in a language specified. The field Caption ML is filled with the content of Target node from translation file.

You must indicate the language, ESP in this case, and the translation file.

The translations lines are created once the process is completed.

Tip

When tags are created or modified, the translation base file (file with the g.xlf extension) is automatically modified, but the translation files into other languages ​​are not modified. They must be modified for the modified or new tags to be translated. For this reason, the translation file is loaded in the specified language and then the Update captions action is executed. This will keep the lines up to date with the current information.

Update captions

This actions inserts the translations lines from a base translation file (file with extension g.xlf). The field Caption ML will be empty for to fill by the user.

Tip

If there are lines previously, they are not deleted, but are updated, marking if necessary the fields Caption changed (the label has been modified) or Caption not used (the label has been removed).

You must indicate the language, ESP in this case, and the base translation file (file with extension g.xlf).

The translations lines are created once the process is completed.

The user can fill the translations in 3 ways:

• Manually: Fill the fields manually.
• Automatically translation: Executing the action Translate captions.
• External translation: Executing the functionallity External translation (External translation)

Tip

The lines marked as Caption not used are lines that no longer exist in the translation base file (file with extension g.xlf) and therefore will not be created in the translation file. These lines can be removed by executing the Delete captions not used action.

Create translation file

You must generate the translation file for the language once the lines are translated.

You must indicate the language, ESP in this case, and the base translation file (file with extension g.xlf). The file is used for generate the translation file with the language.

A new translated file is created once the process has been completed. This file has the Target node filled with the language.

Languages

This document is available in these languages:

• (Spanish)
• (English)