Tom Lane wrote: > Magnus Hagander <[EMAIL PROTECTED]> 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?
I'm afraid I don't understand what you mean exactly. AFAIK the output encoding of Windows gettext is detemined by the ANSI system code page which is usualy CP932(Shift_JIS) in Japan and unrelated to the locale settings. In addition CP20932 is rarely used in Japan IIRC. I've never used it and don't know what it is correctly (maybe a kind of EUC_JP). regards, Hiroshi Inoue -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
