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

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.
Дата
Msg-id 6CDA7879-9656-44F8-A8CC-D1B2B4240145@hagander.net
обсуждение исходный текст
Ответ на Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.  (Hiroshi Inoue <inoue@tpf.co.jp>)
Список pgsql-hackers
On 25 nov 2008, at 05.00, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Hiroshi Inoue <inoue@tpf.co.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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Pavel Stehule"
Дата:
Сообщение: Re: WIP: default values for function parameters
Следующее
От: "Fujii Masao"
Дата:
Сообщение: Re: How should pg_standby get over the gap of timeline?