You are here: Customizing Quality Knowledge Bases>Overview of Customize Features>Locales

DataFlux Data Management Studio 2.5: User Guide

Customize - Locales

A locale is a collection of data types and definitions that apply to a language, as that language is used in a nation or region. For example, the ENGBR locale applies to the English language as it is used in Great Britain. As an example of usage, the ENGBR locale includes a parse definition for postal codes. The postal code parse definition recognizes the structure of British postal codes. The ENUSA local has a different postal code parse definition.

Hierarchy and Inheritance

Locales are organized into the following hierarchy:

+ Global

|--+ Language
   |--+ Locale

Locales inherit data types and definitions from their Language and from Global. This inheritance enables the reuse of data types and definitions in multiple languages and locales. Global definitions apply to all locales. Language definitions apply to their descendant locales.

The Data Types and Definitions pane shows that when you load a locale, you load data types and definitions from that locale, and also from the ancestors of that locale.

Locales can override inherited definitions. If a locale contains a definition that has the same name as an inherited definition, then the locale definition is used at run time. The locale definition masks or overrides the inherited definition.

Derived Locales

Certain locales are derived from other locales, primarily in support of bilingual nations or regions. For example, the locale French - Canada (FRCAN) locale is derived from English - Canada (ENCAN).

   + Global 
   |-+ Language (EN) 
     |-+ Locale 1 (ENCAN)
       |-+ Locale 2 (FRCAN)


Encodings map the character sets of national languages into binary code. Example encodings include Latin 1 (ISO-8859-1) and Turkish (ISO-8859-9).

All of the files in the QKB are encoded using the Unicode encoding standard. The Unicode standard has a variable-length binary code that supports all character sets. Unicode has been used in the QKB since CI 2010B.

As regards the customization of your QKB, encoding is relevant only when you import definitions from another QKB. If you import definitions, you are asked to select an encoding from a list of supported encodings. The default value Use System Default applies in most cases.

Related Topics

Documentation Feedback:
Note: Always include the Doc ID when providing documentation feedback.

Doc ID: dfU_Cstm_12001.html