Korean language - unicode or not

[Richard Lavoie]

One of my clients ask me whether my product may be used on Korean text. My
application does not support unicode characters but support properly single
byte characters (cyrillic, etc.). There seems to be two sets of characters
in the Koeran language. Does anyone know whether one of these character
sets may be handled properly by non-unicode applications?

[Erik Lindberg]

Hello,

> One of my clients ask me whether my product may be used on Korean text.
My
> application does not support unicode characters but support properly
single
> byte characters (cyrillic, etc.).

You don't need Unicode for Korean. You can use codepage Windows Korean (949)
(Wansung encoding).

> There seems to be two sets of characters
> in the Koeran language. Does anyone know whether one of these character
> sets may be handled properly by non-unicode applications?

In litterature (written back in 2000) they say: "At one time, MS had defined
a different codepage for Korean, cp1361, that used "Johab", 'combining'
encoding, which represents each syllable in terms of the component jamo.
This was capable of representing all possible combinations. The Johab
codepage is no longer supported, however."

Thus using cp 949 should be the choice in your case.

Best regards,

Erik Lindberg
Product specialist
Multilizer
www.multilizer.com