Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 11:19 PM
> To: John Hansen
> Cc: alvherre@dcc.uchile.cl; pgman@candle.pha.pa.us;
> girgen@pingpong.net; pgsql-hackers@postgresql.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.
> > >
> > > I'm just curious if Germany/French/Spanish mixed text can
> be sorted
> > > correctly. I think these languages need their own locales
> even with
> > > UNICODE/ICU.
> >
> > No, they will not sort correctly, for that you still need
> the locale.
>
> I'm confused. I thought the ICU patches is intended for using
> on broken locale platforms?
Initially yes, but why duplicate code?
What I meant was, that they will not sort correctly using the C locale.
Locale _name_ needs to be known to ICU for it to sort correctly.
> --
> Tatsuo Ishii
>
>
