From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: [ODBC] pgAdmin2 UTF-8 support |
Date: | 2002-02-25 09:02:48 |
Message-ID: | FED2B709E3270E4B903EB0175A49BCB10475FA@dogbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 25 February 2002 08:51
> To: Dave Page
> Cc: pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] [ODBC] pgAdmin2 UTF-8 support
>
>
> > OK, what about if you select the data back in pgAdmin -
> does it then
> > display it?
> Sure, it does. This is a new feature of PostgreSQL 7.2.
>
> > Also, does SET CLIENT_ENCODING SQL_ASCII; work?
> No it does not. "é" is stored as 'i'.
So, to get this straight in my non multilingual brain, if you set client
encoding to latin1 then european charsets (i.e. latin based) work perfectly
in pgAdmin?
So probably we need to _at least_ do something similar for Japanese/Hebrew
etc...
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Jean-Michel POURE | 2002-02-25 09:14:43 | Re: [ODBC] pgAdmin2 UTF-8 support |
Previous Message | Jean-Michel POURE | 2002-02-25 08:51:04 | Re: [ODBC] pgAdmin2 UTF-8 support |