| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <andreas+pg(at)gate450(dot)dyndns(dot)org>, <masm(at)fciencias(dot)unam(dot)mx>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: localization problem (and solution) |
| Date: | 2005-12-21 16:08:00 |
| Message-ID: | 34077.68.143.134.146.1135181280.squirrel@www.dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane said:
> Andreas Seltenreich <andreas+pg(at)gate450(dot)dyndns(dot)org> writes:
>> I'm afraid having LC_ALL in the environment at this time would still
>> do the wrong thing on setlocale(LC_ALL, ""); since a LC_ALL
>> environment variable overrides the other categories.
>
> Doh, of course, I was misremembering the precedence. So we need
> LANG=C
> LC_ALL unset (probably LANGUAGE too, for glibc)
> others as stated
>
We need to test any solution carefully on Windows, which deals with locales
very differently from *nix, and where we still have some known locale issues
(see recent discussion).
I wonder if the complained of behaviour is triggered by our recent changes
to support utf8 in pl/perl?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-12-21 16:34:12 | Re: localization problem (and solution) |
| Previous Message | Tom Lane | 2005-12-21 16:04:08 | Re: localization problem (and solution) |