From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | 張桂賢 Roger Chang <rchang111(at)gmail(dot)com> |
Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #4714: Unicode Big5 Conversion |
Date: | 2009-03-18 14:55:27 |
Message-ID: | 49C10B5F.2050609@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
張桂賢 Roger Chang wrote:
> There is authoritative source for the Big5 encoding, but don't believe
> that do help
>
> http://www.cns11643.gov.tw/AIDB/encodings_en.do
>
> Skip the historical mess already done. we should focus on reality?
>
> brief events according time-line,
>
> * BIG5 created, mostly by ETEN company, some others but not important now.
> * CNS Standard like 11643, Taiwan Government authority building in
> mean time ...
> * Windows 3 showup, need Chinese ... pick not CNS but BIG5 ???
> Code Page 950 born.
> * ETEN company add "ETen-extension 0xF9D6-0xF9FE" to work with IBM5550
> * Since Windows ME, CP950 add above mentioned 7 char. 0xF9D6-0xF9FE ONLY ???
> * Later Hong Kong add above 7 Char. plus some more symbol in
> HKSCS-2004, and what you found is right.
> * WHAT A MESS !
>
> Focus on reality,
> only mentioned 7 Char. I need to build into pgsql sources to compliant
> with CP950, since few years ago.
Ok, so Windows codepage 950 has those 7 characters, but not the other
ETEN extended chars. I think that's a good enough reason to add those 7
chars; we have 'win950' as an alias for big5 anyway.
I'll go add those characters.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2009-03-18 15:31:19 | Re: BUG #4714: Unicode Big5 Conversion |
Previous Message | Tom Lane | 2009-03-18 12:41:01 | Re: BUG #4715: libpq `PQgetlength' return invalid field length. |