Re: Unicode upper() bug still present

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unicode upper() bug still present
Date: 2003-10-20 18:12:10
Message-ID: 1066673530.5434.13.camel@fuji.krosing.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut kirjutas E, 20.10.2003 kell 21:02:
> Tom Lane writes:
>
> > I noticed by chance that glibc has a "reentrant locale" API that seems
> > to allow for efficient access to multiple locales concurrently. Perhaps
> > it would be a reasonable solution to support multiple locales only on
> > machines that have this library. If we have to write our own locale
> > support it's likely to be a long time coming :-(
>
> Naturally, I cannot promise anything, but this is at the top of my list
> for the next release. I already have sorted out the specifications and
> algorithms and collected locale data for most corners of the world, so
> it's just the coding left.

Have you checked ICU ( http://oss.software.ibm.com/icu/ ) ?

It seems to have all the needed data at least.

> Unfortunately, a real, sustainable fix of this
> situations requires us to start at the very bottom, namely the character
> set conversion interface, then the gettext interface, then the new locale
> library, then integrating the per-column granularity into the
> parser/planer/executor. So you may be looking at a two-release process.

---------------
Hannu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message ivan 2003-10-20 18:56:05 how to put passwd ?
Previous Message Peter Eisentraut 2003-10-20 18:02:12 Re: Unicode upper() bug still present