Re: Encoding conversion problem

Hi Lew,

> I uinderstand my confusion now - it stemmed from the phrase "the
encoding of
> the JVM".  The JVM itself only uses one encoding; it translates to and
from
> other encoding on I/O.  So to make sure I understood you correctly, were
you
> referring to the encoding specified by the I/O call?
Maybe I don't understand :-(
In my posts I tried to specify the encoding of the DBMS and the JVM
encoding (i.e. the system property file.encoding) in the different
cases and, as you stated, the JVM performs the necessary translations.
In my JDBC calls I don't specify/force any encoding.


> Generally if the encoding you specify for I/O is different from the
encoding
> in your data store, it will cause trouble.  This is not limited to Java.
 Over
> in the Postgres newsgroups one finds people have trouble with character
> encoding from all sorts of platforms, mostly stemming from trying to
store
> characters in a column that are not part of the specified character
encoding
> for the DB.  If such things don't match, then problems will hatch.
I disagree...
For our application we keep the DBMS with a fixed encoding and the
application performs the necessary conversions. For instance for
polish installations we use an ISO-8859-1 database and an application
server configured with ISO-8859-2 where we store polish characters
without problems.

Andrea