> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 20 October 2003 10:07
> To: Albin Blaschka
> Cc: 'pgadmin-support@postgresql.org'; Reinhard Resch; Wilhelm Graiss
> Subject: Re: [pgadmin-support] German umlauts in pgadmin III
>
> Umlaute are no ascii chars, so they can't converted to unicode.
> V1.0.1 which was released some days ago has a workaround for
> miscoded databases, leaving encoding conversions to the
> client if the db is created SQL_ASCII.
I just ran into this on my system with the £ symbol (UK Pound symbol, not #), however the fix doesn't seem to work in
CVStip - Any column that contains a £ value anywhere in it shows up as having a null value. At very least I would
expectto see an 'unknown char' symbol in place of the pound sign, and the rest of the string intact.
Regards, Dave.