Re: German umlauts in pgadmin III

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "Albin Blaschka" <Albin(dot)Blaschka(at)bal(dot)bmlfuw(dot)gv(dot)at>
Cc: <pgadmin-support(at)postgresql(dot)org>, "Reinhard Resch" <Reinhard(dot)Resch(at)bal(dot)bmlfuw(dot)gv(dot)at>, "Wilhelm Graiss" <Wilhelm(dot)Graiss(at)bal(dot)bmlfuw(dot)gv(dot)at>
Subject: Re: German umlauts in pgadmin III
Date: 2003-10-22 11:28:51
Message-ID: 03AF4E498C591348A42FC93DEA9661B84C5C14@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 20 October 2003 10:07
> To: Albin Blaschka
> Cc: 'pgadmin-support(at)postgresql(dot)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 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.

Browse pgadmin-support by date

  From Date Subject
Next Message Tino Wildenhain 2003-10-22 11:31:15 Re: Execute TO in PgadminIII
Previous Message Gaetano Mendola 2003-10-22 10:47:28 Re: Execute TO in PgadminIII