A locale bundle is a set of properties files used in localizing software. The files contain other-language versions of the labels and messages displayed to users. The locale bundles associated with a Domain provide localized text when creating and running reports based on Domains. When a user’s operating environment specifies a locale, the server looks for the corresponding locale bundle and uses the labels and messages it contains. The localized text appears in the Ad Hoc designer and in the report viewer. The server interface is already internationalized, and Domains allow reports localized so users can create and view reports in their language.
A locale bundle for a Domain consists of a single file containing all the internationalization keys for the sets and items in the Domain. Each key is associated with the text for the label or description in the language of the target locale. The name of the file includes the target locale, so the server automatically associates it with the user’s locale when needed.
|
Language |
Locale |
File Name |
Sample Contents |
|
English |
default |
ExampleDomain.properties |
ACCOUNTS.NAME.LABEL=Customer ACCOUNTS.NAME.DESCR=Name of Customer |
|
French |
fr |
ExampleDomain_fr.properties |
ACCOUNTS.NAME.LABEL=Client ACCOUNTS.NAME.DESCR=Nom du client |
When a Domain with locale bundles is used to create or run a report, the server resolves each label to display as follows:
| • | The server looks for the same key in a default bundle among the resources. If these exist, it displays the text associated with the key in the default bundle; if the default bundle or key does not exist, then |
| • | It displays the text of the label property defined in the Domain design; if no label is defined, then |
| • | It displays the value of the id property. |
Descriptions are localized in the same manner, except they are left blank if there is no locale bundle, default bundle, or description property defined.
There are several strategies for managing the locale bundles. Based on the search algorithm above and your localization needs, you could have one of the following scenarios:
| • | You do not have any localization needs at the time you create the Domain. You give all labels and descriptions a clear and complete text within the design, and you leave the key names undefined. As your enterprise grows, users in another country need to create reports based on the Domain. To create localized text for those users, edit the Domain design to define the internationalization keys, then create the locale bundle. You can create locale bundles incrementally each time you have users who need a new language. Users in your home country who do not specify a locale still see the labels and description in the original Domain design. |
| • | You want to create the Domain tailored to a multilingual environment where reports need to be localized for each user’s specified locale. In this case, you do not specify any labels or descriptions in the Domain design, only the internationalization keys. Then you create a default locale bundle that gives the clear and complete text of every label and description in your preferred language. In this way, all user-visible text for the Domain is in the standard format of a locale bundle, and you can use specialized software or translation services to create all the locale bundles you need. In case a label or description is not translated, users see the text of the default locale bundle. |