Re: Patch for collation using ICU

From: "John Hansen" <john(at)geeknet(dot)com(dot)au>
To: "Alvaro Herrera" <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <girgen(at)pingpong(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch for collation using ICU
Date: 2005-05-08 05:01:26
Message-ID: 5066E5A966339E42AA04BA10BA706AE50A930E@rodrick.geeknet.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> Sent: Sunday, May 08, 2005 2:49 PM
> To: John Hansen
> Cc: Tatsuo Ishii; pgman(at)candle(dot)pha(dot)pa(dot)us;
> girgen(at)pingpong(dot)net; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> On Sun, May 08, 2005 at 02:07:29PM +1000, John Hansen wrote:
> > Tatsuo Ishii wrote:
>
> > > So Japanese(including ASCII)/UNICODE behavior is
> perfectly correct
> > > at this moment.
> >
> > Right, so you _never_ use accented ascii characters in Japanese?
> > (like è for example, whose uppercase is È)
>
> That isn't ASCII. It's latin1 or some other ASCII extension.

Point taken...
But...

If you want EUC_JP (Japanese + ASCII) then use that as your backend encoding, not UTF-8 (unicode).
UTF-8 encoded databases are very useful for representing multiple languages in the same database,
but this usefulness vanishes if functions like upper/lower doesn't work correctly.

So optimizing for 3 languages breaks more than a hundred, that's doesn't seem fair!

>
> --
> Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>) "La principal
> característica humana es la tontería"
> (Augusto Monterroso)
>
>

... John

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2005-05-08 05:13:42 Can we get patents?
Previous Message Alvaro Herrera 2005-05-08 04:48:33 Re: Patch for collation using ICU