Data translation

The new field descriptions are automatically copied to the other data languages. These descriptions must be translated. This is to ensure that all users who are running another data language code can read the new fields in their own language.

We recommend that you assign dedicated users to perform the data translation; these users must be authorized to switch between different data languages.

To ensure that a user can switch to another data language, select the Allow Changing of Data Languages check box in the user's user data template properties. See the ( User Data Template (ttams1110m000) session).

Insertion and translation process

The tasks to translate multilanguage field descriptions depend on the data language the new records are specified in. See these sample scenarios:

Scenario 1: A user works in the base language and inserts a record

1. When the user inserts a record, the descriptions of the multilanguage-enabled table fields are inserted in the base language code. The descriptions are automatically copied to all other linked data languages.
2. For each table that is involved, you must run the Print Multi Language Application Data (ttadv4438m000) session. The session prints a report that shows the records that must be translated to other languages.
3. Switch to the other data language(s) and translate the descriptions of these records.

Scenario 2: A user works in another language and inserts a record

1. When the user inserts a record, the descriptions of the multilanguage enabled table fields are inserted in the other language code. Then they are automatically copied to all other available data languages and the base language.
2. For each table that is involved, you must run the Print Multi Language Application Data (ttadv4438m000) session. The session prints a report that shows the records that must be translated.
3. Switch to the base language and translate the descriptions of these records to the base language. The translated descriptions are automatically copied from the base language code to all other available data language codes. The language code in which the records were created first is not copied.
4. Run the Print Multi Language Application Data (ttadv4438m000) session again for each table that is involved. The session prints a report that shows the records that must be translated from the base language to other languages.

5. Switch to the other data language(s) and translate the descriptions of these records.

   Verify whether the descriptions that are stored in the original language code are still correct. That is, the language code in which the records were created.

   To remove the corresponding records in the check report, save a dummy change of these descriptions.