Hi.
----- Original Message -----
From: "ITAGAKI Takahiro" <[EMAIL PROTECTED]>
"Hiroshi Saito" <[EMAIL PROTECTED]> wrote:
Ah Ok, Please check it.
Your patch looks useful to prevent mismatch of encoding and locale on Windows,
but I found there is a limitation that user will not able to specify locale.
I added an alternative of nl_langinfo(CODESET) for Win32.
Please check following commands:
initdb --encoding=EUC_jp --locale=Japanese_Japan.932
vs.
initdb --encoding=EUC_jp --locale=Japanese_Japan.20932
One problem is that user need to know codepage numbers. It might
be possible to replace the default codepage to server encodings
automatically if we have a mapping table from encoding to codepage.
Yes, I think your approach looks very good. Then, It seems that it is necessary
to consider an original initial value problem again. I consider a document publication
or management. Anyway, Thanks.
Regards,
Hiroshi Saito
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
