"Hiroshi Saito" <[EMAIL PROTECTED]> wrote:
> regression test surely goes wrong.!
This fix does nothing against the regression failure.
It is probably reasonable to choose UTF-8 as a server encoding when we cannot
support the encoding of the current locale. A remaining issue is which we
should use no-locale, locale of another encoding, or reporting error then.
At least on Windows, locale of another encoding works correctly because
we've already had some Windows-specific hacks. (try grep MultiByteToWideChar)
In fact, we can accept options like:
initdb -E UTF8 --locale=Japanese_Japan.932 -- CP932 is SJIS in nature
I'll suggest to use UTF8 if the encoding is UTF-8 or NOT specified and
we don't support the locale encoding on Windows, i.e. locale is always
enabled on regression tests.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
