Globalization, localization, and NLS

APEX was designed with globalization, localization, and NLS (National Language Support) in mind. To begin with, the APEX interface is translated into nine languages, other than English. The languages are German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese.

APEX can utilize all the globalization, localization, and NLS features that the Oracle database has to offer, and add some of its own. The Application Builder Shared Components module includes a Globalization section, which allows us to define relevant parameters for globalization, localization, and NLS. It also includes a wizard to guide us through the process of translating our entire application into secondary languages.

APEX takes into account the client side NLS settings when dealing with the import and export of data into and out of the database. It also takes into account the database NLS settings, in order to properly sort data, display dates, number format (e.g. decimal point or comma) and the local currency, among others.

APEX supports the XLIFF (XML Localization Interchange File Format) standard, which allows us to translate an entire APEX application into any language we need, without re-writing the application code. APEX provides a built-in mechanism to simultaneously run the same application in multi language User Interfaces, giving us several options to determine the application language, including the option of matching the APEX application language to the end user's browser language preferences. Moreover, if we need to support a language which is not included in the native supported languages list, this mechanism will allow us to specifically translate the built-in APEX engine strings and messages into that language, allowing us to develop and support APEX application in any language that our database can support.

Note

Since version 2.0, the client side communicates with the server side, using the AL32UTF8 character set, regardless of the database character set. Due to some of the advanced technologies APEX is using (like AJAX), this setting is mandatory. If you are going to work in a multi-language environment, it would be optimal to set your database character set to AL32UFT8. This will ensure a true multi-language environment, while eliminating the need to employ any character set conversions between the client and the server. Oracle is advising users to use AL32UTF8 as their default choice for the database character set.

Throughout this book, we will devote special attention to globalization, localization, and NLS issues in the APEX environment, including RTL (Right-To-Left) support examples.