Localizing user interface controls
In this topic ...
Localizing Elements in the Web Application
Related Topics ...
We can use the Localized Resource Builder to add a Resource Bundle to the Web application. Depending on the browser's locale setting, the locale-specific resource bundle gets added to the Web application.
For example, we can configure Button labels and other non-content elements of your pages to get their values from the resource bundle. Here's how:
To localize non-content elements in the Web application:
- Add a Localized Resource Builder call to the model above non-content Builders in the Builder call list. and specify the following input values:
- Resource Bundle Name -- Enter the fully-qualified name of the property file or Java class that serves as the default Resource Bundle. For example, enter com.acme.LabelResources for the property file stored as, WEB-INF/work/source/com/acme/LabelResources.properties.
Store the locale-specific versions of this property in the same directory. For example, in the acme directory, you could store the Japanese version of the properties file (LabelResources_ja.properties) and the Italian version (LabelResources_it.properties).
- Language -- Enter the ISO language code for the Resource Bundle to load. Profile this value and create a profile set (Language), a profile for each language for which you have a resource bundle, and specify the ISO code as the Language value for each profile.
- Country -- Enter the ISO country code for the Resource Bundle to load. Profile this value create a profile in an appropriate profile set (for example, Language) and specify the ISO code as the Country value for each profile.
- For any Button Label, or similar builder call input, set the value using the Reference Chooser and selecting the appropriate entry from the LocaleData variable, which the Localized Resource Builder call adds to the Web application.