From: | "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp> |
---|---|
To: | "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de> |
Cc: | <jm(dot)poure(at)freesurf(dot)fr>, <pgadmin-hackers(at)postgresql(dot)org>, "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Subject: | Re: pgadmin3 clientencoding |
Date: | 2003-06-10 18:37:05 |
Message-ID: | 020801c32f7f$4ad522e0$1f324d80@w2k |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Andreas.
----- Original Message -----
From: "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>
To: <jm(dot)poure(at)freesurf(dot)fr>; <pgadmin-hackers(at)postgresql(dot)org>; "Dave Page"
<dpage(at)vale-housing(dot)co(dot)uk>
Sent: Tuesday, June 10, 2003 11:41 PM
Subject: Re: [pgadmin-hackers] pgadmin3 clientencoding
> Jean-Michel POURE wrote:
(snip)
> >
> >Therefore, pgAdmin3 shall manage encodings transparently. This is a
***key
> >feature***. Don't get me wrong, I propose to:
> >
> >1) Always compile pgAdmin3 with Unicode support. (By the way, I would
also be
> >delighted if all .po files were stored in UTF-8).
> >
> Yes.
No, it thinks that should be an option.
(snip)
> >PostgreSQL is the only database in the world with such on-the-fly
conversion
> >at data stream level. So why not use it.
> >
> >3) We only need to check whether the data entered in the grid can be (a)
> >converted from UTF-8 into the database encoding and (b) back from the
> >database encoding into Unicode.
> >
> Yes.
This agrees.
But, time is necessary.
(snip)
With kindest regards,
Hiroshi-Saito
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2003-06-10 19:04:16 | Re: PostgreSQL presentation at LSM |
Previous Message | Jean-Michel POURE | 2003-06-10 18:04:53 | Re: configuration script problem |