å¼µæ¡è³¢ 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