If CARL Source is used in an international context, that is, by users speaking different languages, it is possible to translate any terms you wish so that the functions can be understood by all users.
Most of the standard terms in the application can be provided by CARL Berger-Levrault in different languages.
The translation function allows you to translate your own data:
- Lists of values,
- Message templates,
- Statuses and transitions if you have created your own status workflows,
- Names of specific attributes or free fields, particularly in order to display the correct pop-up information for these fields in the forms where they appear.
If necessary, other application data may become translatable, such as the names of templates, for example, or the names of indicators. Consult with CARL Berger-Levrault for this type of configuration.
In the object dictionary, business objects that can be translated include the Translatableproperty. This is checked if at least one attribute (Alphanumeric) has been designated as Translatable.
The Enable/Disable business data translations actions (found in the object dictionary or language configuration) allow you to globally check off a list of default business objects and their attributes to make them translatable or non-translatable in one go. The data to be made translatable (or otherwise) can then be configured on a case-by-case basis.
Translation process
Only an authorized user may fill in the translation of names in the application.
For such a user: expanding the section accessible by clicking on the name of the logged in user (top right), the field displaying the user language provides access to a list of choices for changing the language of the current session.
This allows the translating user to switch dynamically between his/her language and another language, from among those defined in the operating configuration.
The new language will be applied to all screens that are opened thereafter.
Switching to a language that is not the language of the application has the following effects:
- The current screen is redisplayed dynamically in the "active" language for all terms already having a saved translation,
- The display of translatable fields is modified:
- Translatable fields that have already been translated are displayed in the active language,
- Translatable fields that have not yet been translated are displayed with their default content (that is, in the language of the application) and in a special style: greyed out and in italics to denote a missing translation.
When the field becomes the active data entry field, the text disappears to allow the translator to fill in the translation. - The tooltip for translatable fields includes the icon
indicating that the field is translatable.
- Translatable multi-line fields are not shown as greyed out or in italics, but they function in the same way.
In a table, the formatting is applied only to the selected line. - The pop-up information displayed for a translatable field specifies the language of the displayed text.
After the translations are entered, each user of that language will see the translated data in place of the "native" data, and if a user modifies a translated name, the translation will be modified and not the data in the language of the application.
If the DESCRIPTION object is made translatable, all long (multi-line) comment fields for each entity also become translatable across all application features, even if the entity itself is not translatable.
The user sees the existing comment in the entity's original language if no translation is available for their language. They have the option to edit this comment, which is then initialized in the displayed language with the content of the entity's original language, while incorporating the changes made, transparently to the user. This data is updated for the displayed language, while the original comment remains intact in its language of creation.