Re: UNICODE isn't expressed.(pg_dump,pg_restore) - Mailing list pgadmin-hackers

From Andreas Pflug
Subject Re: UNICODE isn't expressed.(pg_dump,pg_restore)
Date
Msg-id 419B2824.5000703@pse-consulting.de
Whole thread Raw
In response to UNICODE isn't expressed.(pg_dump,pg_restore)  ("Hiroshi Saito" <saito@inetrt.skcapi.co.jp>)
List pgadmin-hackers
Hiroshi Saito wrote:
> Hi Andreas.
>
> I think how to solve this problem.
>
> case1)
> postgresql.conf-> # client_encoding =  this is comment out;
> Then, pg_dump is discharged with server_encoding.
>
> case2)
> postgresql.conf-> client_encoding = UNICODE
> Then, pg_dump is discharged with UNICODE.
> This case is to see this.
> http://cre-ent.skcapi.co.jp/~saito/pgadmin3/pga_dmp.jpg

ExternProcessDialog expects any program's output to be in the machine's
charset, but in the case of pg_dump it may be Unicode. This isn't fixed
too easy, because charset translation is performed in a base class.
I've put it on the TODO list for 1.3.

Regards,
Andreas

pgadmin-hackers by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Mistake of the pg_dump option
Next
From: cvs@cvs.pgadmin.org
Date:
Subject: CVS Commit by andreas: fix pg_dump option, some TODO updates