Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hiroshi Inoue <inoue@tpf.co.jp>
Cc: Andrew Dunstan <andrew@dunslane.net>, Heikki Linnakangas <heikki.linnakangas@iki.fi>, pgsql-hackers@postgresql.org
Date: 2011-04-20T13:08:59Z
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

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.  Are there any
cases where a dot works as part of the basic locale name?

			regards, tom lane