Using language identifiers

American English ("en") is the default language of the MDEX Engine.

If your application contains text in non-English languages, you should specify to the MDEX Engine the language of the text, so that it can perform language-specific operations correctly.

You use a language ID to identify a language. Language IDs must be specified as a valid RFC-3066 or ISO-639 code, such as the following examples:
  • da – Danish
  • de – German
  • el – Greek
  • en – English (United States)
  • en-GB – English (United Kingdom)
  • es – Spanish
  • fr – French
  • it – Italian
  • ja – Japanese
  • ko – Korean
  • nl – Dutch
  • pt – Portuguese
  • zh – Chinese
  • zh-CN – Chinese (simplified)
  • zh-TW – Chinese (traditional)
A list of the ISO-639 codes is available at:
http://www.w3.org/WAI/ER/IG/ert/iso639.htm

How to supply the language ID

You can supply the language ID for source data using one of these methods:
  • A global language ID can be used if all or most of your text is in a single language.
  • A per-record language ID should be used if the language varies on a per-record basis.
  • A per-dimension/property language ID should be used if the language varies on a per-dimension basis.
  • A per-query language ID should be used in your front-end application if the language varies on a per-query basis.

The following topics describe these methods of specifying the language ID for your data.