You *can* use unicode, if you set the client encoding to a codeset your machine supports (might be Latin9). SQL_ASCII looks convenient, but when it comes to multilanguage it's a real pain, so it's better to designate what the data really is.Dear Jean-Michel, I'm succeeded to subscribe this list. Thank you.
You can register the support mailing list from:Done.
http://www.pgadmin.org/pgadmin3/support.php#support_list
The euro display problem is an encoding problem. The euro sign is not partof
an ASCII database. Whenever you would like Euro support, choose:To tell the truth it wasn't what I wnated. Actually I can insert the euro
Database->Create Database and select dropdown menu:
Latin9 (Iso-8859-15) or Unicode encoding.
sign via ODBC using pure SQL_ASCII encoding. PGAdmin can display the euro
sign. The only problem is that it can't display which was inserted with it.
I can't use unicode encoding, because the client machines are win9x which
does not support unicode (as far as I know). It's not a crucial problem, but
it's an inconvenience.
Regards, Andreas
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org