Hi Andreas.
- Original Message -
From: "Andreas Pflug" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Dave Page"
<[EMAIL PROTECTED]>
Sent: Tuesday, June 10, 2003 11:41 PM
Subject: Re: [pgadmin-hackers] pgadmin3 clien
Hi Andreas.
- Original Message -
From: "Andreas Pflug" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Dave Page" <[EMAIL PROTECTED]>
Sent: Tuesday, June 10, 2003 6:11 PM
Subject: Re: [pgadmin-hackers] pgadmin3 clientencoding
> Andreas Pflug w
Jean-Michel POURE wrote:
I am absolutely sure that we cannot rely on recommandations, such as "create
UNICODE database for multi-byte data and SQL_ASCII otherwise".
Jean-Michel,
you got me wrong. Client encoding is only about the data transfer, and
that includes not only the transfer from the
Dear Andreas,
I don't know if I understand you well. If I don't, please disgard my message.
Here is my point of view:
> The longer I think about this, the more the current implementation
> appears wrong to me. The decisive factor is not a user's wish, but the
> ability of our charset conversion
Jean-Michel POURE wrote:
On Tuesday 10 June 2003 11:39, Andreas Pflug wrote:
OK, this means a client encoding per database is needed, right?
Additional property for database?
Yes. Whenever possible database, client and wxWindows encodings should be the
same. For example, the best solution
On Tuesday 10 June 2003 11:39, Andreas Pflug wrote:
> OK, this means a client encoding per database is needed, right?
> Additional property for database?
Yes. Whenever possible database, client and wxWindows encodings should be the
same. For example, the best solution is to have a full Unicode ch
Jean-Michel POURE wrote:
On Tuesday 10 June 2003 11:11, you wrote:
Do we really need special encodings, besides unicode? If so, this
should be implemented on a tree node (Server property: client
encoding) to make it possible to let the change of encoding have
immediate effect, or as the "System
On Tuesday 10 June 2003 11:11, you wrote:
> > Do we really need special encodings, besides unicode? If so, this
> > should be implemented on a tree node (Server property: client
> > encoding) to make it possible to let the change of encoding have
> > immediate effect, or as the "System Object" sett
Andreas Pflug wrote:
Do we really need special encodings, besides unicode? If so, this
should be implemented on a tree node (Server property: client
encoding) to make it possible to let the change of encoding have
immediate effect, or as the "System Object" setting is implemented.
There's anot
