Home | Previous Page | Next Page   GLS Fundamentals >

Understanding a GLS Locale

In a client/server environment, both the database server and the client application must know which language the data is in to be able to process the application data correctly. A GLS locale is a set of Informix files that bring together the information about data that is specific to a given culture, language, or territory. In particular, a GLS locale can specify the following:

IBM Informix products use the following GLS files to obtain locale-related information. For more information, see Appendix A. Managing GLS Files.

Type of GLS File Description
GLS locale files Specify language, territory, writing direction, and other cultural conventions.
Code-set files Specify how to map each logical character in a character set to a unique bit pattern.
Code-set-conversion files Specify how to map each character in a "source" code set to a corresponding characters in a "target" code set.
The registry file Associates code-set names and aliases with code-set numbers that specify filenames of locale files and code-set conversion files.

Each database is limited to a single locale, but different databases of the same database server can support different locales.

A single database can store character data from two or more languages that require different character sets by using the open-source International Components for Unicode (ICU) implementation of the Unicode code set (UTF-8). This code set is available in GLS database server locales for many languages and territories. (Locales for some client-side systems also support the ICU code set UTF-8, as well as the ICU code sets UTF-16 and UTF-32.)

Dynamic Server

The SET COLLATION statement of Dynamic Server supports more than one localized collating order to sort NCHAR and NVARCHAR character strings.

End of Dynamic Server
Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]