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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
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 13:08:59
Message-ID: 24758.1303304939@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Hiroshi Inoue 2011-04-20 13:16:38 Re: Re: [COMMITTERS] pgsql: setlocale() on Windows doesn't work correctly if the locale name
Previous Message Bruce Momjian 2011-04-20 09:45:30 pgsql: Pg_upgrade C comment addition.

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2011-04-20 13:16:38 Re: Re: [COMMITTERS] pgsql: setlocale() on Windows doesn't work correctly if the locale name
Previous Message Jerry Sievers 2011-04-20 12:49:10 Re: time-delayed standbys