Single-Byte and Double-Byte Considerations
Many single-byte languages support either national code pages or multinational code pages. The double-byte languages support specific individual national code pages by language.
Single-byte character sets use a collection of phonetic characters that require one byte to create a single character. Conversely, the double-byte character sets use ideographic characters and require two bytes to create a single character.
Single-byte languages can generally be run on single-byte or double-byte systems. Double-byte languages, such as Japanese, Chinese, and Korean, must run on machines configured to support a double-byte system. For example, a double-byte SQL Server or Oracle database is required for Chinese and Japanese languages.
The software can perform a Query By Example (QBE) on any character. However, when using a double-byte language, this process may not necessarily use an understandable collating sequence, although it can still use QBE for any double-byte column.
The following table shows the languages that the software supports and the LocalCodeSet
values set in the JDE.INI
for each platform:
Tier |
Language |
Language Code |
LocalCodeSet Value |
---|---|---|---|
1 |
English |
E |
WE_ISO88591 |
1 |
French |
F |
WE_ISO88591 |
1 |
German |
G |
WE_ISO88591 |
1 |
Italian |
I |
WE_ISO88591 |
1 |
Spanish |
S |
WE_ISO88591 |
1 |
Portuguese |
P |
WE_ISO88591 |
1 |
Japanese |
J |
JA_SJIS |
2 |
Danish |
DN |
WE_ISO88591 |
2 |
Dutch |
DU |
WE_ISO88591 |
2 |
Finnish |
FN |
WE_ISO88591 |
2 |
Norwegian |
NO |
WE_ISO88591 |
2 |
Swedish |
W |
WE_ISO88591 |
2 |
Korean |
KO |
KO_KSC |
2 |
Traditional Chinese |
CT |
TC_BIG5 |
2 |
Simplified Chinese |
CS |
SC_GB |
3 |
Arabic |
AR |
AR_CP1256 |
3 |
Czech |
C |
EECP1250 |
3 |
Hungarian |
HU |
EECP1250 |
3 |
Polish |
PO |
EECP1250 |
3 |
Greek |
GR |
GR_CP1253 |
3 |
Russian |
RU |
RS_CP1251 |
3 |
Turkish |
TR |
TK_CP1254 |