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

From Hiroshi Saito
Subject Re: UTF-8 encoding failure
Date
Msg-id DDA13DC46C09430C8F2703CB4ADE01E9@acer08f817a9b5
Whole thread Raw
In response to UTF-8 encoding failure  (Martin Schäfer <Martin.Schaefer@cadcorp.com>)
Responses Re: UTF-8 encoding failure  (Martin Schäfer <Martin.Schaefer@cadcorp.com>)
List pgsql-bugs
Hi Martin-san.

Umm, I sent what corrected some of your TestPostgreSQLJapanese.cpp.
http://archives.postgresql.org/pgsql-bugs/2010-03/msg00188.php
Did you use it?

Regards,
Hiroshi Saito

----- Original Message -----
From: "Martin Schäfer" <Martin.Schaefer@cadcorp.com>


> Unfortunately there are encoding problems on my machine. I'm getting this output:
>
> Testing with encoding UTF-8:
> 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:
> 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".
>
> Instead of a Japanese OS, I used an English (UK) OS and set the system locale to Japanese,
> but that should be good enough I think.
> I also used a new install of PostgreSQL, with only the PostGIS module added.
>
> Okay, I find it difficult to imagine that a bug like this would not have been found
> before. But if it works fine on your machines, why doesn't it work on my machine?
>
> Regards,
>
> Martin Schäfer
> Principal Software Engineer
> Cadcorp
> Computer Aided Development Corporation Ltd.
> 1 Heathcock Court, London, WC2R 0NT
> martin.schaefer@cadcorp.com
> www.cadcorp.com
>
>> -----Original Message-----
>> From: Takahiro Itagaki [mailto:itagaki.takahiro@oss.ntt.co.jp]
>> Sent: Friday, March 26, 2010 3:07 AM
>> To: Martin Schäfer; Hiroshi Saito
>> Cc: pgsql-bugs@postgresql.org
>> Subject: Re: [BUGS] UTF-8 encoding failure
>>
>> "Hiroshi Saito" <z-saito@guitar.ocn.ne.jp> wrote:
>> > Probably it is not a bug.
>> >
>> > Testing with encoding UTF-8:
>> > NOTICE:  CREATE TABLE will create implicit sequence
>> "蝗帛ョ誉gid_seq" for serial column "蝗帛ョ・gid"
>> > Testing with encoding SJIS:
>> > NOTICE:  CREATE TABLE will create implicit sequence
>> "四宗_gid_seq" for serial column "四宗.gid"
>>
>> > From: "Martin Schafer" <Martin.Schaefer@cadcorp.com>
>> > - UTF8: does not return the same column name used to create
>> the table.
>>
>> Yeah, there are no encoding problems in libpq and postgres,
>> but you need to print NOTICE messages in the same codepage
>> with your console.
>> You probably need to replace routines to display NOTICE
>> messages in libpq.
>> PQsetNoticeReceiver() would be a help.
>>
>> Or, you could just change the codepage of your console to UTF-8.
>> However, there is a known problem in Windows console that console with
>> UTF-8 codepage cannot display any kanji characters. I'm not
>> sure what we can do to fix it ... some font settings in the registory?
>>
>> Regards,
>> ---
>> Takahiro Itagaki
>> NTT Open Source Software Center
>>
>>
>>
>>

pgsql-bugs by date:

Previous
From: "sachin"
Date:
Subject: BUG #5392: Query Optimization
Next
From: Martin Schäfer
Date:
Subject: Re: UTF-8 encoding failure