| From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: setlocale() on Windows doesn't work correctly if the locale name |
| Date: | 2011-04-20 21:39:42 |
| Message-ID: | 4DAF529E.7000107@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
(2011/04/20 22:08), Tom Lane wrote:
> Hiroshi Inoue<inoue(at)tpf(dot)co(dot)jp> writes:
>> In my environment (Windows Vista using VC8)
>
>> setlocale(LC_XXXX, "Chinese (Traditional)_MCO.950");
>> works and
>> setlocale(LC_XXXX, NULL);
>> returns
>> Chinese (Traditional)_Macao S.A.R..950
>> but
>> setlocale(LC_XXXX, "Chinese (Traditional)_Macao S.A.R..950");
>> fails.
>
> Interesting. This example suggests that maybe Windows' setlocale can
> only cope with dot as introducing a codepage number.
ACP or OCP as well as codepage number seem to be allowed.
> Are there any
> cases where a dot works as part of the basic locale name?
Unfortunately I don't know any explanation how dots are allowed.
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2011-04-20 21:40:47 | Re: Re: [COMMITTERS] pgsql: setlocale() on Windows doesn't work correctly if the locale name |
| Previous Message | Peter Eisentraut | 2011-04-20 20:23:35 | pgsql: Fix PL/Python traceback for error in separate file |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2011-04-20 21:40:47 | Re: Re: [COMMITTERS] pgsql: setlocale() on Windows doesn't work correctly if the locale name |
| Previous Message | Tom Lane | 2011-04-20 21:29:20 | Re: pgindent weirdness |