John Hansen wrote:
> > --On l?rdag, maj 07, 2005 22.53.46 +1000 John Hansen
> > <john@geeknet.com.au>
> > wrote:
> >
> > > Errm,... initdb --encoding UNICODE --locale C
> >
> > You mean that ICU *shall* be used even for the C locale, and
> > not as Bruce suggested here:
>
> Yes, that's exactly what I mean.
There are two reasons for that optimization --- first, some locale
support is broken and Unicode encoding with a C locale crashes (not an
issue for ICU), and second, it is an optimization for languages like
Japanese that want to use unicode, but don't need a locale because
upper/lower means nothing in those character sets.
So, the first issue doesn't apply for ICU, and the second might not
depending on what characters you are using in the Unicode character set.
I guess I am little confused how ICU can do upper() when the locale is
C. What is it using to determine A is upper for a? Am I confused?
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073