Localization

23

Localization Overview

Message Properties Files

Customizing the Navigation Tree

Double-Byte Characters in Audit Trails

Localization Overview

Redcell text appears in the following distinct entities: menus, forms and fields, and messages. The Internationalization feature of Redcell lets you alter the text for each of these entities to the language appropriate for a particular locale. This chapter describes the steps needed to do this.

The easiest of these to change is setting properties to force a particular locale for messages. Only message files for English ship with the software, so these properties have English as the default. You can override them as needed.

Setting the language property to empty string in installprops/lib/installed.properties applies the operating system’s defaults.

Override the properties for Locale follows in that file:

oware.resourcebundle.language=en

oware.resourcebundle.country=US

oware.resourcebundle.language.variant=

The language value must be a valid ISO Language Code. These codes are the lower-case, two-letter codes as defined by ISO-639. You can find a full list of these codes at a number of sites, for example: www.ics.uci.edu/pub/ietf/http/related/iso639.txt

The country value must be a valid ISO Country Code. These codes are the upper-case, two-letter codes as defined by ISO-3166. You can find a full list of these codes at a number of sites, for example: www.chemie.fu-berlin.de/diverse/doc/ISO_3166.html

The variant value is a vendor or browser-specific code. For example, use WIN for Windows, MAC for Macintosh, and POSIX for POSIX. Where two variants exist, separate them with an underscore, and put the most important one first. For example, a Traditional Spanish collation might construct a locale with parameters for language, country and variant as: es, ES, Traditional_WIN.

[spacer]

Multilingual support does not necessarily extend to all application add-ons.