Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use.
От | Tom Lane |
---|---|
Тема | Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use. |
Дата | |
Msg-id | 2830.1227543964@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Explicitly bind gettext() to the UTF8 locale when in use. (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext() to
the UTF8 locale when in use.
|
Список | pgsql-hackers |
Magnus Hagander <magnus@hagander.net> writes: > Hiroshi Inoue wrote: >> because Shift_JIS isn't allowed as a server encoding. So >> the Japanese Windows native message encoding Shift_JIS never >> matches the server encoding EUC_JP and a conversion between >> Shitt_jis and EUC_JP is necessarily needed. > Ah, so we're basically hardcoding that information? The system will go > up in SJIS, but since we can't deal with it, we switch it to EUC_JP? I'm not following this either. If the patch is really necessary then it seems it must be working around a bug in the Windows version of gettext, ie failure to distinguish CP932 from CP20932. Is that correct? > Ok, I think I understand. I've made some minor stylistic changes (we > don't normally use if (NULL != <whatever>) in the pg sources), and will > apply with those. It definitely needs a comment explaining why this is needed. regards, tom lane
В списке pgsql-hackers по дате отправления: