One Identity Manager supports language-dependent representation of data. You can use this feature to edit display text in different languages for the One Identity Manager tool user interfaces. You can also create multi-language text for process information output, script processing as well as processing messages.
Detailed information about this topic
Related topics
In order to use multi-language data representation in One Identity Manager, the following prerequisites need to be fulfilled:
-
The language is set up in the database and labeled with the Select in front-end option.
-
A fallback language for the database is set. In default installation of One Identity Manager, the language used is English - United States [en-US]. This language is used if there is no translation available for a language-dependent data break down in the user’s requested language.
-
The Multilingual option has to be set on the column definitions in order to use multi-language display text.
-
Source and target of the translation are known.
-
#LD notation is used for outputting language-dependent data from within Visual Basic .NET expressions. #LD text is automatically extracted for translation. To do this, a column must be labeled as #LD content.
The translations are stored in the DialogMultiLanguage table. A key, the language and the translation are entered into the table.
Example:
The QERResource.Ident_QERResource column has the Resource text displayed as its column name in the login language English - United States [en-US] (DialogColumn.Caption). The Ressource column name should be used for the login language German - Germany [de-DE].
The QERResource.Ident_QERResource column contains the value Car. A user with the login language English - United States [en-US] is shown the Car value. A user with the login language German - Germany [de-DE] is shown the Auto value.
Table 67: Example of language-dependent entries in the DialogMultiLanguage table
|
DialogColumn.Caption |
Resource |
English - United States [en-US] |
Resource |
|
Resource |
German - Germany [de-DE] |
Resource |
|
QERResource.Ident_QERResource |
Car |
English - United States [en-US] |
Car |
|
Car |
German - Germany [de-DE] |
Auto |
Related topics
Columns must be marked for translation in order to enter multilingual captions.
To label a column for translation
-
In the Designer, select the One Identity Manager schema category.
-
Select the table and start the Schema Editor with Show table definition.
-
Select the column and then the Column properties view.
-
Select the Column tab and edit the Multilingual property. Specify the following settings:
-
Translation target: The column content is displayed in translation.
-
Translation source: The column supplies the translation.
-
#LD content: The column has contents in #LD notation. The contents are extracted for translation.
-
Without text memory fallback: The text store is not used as fallback for the column.
-
Split string at delimiter: The column content is separated at the delimiter. Forward slash (/), backslash (\) and colon (:) are recognized as delimiters. The function finds the translation of each part and combines them to form the complete content. For example, the setting is used for translating the full names of departments or application roles.
NOTE: To use this function, ensure that each of the parts are translated or their translations can be found from a translation source.
You can combine the values. The combination of values determines the resulting translation.
-
A translation target is normally the same as the translation source. If the translation, however, is taken from another translation source, enter this additionally as a language dependency.
Example: A column is translation target and source
The contents of the QERResource.Ident_QERResource column are to be translated. The Ident_QERResource column contains the value Car. A user with the login language English - United States [en-US] should be shown the value Car. A user with the login language German - Germany [de-DE] should be shown the value Auto. The actual translation should be maintained in the QERResource.Ident_QERResource column.
-
Label the QERResource.Ident_QERResource column in the Multilingual property with Translation target.
-
Label the QERResource.Ident_QERResource column in the Multilingual property with Translation source.
-
In the Language Editor, translate the entries for the Ident_QERResource column of the QERResource table.
When the column is loaded, it is determined that QERRessource.Ident_QERResource should be translated. For translation, the relevant key for the QERRessource.Ident_QERResource column is determined from the DialogMultiLanguage table and the value saved for the user’s login language is displayed.
Example: A column is translation target and takes its translation from another translation source
The action is displayed in the Manager process view in the current user's login language. The contents of the column DialogProcess.DisplayName are taken from the column JobEventGen.ProcessDisplay. The column JobEventGen.ProcessDisplay may use #LD notation to create the display string.
-
Label the JobEventGen.ProcessDisplay column in the Multilingual property with the values Translation source and #LD content.
-
Label the DialogProcess.DisplayName column in the Multilingual property with Translation target and as the Language dependecy, enter the JobEventGen.ProcessDisplay column.
-
In the Language Editor, translate the entries for the ProcessDisplay column of the JobEventGen table.
When the column is loaded, it is determined that DialogProcess.DisplayName should be translated. For translation, the relevant key for the JobEventGen.ProcessDisplay column is determined from the DialogMultiLanguage table and the value saved for the user’s login language is displayed.
Related topics
