From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Locale + encoding combinations |
Date: | 2007-10-12 11:53:18 |
Message-ID: | 470F602E.9060800@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote
> That still leaves us with the problem of how to tell whether a locale
> spec is bad on Windows. Judging by your example, Windows checks whether
> the code page is present but not whether it is sane for the base locale.
> What happens when there's a mismatch --- eg, what encoding do system
> messages come out in?
I'm not sure how to test that specifically, but it seems that accented
characters simply fall back to their undecorated equivalents if the
encoding is not appropriate, eg:
Dave(at)SNAKE:~$ ./setlc French_France.1252
Locale: French_France.1252
The date is: sam. 01 of août 2007
Dave(at)SNAKE:~$ ./setlc French_France.28597
Locale: French_France.28597
The date is: sam. 01 of aout 2007
(the encodings used there are WIN1252 and ISO8859-7 (Greek)).
I'm happy to test further is you can suggest how I can figure out the
encoding actually output.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2007-10-12 12:00:31 | Re: Locales and Encodings |
Previous Message | Gokulakannan Somasundaram | 2007-10-12 11:50:20 | Re: Including Snapshot Info with Indexes |