Translations

Translated application strings are stored in the translation XML files located in the \bin folder (by default, C:\Program Files\Omada Identity Suite\Enterprise Server\website\bin). The files have an .xml extension, for example, en-us.master.xml is for American English, and de-de.master.xml is for German.

The relevant XML file contains both built-in strings, which can only be customized using custom XML files, and the translations for the master data (for example, view names, menu items, properties, etc.), which can also be maintained from within the application.

Customize the built-in strings

To customize the built-in strings, create a corresponding, new custom.xml file and store it in C:\Program Files\Omada Identity Suite\Enterprise Server\website\bin folder.

For each language, create a new file and name it accordingly: <xx-xx>.custom.xml where xx-xx is standard language and region code, for example, en-us.custom.xml:

<?xml version="1.0" encoding="utf-8"?>
<translations mode="advanced" xmlns="http://tempuri.org/OmadaTranslations">
  <text id="1017">
    <source>APSTRLST</source>
    <type>Btn</type>
    <original>APSTRLST_Btn_Refresh</original>
    <originalTranslation>Refresh</originalTranslation>
    <translated>Reload</translated>
    <clientside>false</clientside>
    <review>false</review>
  </text>
</translations>

tip

For information on the available languages and their corresponding cultures, refer to the Menus and settings section of the documentation.

Within the file, translate the strings in the <translated> tags. Do not change anything else.

warning

Remember to supply the custom file only with the strings that are different from the master strings. Do not duplicate the existing elements in the file.

Master data strings

info

Captions are automatically imported for languages not marked as disabled. Marking unused languages as disabled can improve performance and reduce noise in the frontend when the system is translating to the relevant languages. To do this, from SQL Management Studio, open the table tblLanguage, and mark unused languages as disabled.

During an upgrade, default data strings will be automatically overwritten if they have not been altered (disregarding the letter case, spacing, commas, and periods).

If you want to revert to the default values, which is recommended, you must open the Application strings menu item located in the Omada Identity Portal > Setup > Administration > More and click Revert to defaults. In that view, you can see all customized strings, and choose the ones you want to revert to the default value.

note

The function Revert to defaults must be executed in all staging environments, including production environments.

During a product update, the non-customized application strings may be revised.

When customizing an application string, the string will not be overwritten during a product update. You can only go back to the default value by using the Revert to defaults function.