Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: [PATCHES] Postgres-6.3.2 locale patch (fwd)

From: t-ishii(at)sra(dot)co(dot)jp
To: Peter Mount <peter(at)taer(dot)maidstone(dot)gov(dot)uk>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: [PATCHES] Postgres-6.3.2 locale patch (fwd)
Date: 1998-06-04 08:16:13
Message-ID: 199806040816.RAA13969@srapc451.sra.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
>In a same vein, for getting JDBC up to speed with this, we may need to
>have a function on the backend that will handle the translation between
>the encoding and Unicode. This would allow the JDBC driver to
>automatically handle a new character set without having to write a class
>for each package.

I already have a patch to handle the translation on the backend
between the encoding and SJIS (yet another encoding for Japanese).
Translation for other encodings such as Big5(Chinese) and Unicode are
in my plan.

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?
---
Tatsuo Ishii
t-ishii(at)sra(dot)co(dot)jp

Responses

pgsql-hackers by date

Next:From: Peter MountDate: 1998-06-04 08:58:12
Subject: Re: [HACKERS] Re: [PATCHES] Postgres-6.3.2 locale patch (fwd)
Previous:From: Stephane MONEGERDate: 1998-06-04 08:03:57
Subject: Problem with array of char

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group