Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, Hiroshi Saito <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
Subject: Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.
Date: 2008-11-25 06:00:02
Message-ID: 6CDA7879-9656-44F8-A8CC-D1B2B4240145@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 25 nov 2008, at 05.00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> writes:
>> Tom Lane wrote:
>>> If that's true then this code is presently broken for *every* locale
>>> under Windows, not only Japanese.
>
>> Maybe there are a few languages/countires where 2 encodings are
>> widely used.
>
> UTF8 vs Latin-N?

We already special-cases utf8...

I think the thing us that as long as the encodings are compatible
(latin1 with different names for example) it worked fine.

> In any case I think the problem is that gettext is
> looking at a setting that is not what we are looking at. Particularly
> with the 8.4 changes to allow per-database locale settings, this has
> got to be fixed in a bulletproof way.
>

Agreed.

/Magnus

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2008-11-25 11:49:35 pgsql: If pg_ctl stop fails, print an error message and exit (instead of
Previous Message Tom Lane 2008-11-25 04:00:18 Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2008-11-25 06:54:21 Re: How should pg_standby get over the gap of timeline?
Previous Message Pavel Stehule 2008-11-25 05:23:29 Re: WIP: default values for function parameters