At Korea, Johab code is very old encondig.
by the way, cp949 code page is really used in most environments.
Personally speaking, Johab server code set is not need.
I think that PostgreSQL supports UHC (cp949) server code set.
This feature will be greet many Korean. :)
Unfortunately, UHC code set have character sequences less then 128 byte.
I tred to patch this problem, but this is not simply. I had gave up. :(
----- Original Message -----
From: "ITAGAKI Takahiro" <[EMAIL PROTECTED]>
To: "Tom Lane" <[EMAIL PROTECTED]>
Cc: <pgsql-hackers@postgresql.org>
Sent: Monday, March 26, 2007 11:29 AM
Subject: Re: [HACKERS] Server-side support of all encodings
Tom Lane <[EMAIL PROTECTED]> wrote:
> PostgreSQL suppots SJIS, BIG5, GBK, UHC and GB18030 as client
> encodings,
> but we cannot use them as server encodings. Are there any reason for
> it?
Very much so --- they aren't safe ASCII-supersets, and thus for example
the parser will fail on them. Backend encodings must have the property
that all bytes of a multibyte character are >= 128.
But then, PG_JOHAB have already infringed it. Please see
johab_to_utf8.map.
Trailing bytes of JOHAB can be less than 128.
It's true that other server-supported encodings use only characters >=
128.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
