Thanks very much for your help.
You are right its UTF-8.
I have tried all "SET CLIENT_ENCODING TO '*'" but nothin worked.
There is an error and i don't find it.
PGAdmin III (also on Windows) works fine so i am testing now what encoding PGAdmin III is using.
I have set up the debugging and PGAdmin says that it is using the SQL_ASCII encoding. All the Umlauts are there. This
isreally curious.
I am too tired to find the error today and go home now.
Thanks for any help
Best regards
Gunnar
-----Ursprüngliche Nachricht-----
Von: Benjamin Riefenstahl [mailto:Benjamin.Riefenstahl@epost.de]
Gesendet: Donnerstag, 4. Dezember 2003 15:37
An: Gunnar Groetschel
Cc: Pgsql-Odbc (E-Mail)
Betreff: Re: PLEASE: I really need german characters
Hi Gunnar,
"Gunnar Groetschel" <ggroetschel@sokoma.de> writes:
> If i use the odbc driver i see only sh** (Möller should be Müller).
That looks like UTF-8.
> psql -l shows me, that the database is in SQL_ASCII (what should be
> ok - after 2 hours reading manual pages).
I haven't read the manual for this, but strictly speaking "ASCII"
means, that you don't have umlauts at all, or rather that their
encoding is undefined. Which is not good for a stable database,
because with any update of any tool, that tool can change its internal
default interpretation and potentially start corrupting data. You
really do want a database encoding that supports your data explicitly.
Some ODBC-based tools let you configure how to encode data going in
and out of the ODBC API. Also in the past I have had success with
issuing
SET CLIENT_ENCODING TO 'UNICODE'
on the connection once to get the data in UTF-8. You may want to see,
if a similar statement can be used to change the DB interface encoding
to Latin-1 or Windows-1252.
benny