Re: [HACKERS] Re: [PATCHES] Postgres-6.3.2 locale patch (fwd) - Mailing list pgsql-hackers

From Satoshi Kinoshita
Subject Re: [HACKERS] Re: [PATCHES] Postgres-6.3.2 locale patch (fwd)
Date
Msg-id 3580CEF4.32C3B4C9@acm.org
Whole thread Raw
In response to Re: [HACKERS] Re: [PATCHES] Postgres-6.3.2 locale patch (fwd)  (t-ishii@sra.co.jp)
Responses Re: [HACKERS] Re: [PATCHES] Postgres-6.3.2 locale patch (fwd)  (t-ishii@sra.co.jp)
List pgsql-hackers
> The biggest problem for Unicode is that the translation is not
> symmetrical. An encoding to Unicode is ok. However, Unicode to an
> encoding is like one-to-many. The reason for that is "Unification." A
> code point of Unicode might correspond to either Chinese, Japanese or
> Korean. To determine that, we need additional infomation what language
> we are using. Too bad. Any idea?

It seems not that bad for the translation from Unicode to Japanese EUC
(or SJIS or Big5).
Because Japanese EUC(or SJIS) has only Japanese characters and Big5 has only Chinese characters(regarding to only CJK).
Right?
It would be virtually one-to-one or one-to-none when translating
from unicode to them mono-lingual encodings.
It, however, would not be that simple to translate from Unicdoe to
another multi-lingual encoding(like iso-2022 based Mule encoding?).

Kinoshita

pgsql-hackers by date:

Previous
From: t-ishii@sra.co.jp
Date:
Subject: Re: [HACKERS] now 6.4
Next
From: 8ch5yg
Date:
Subject: ...