Korean (KO16KSC5601) or UTF8

From: Carlos <miotromailcarlos_at_netscape.net>
Date: 3 Oct 2003 04:35:59 -0700
Message-ID: <1de5ebe7.0310030335.6cd36daf@posting.google.com>

Hi all:

Our system is Oracle 8.1.6 on Windows 2000 and we face a project that must be developed in Korean. My doubts are about choosing between UTF8 codepage and an only-korean codepage (KO16KSC5601: KSC5601 16-bit Korean) that has the ASCII within. Note that we must NOT support many languages at a time in the same DB, but one exotic ( at least for us it is!) language at a time. So, does it worth to go to unicode with UTF8? Without having much experience with *foreign* codepages, It seems to me that
it would be easier with the korean codepage, since is a single change for
us: we change our western europe codepage for this new one. Besides that,
I have read about troubles with UTF8 an the way Oracle manages it. (Some
claim that Oracle UTF8 is not *pure* unicode).

On the other hand, we will have to interactuate some other UNIX systems (I guess they will be 'korean' UNIXes) through C/C++ apps.

Finally, there will be windows clients executing Oracle Forms.

So, what is your (expert) opinion? I would appreciate any suggestions, experiences and tips that you could send me.

Thank you very much in advance and greetings from Spain.

Carlos. Received on Fri Oct 03 2003 - 06:35:59 CDT