> -----Original Message-----
> From: Andreas Pflug [mailto:[EMAIL PROTECTED] 
> Sent: 20 October 2003 10:07
> To: Albin Blaschka
> Cc: '[EMAIL PROTECTED]'; 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 CVS tip - Any column that contains a £ value anywhere 
in it shows up as having a null value. At very least I would expect to see an 'unknown 
char' symbol in place of the pound sign, and the rest of the string intact.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to