ITAGAKI Takahiro wrote:
Hiroshi Inoue <[EMAIL PROTECTED]> wrote:
Please call setlocale(LC_CTYPE/LC_ALL, "") first.
Ah, it works! But setlocale(*, "") means that we always use platform
locale (Japanese and SJIS in Japan).
Maybe you can call setlocale(LC_CTYPE, ".20932") instead and you
would get CP20932 encoding. The encoding of LC_TIME or LC_MESSAGES
has little meaning.
> It could be different from server
encoding and locale in postgres. Is it acceptable? I think we need to
set LC_CTYPE and other LC_* independently...
Seems LC_CTYPE and LC_TIME should be convertible even though we use
wcsftime (which internally calls strftime?).
As for gettext(LC_MESSAGES) on Windows we can set LC_CTYPE independently
because it is unrelated to the output encoding. In addition we can call
bind_textdomain_codeset to change the output encoding.
I'm providing a patch to adjust the output encoding of Windows
gettext.
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
