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

From Takahiro Itagaki
Subject Re: UTF-8 encoding failure
Date
Msg-id 20100326110648.9F68.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: UTF-8 encoding failure  ("Hiroshi Saito" <z-saito@guitar.ocn.ne.jp>)
Responses Re: UTF-8 encoding failure  (Martin Schäfer <Martin.Schaefer@cadcorp.com>)
List pgsql-bugs
"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: Tom Lane
Date:
Subject: Re: BUG #5389: Column order on dump/reload broken from defined setof function
Next
From: Martin Schäfer
Date:
Subject: Re: UTF-8 encoding failure