Horton

Re: Re: [COMMITTERS] pgsql: setlocale() on Windows doesn't work correctly if the locale name

Hiroshi Inoue <inoue@tpf.co.jp>

View thread
From: Hiroshi Inoue <inoue@tpf.co.jp>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, Heikki Linnakangas <heikki.linnakangas@iki.fi>, pgsql-hackers@postgresql.org
Date: 2011-04-20T21:39:42Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. setlocale() on Windows doesn't work correctly if the locale name contains

(2011/04/20 22:08), Tom Lane wrote:
> Hiroshi Inoue<inoue@tpf.co.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