Tatsuo Ishii wrote:
Be very careful not to break the standard defined by Unicode.
For example the glyph for 0xe7a281 == U+7881 is defined in page 43 of
http://unicode.org/charts/PDF/U4E00.pdf. So we need to make sure that the
particular kanji character defined in Big5 0xf9d6 has the same glyph
as
> > 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
Heikki Linnakangas wrote:
張桂賢 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,
*
張桂賢 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 ETE
Roger Chang wrote:
The following bug has been logged online:
Bug reference: 4714
Logged by: Roger Chang
Email address: rchang...@gmail.com
PostgreSQL version: 8.3
Operating system: All
Description:Unicode Big5 Conversion
Details:
This is NOT a bug. but cause some
The following bug has been logged online:
Bug reference: 4714
Logged by: Roger Chang
Email address: rchang...@gmail.com
PostgreSQL version: 8.3
Operating system: All
Description:Unicode Big5 Conversion
Details:
This is NOT a bug. but cause some problem. Since long t
