Oracle Note Which Character Set Supports Wich Language
Oracle Note Which Character Set Supports Wich Language
In this Document
Purpose
Scope
Details
Character Sets:
References
APPLIES TO:
PURPOSE
To help in choosing the correct NLS_CHARACTERSET for your Oracle database or to have an idea what languages a
client will support once the correct NLS_LANG is found.
SCOPE
All DBA's
DETAILS
This note identifies which ISO or MSWIN character sets supported by Oracle contain the characters from which
languages.
The Oracle name for the character set is given with the ISO name in brackets.
The NLS_LANG NEEDS to reflect the client Operating system charterset/encoding and cannot be "choosen", there is
only one correct value for a certain client.
This means that the old fable that the NLS_LANG NEED to be the same as the NLS_CHARACTERSET is NOT true. It
may be perfectly CORRECT to use a NLS_LANG set to WE8MSWIN1252 for a windows client and a
NLS_CHARACTERSET set to AL32UTF8 for example
This is documented in
Note:158577.1 NLS_LANG Explained (How does ClientServer Character Conversion Work?)
Note:179133.1 The correct NLS_LANG in a Windows Environment
Note:264157.1 The correct NLS_LANG setting in Unix Environments
Note:229786.1 NLS_LANG and webservers explained.
The NLS_CHARACTERSET has no relation with the Operating System of the database server, so it can be "choosen
freely" from all that are available in Oracle.
Oracle do not need any "OS" support to use a characterset as NLS_CHARACTERSET.
Hence for the NLS_CHARACTERSET the question "which one do I need to use" is often asked.
For the majority of customers an Unicode character set (AL32UTF8) is the best choice Note 333489.1 Choosing a
database character set means choosing Unicode and Note 1051824.6 What languages are supported in an Unicode
(UTF8/AL32UTF8) database?
For nonUnicode charactersets the best choice are xx8MSWIN125x charactersets, even if the database itself runs
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=t0260t5af_14#BODYTEXT 1/4
03/06/2015 Document Display
on an Unix platform.
The reason is simply that the majority of the clients are windows based systems, hence the best nonUnicode
characterset for a database is a characterset that can store all the characters known by those clients, which means
an xx8MSWIN125x characterset.
Your current value for the database characterset ( NLS_CHARACTERSET ) can be found with this select:
Character Sets:
All of these character sets below contain also the 7bit ASCII characters ( US7ASCII ) characters ie: all English
characters and numerals used in languages who don't use an diacritics (accents and so) like English or the Latin
script version of Malay.
WE8ISO8859P15 (ISO 885915), WE8MSWIN1252 Albanian, Basque, Breton, Catalan, Cornish, Danish,
Dutch, Finnish, French, Frisian, Galician, German,
Greenlandic, Irish Gaelic (new orthography), Italian,
Luxemburgish, Norwegian, Portuguese, Rhaeto
Romanic, Scottish Gaelic, Spanish, Swedish .
The Euro symbol
VN8MSWIN1258 Vietnamese
TH8TISASCII Thai
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=t0260t5af_14#BODYTEXT 2/4
03/06/2015 Document Display
JA16SJIS Japanese
KO16MSWIN949 Korean
UTF8, AL32UTF8, AL16UTF16 All above languages and many more Note 1051824.6
What languages are supported in an Unicode
(UTF8/AL32UTF8) database?
REFERENCES
NLS_CHARACTERSET
NOTE:282336.1 Charts of most current monobyte / 8 bit Character sets
Didn't find what you are looking for?
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrlstate=t0260t5af_14#BODYTEXT 4/4