The distinction between the data language and the display language in the AR System is crucial for localization.
If you have users in different locales, for example, users in England, France, and Germany, you must select a single data language in which users enter, search, and modify the data. Typically, this language is the one that is the most common across all your user locales. Only one data language can exist for a single AR System installation, and you select it at the time of installation. This requirement guarantees that users in France can find help desk tickets created in Germany or England because there are common data to work against.
The display language is used in the user interface (views) and should be determined while you install the clients.
During the installation of AR Systemclients, you can select more than one display or "view" language for your users to use, but the display language must be compatible with the underlying data language. For example, you can install French and German in any combination (data or display), but you cannot install a display language of French with a Japanese data language.
AR System provides many ways to localize the forms that users use to operate on the data, and those form views can use multiple display languages. Users can select the display language, assuming it is installed that is closest to their native language. According to this, French users see form views, error messages, and online help in their native language. With applications like the BMC Helix ITSM, you can add display languages after installation. For example, if an office is opened in Holland, you can add a Dutch language pack to the application.
For general messages, menus, and buttons, such as OK and Cancel, the browser uses the language that was installed on it. For example, if you localize forms in German, but the user is using a browser with English installed, the user might still see some messages, menus, and buttons in English.