> Hello,
>
> Thanks for all the answers, I solved the problem with "converting" my
> databases to Latin1...
> (dumping the data, dropping the DB, recreate it with Latin1, reloading
> data)
>
> Was quite an effort, but did it and without problems...
>
> BTW: PGAdmin III, V1.01 did *not* work in that case (displaying german
> umlaute properly...)
>
> Thanks,
> Albin
>
> --
> ************************************************************************
> ** Albin Blaschka, Mag. rer. nat.
> ** BAL Gumpenstein
> ** Projekt: Landschaft und Landwirtschaft im Wandel
> ** Tel.: 03682 / 22451 - 244
> ** No trees were killed in the creation of this message.
> ** However, many electrons were terrible inconvenienced.
> ************************************************************************
>
>
>
>
>
> ----------
> Von: Dave Page[SMTP:dpage@vale-housing.co.uk]
> Gesendet: Mittwoch, 22. Oktober 2003 13:28
> An: Andreas Pflug; Albin Blaschka
> Cc: pgadmin-support@postgresql.org; Reinhard Resch; Wilhelm Graiss
> Betreff: RE: [pgadmin-support] German umlauts in pgadmin III
>
>
>
> > -----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 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.
>
>
