From: | "Ioseph Kim" <pgsql-kr(at)postgresql(dot)kr> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: CP949 for EUC-KR? |
Date: | 2010-05-04 05:09:38 |
Message-ID: | 28505590D0214F85AD2633355B77D4B2@edarts.kr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi, I'm Korean.
CP51949 is EUC-KR correct.
so, that defined code is correct too.
But in Korea, EUC-KR code is not good to use all Korean character.
In recent years, many people in Korea use the CP949 code.
MS Windows codepage also is CP949.
----- Original Message -----
From: "Takahiro Itagaki" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: <pgsql-hackers(at)postgresql(dot)org>
Sent: Tuesday, April 27, 2010 7:27 PM
Subject: [HACKERS] CP949 for EUC-KR?
>I heard pg_get_encoding_from_locale() failed in kor locale.
>
> WARNING: could not determine encoding for locale "kor": codeset is "CP949"
>
> I found the following description in the web:
> CP949 is EUC-KR, extended with UHC (Unified Hangul Code).
> http://www.opensource.apple.com/source/libiconv/libiconv-13.2/libiconv/lib/cp949.h
>
> but we define CP51949 for EUC-KR in chklocale.c.
> {PG_EUC_KR, "CP51949"}, /* or 20949 ? */
>
> Which is the compatible codeset with our PG_EUC_KR encoding?
> 949, 51949, or 20949? Should we add (or replace) CP949 for EUC-KR?
>
> Regards,
> ---
> Takahiro Itagaki
> NTT Open Source Software Center
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2010-05-04 05:36:19 | Re: what is good solution for support NULL inside string_to_array function? |
Previous Message | Jan Wieck | 2010-05-04 03:55:25 | Re: COPY is not working |