From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Locale + encoding combinations |
Date: | 2007-10-10 14:08:36 |
Message-ID: | 470CDCE4.4010009@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Dave Page <dpage(at)postgresql(dot)org> writes:
>> Tom Lane wrote:
>>> Are you certain that that acceptance actually represents support?
>>> Have you checked that it rejects combinations involving real code
>>> pages (ie, NOT 65001) that don't really work with the locale?
>
>> It fails with ones that Microsoft have decided don't belong in my
>> language group and therefore aren't installed. It accepts all the others
>> I've tried, but then from the sample I've looked, they all have
>> 0-9a-zA-Z in them so I guess they're all capable of handling English.
>
> That doesn't exactly fill me with confidence. Maybe you need to make
> some tests involving a non-English base locale?
Hmm, I'm guessing these probably shouldn't work:
Dave(at)SNAKE:~$ setlc "Japanese_Japan.28605"
Japanese_Japan.28605
Dave(at)SNAKE:~$ setlc "Japanese_Japan.28595"
Japanese_Japan.28595
Dave(at)SNAKE:~$ setlc "Russian_Russia.1252"
Russian_Russia.1252
Dave(at)SNAKE:~$ setlc "Russian_Russia.28591"
Russian_Russia.28591
1252 == WIN1252
28591 == LATIN1
28605 == LATIN9
28595 == ISO8859-5 (Cyrillic)
28597 == ISO8859-7 (Greek)
In fact, it looks like it'll allow me to use anything thats installed,
regardless of whether they're liekly to be compatible. So much for
trusting setlocale() :-(
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-10-10 14:09:53 | Re: Locale + encoding combinations |
Previous Message | Aidan Van Dyk | 2007-10-10 14:05:30 | Re: Timezone database changes |