Oracle8i National Language Support Guide Release 8.1.5 A67789-01 |
|
This appendix lists the languages, territories, character sets, and other locale data supported by the Oracle server. It includes these topics:
You can also obtain information about supported character sets, languages, territories, and sorting orders by querying the dynamic data view V$NLS_VALID_VALUES. For more information on the data which can be returned by this view, see Oracle8i Reference.
Table A-1 lists the languages supported by the Oracle server.
Oracle error messages and user interfaces have been translated into the languages which are listed in Table A-2.
Table A-3 lists the territories supported by the Oracle server.
Oracle-supported character sets are listed below, for easy reference, according to three broad language groups:
Note that some character sets may be listed under multiple language groups because they provide multilingual support. For instance, Unicode spans the Asian, European, and Middle Eastern language groups because it supports most of the major scripts of the world.
The comment section indicates the type of encoding used:
As mentioned in Chapter 3, "Choosing a Character Set", the type of encoding will affect performance so you should use the most efficient encoding that meets your language needs. Also, some encoding types can only be used with certain data types. For instance, fixed-width multibyte encoded character sets can only be used as an NCHAR character set, and not as a database character set.
Also documented in the comment section are other unique features of the character set that may be important to users or your database administrator. For instance, whether the character set supports the new Euro currency symbol, whether user defined characters are supported for character set customization, and whether the character set is a strict superset of ASCII (which will allow you to make use of the ALTER DATABASE [NATIONAL] CHARACTER SET command in case of migration.)
EURO = Euro symbol supported
UDC = User-defined Characters supported
ASCII = Strict Superset of ASCII
Oracle does not document individual code page layouts. For specific details about a particular character set, its character repertoire, and code point values, you should refer to the actual national, international, or vendor-specific standards.
Table A-4 lists the Oracle character sets that can support Asian languages.
Table A-5 lists the Oracle character sets that can support European languages.
Table A-6 lists the Oracle character sets that can support Middle Eastern languages.
Table A-7 lists the Oracle character sets that provide universal language support, that is, they attempt to support all languages of the world, including, but not limited to, Asian, European, and Middle Eastern languages.
Name | Description | Comments |
---|---|---|
AL24UTFFSS |
Unicode 1.1 UTF-8 Universal character set |
MB, ASCII, EURO |
UTF8 |
Unicode 2.0 UTF-8 Universal character set |
MB, ASCII, EURO |
Note: The Unicode 1.1 character set has been superseded by Unicode 2.0. One of the major differences between version 1.1 and 2.0 is the redefinition and addition of 11,172 Korean characters. Whenever possible, you should use the latest version of the Unicode standard. The primary scripts currently supported by Unicode 2.0 are:
Arabic |
Gujarati |
Latin |
Armenian |
Gurmukhi |
Lao |
Bengali |
Han |
Malayalam |
Bopomofo |
Hangul |
Oriya |
Cyrillic |
Hebrew |
Tamil |
Devanagari |
Hiragana |
Telugu |
Georgian |
Kannada |
Thai |
Greek |
Katakana |
Tibetan |
For details on the Unicode standard, see http://www.unicode.org or refer to the Unicode Standard, defined by the Unicode consortium.
Linguistic definitions define linguistic cases for particular languages. Extended linguistic definitions include some special linguistic cases for the language. Typically, using the extended definition means that characters will be sorted differently from their ASCII values. For example, ch and ll are treated as only one character in XSPANISH. Table A-8 lists the linguistic definitions supported by the Oracle server.
By default, most territory definitions use the Gregorian calendar system. Table A-9 lists the other calendar systems supported by the Oracle server.
March 20, 1998 looks like this in ROC Official:
March 27, 1998 looks like this in Japanese Imperial:
Table A-10 lists the character sets that support the Euro symbol.