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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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
From | Date | Subject | |
---|---|---|---|
Next Message | cvs | 2004-11-17 10:37:08 | CVS Commit by andreas: fix pg_dump option, some TODO updates |
Previous Message | Hiroshi Saito | 2004-11-17 06:27:12 | Mistake of the pg_dump option |