Creating the translation definition

The translation definition maps the label, description, and screen tip strings in your data module to the translations of those strings.

Before you begin

Your metadata must already be translated and the translation sources must already be added to the data module.

About this task

Specify the following properties to create the translation definition:

Label: The label is the name of the translation. The default value is the language name as set by the To language property. For example, if the To language property is French, the label value is French. You can change the label to any word or phrase. If you do this, the synchronization between the To language property and the label is lost. To restore the synchronization between the To language property and the label, click the Clear label button.
To language: This property defines the locale of the translation. If the content language of the user matches the To language value, the translation is used.
From language: This property represents the locale of the original text column. The locale of the original text could be different than the Design language property of the data module.
Specifying the From language locale allows the modeler to override translations from source modules that could be in a different design locale.
Original text field: The original text is the text of the Label, Screen tip, or Description from the data module. This text is the source string for translation. The instances of that string will be translated.; Select the checkbox Match the case of the original text if you know that your data source is case-sensitive. Otherwise, labels such as Retailer country and Retailer Country would be translated identically.
Translated text field: The translated equivalent of the Original text field.
Long identifier: This property consists of the identifier of the object whose Label, Screen tip, or Description is being translated, and any qualifying identifiers. This property is optional.; You can use the Long identifier to refine the scope of localization so that a string can be translated in different ways for different objects with the same label.; Select the checkbox Match the case of the long identifier to further refine of scope of the translation by matching the case of the long identifier. By default, the matching is case-insensitive
Active: You can have only one translation for a To language and From language locale pair set as active. However, you can have multiple inactive translations for the same locale pair.

Procedure

Click the Languages icon in the vertical toolbar.
Click the Add metadata conversion icon , and in the Create language dialog box, specify the required settings.
The following image shows the translation settings based on the sample data. For more information, see Using the sample files to create a multilingual data module.

The translation definition is added to the Languages pane.
To preview the definition, from its context menu, click Preview language.

A new tab is created where you can see the translated metadata. A green border is added around the previewed metadata.

You can save the data module preview with the translated strings in it. However, do not overwrite the source data module with the preview.
Save the data module.
To test the translated metadata, create a report based on your data module.
In user locale preferences, change the content language to the language to which your metadata is translated. The data tree in the report shows the translated strings in your selected language.