Skip site navigation (1) Skip section navigation (2)

Re: UNICODE isn't expressed.(pg_dump,pg_restore)

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Hiroshi Saito <saito(at)inetrt(dot)skcapi(dot)co(dot)jp>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: UNICODE isn't expressed.(pg_dump,pg_restore)
Date: 2004-11-17 10:29:56
Message-ID: 419B2824.5000703@pse-consulting.de (view raw or flat)
Thread:
Lists: 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

In response to

pgadmin-hackers by date

Next:From: cvsDate: 2004-11-17 10:37:08
Subject: CVS Commit by andreas: fix pg_dump option, some TODO updates
Previous:From: Hiroshi SaitoDate: 2004-11-17 06:27:12
Subject: Mistake of the pg_dump option

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group