Ioseph Kim pgsql...@postgresql.kr wrote:
CP51949 is EUC-KR correct.
{PG_EUC_KR, CP51949}, /* or 20949 ? */
Thank you for the information. I removed or 20949 ? from the line.
Regards,
---
Takahiro Itagaki
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list
itagaki.takah...@oss.ntt.co.jp
To: pgsql-hackers@postgresql.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
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).
Takahiro Itagaki wrote:
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).
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
Should we add (or replace) CP949 for EUC-KR?
No. CP949 is not plain EUC-KR, but EUC-KR with some extensions (UHC). At
least on CVS HEAD, we recognize CP949 as an alias for the PostgreSQL
PG_UHC encoding.
That's it! We should
Takahiro Itagaki wrote:
That's it! We should have added an additional alias to chklocale, too.
Index: src/port/chklocale.c
===
--- src/port/chklocale.c (HEAD)
+++ src/port/chklocale.c (fixed)
@@ -172,6 +172,7 @@
