Re: UTF-8 encoding failure - Mailing list pgsql-bugs

Hi Martin-san.

I prepared the environment which was alike in order to reproduce your problem.
And a very comfortable result is obtained.
http://winpg.jp/~saito/PGSQL_SJIS/InternationalVersionWindows/

Probably some of Japanese language setup is lacking.

Regards,
Hiroshi Saito

----- Original Message -----
From: "Hiroshi Saito" <z-saito@guitar.ocn.ne.jp>


> Hi.
>
> Ummm, it is very strange....
> Can you do chcp command?
>
> C:\home\HIROSHI>chcp 932
> 現在のコード ページ: 932
>
> Anyway,  I want to prepare and check the same environment as you.
> It may be that there is a shortage of environment for changing some.
> the following things , but, It is hard to consider a problem...
> http://download.microsoft.com/download/6/2/e/62e61f10-e106-4f4c-a862-63eec2b41efb/readme.htm
> However, time is required.
>
> Regards,
> Hiroshi Saito
>
> ----- Original Message -----
> From: "Martin Schäfer" <Martin.Schaefer@cadcorp.com>
>
>
>> Okay, got it now.
>>
>> Unfortunately, the output is exactly the same as before:
>>
>> G:\Test\TestPostgreSQLJapanese>PostgreSQLJapaneseSJIS.exe localhost 5432 dev308 postgres
>> postgres
>> localhost 5432 dev308 postgres postgres
>> Testing with encoding UTF-8:
>> NOTICE:  CREATE TABLE will create implicit sequence "蝗帛ｮ誉gid_seq" for serial column "蝗帛ｮ・gid"
>> NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "蝗帛ｮ誉pkey" for table "蝗帛ｮ・
>> PQfname(pResult, 4) returned incorrect field name.
>> PQfname(pResult, 5) returned incorrect field name.
>> PQfname(pResult, 6) returned incorrect field name.
>>
>> Testing with encoding SJIS:
>> NOTICE:  CREATE TABLE will create implicit sequence "四宗_gid_seq" for serial column "四宗.gid"
>> NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "四宗_pkey" for table "四宗"
>> Query failed with error:
>> ERROR:  invalid byte sequence for encoding "UTF8": 0xe59eff
>> HINT:  This error can also happen if the byte sequence does not match the encoding
>> expected by the server, which is controlled by "client_encoding".
>>
>> I'm beginning to believe that the problem is indeed in the combination of UK English
>> operating system with Japanese locale. Maybe someone else could test this combination?
>>
>> Regards,
>>
>> Martin
>