Re: Problems with charsets, investigated...

Well, thanx for the info, but i doubt that it's the problem. I do a debug
output (in command line, therefore not thru tomcat), after just getting
the data from Enhydra's DODS (relational-object layer).
So either the bug's in DODS (but why then it didn't show up with all
previous versions ?), or it's sthg in the JDBC driver. For looking thru
DODS' templates, i know that no copy is made (i mean there's no getBytes()
involved) so the problem shouldn't be here...

Thanx for your clue though, it's interesting to know !

Alexandre Aufrere

----------------------------------------------------
De : Jan de Visser <jdevisser(at)digitalfairway(dot)com>
A : pgsql-jdbc(at)postgresql(dot)org
Objet : Re: [JDBC] Problems with charsets, investigated...
Date : Sat, 7 Aug 2004 23:12:36 -0400
> On August 7, 2004 10:29 pm, Oliver Jowett wrote:
> > > 6) Our web app choses to display Java Strings accordingly to
> > > file.encoding, therefore as ISO-8859-1
> > > 7) Bing ! problem: we are now interpreting UTF8-encoded strings (see
> > > point 2/3) as ISO-8859-1
> > > Therefore all the accentuated characters go wrong !
> >
> > This implies that your web app is not transcoding correctly from
UTF-16
> > (internal string representation) to ISO-8859-1.
> >
> > How does your web app use file.encoding exactly? Note that the
> > file.encoding property does *not* control the default encoding used by
> > String.getBytes(), as I understand it; the default eencoding is
> > JVM-controlled from the system's locale settings.
>
> Hrm. This rings a bell. We use JBoss 3.2.3, which ships with a broken
tomcat.
> That particular tomcat version hardcodes a transcoding to LATIN1. Caused
us a
> lot of hair-pulling, and we fixed it by patching the offending code in
tomcat
> (in coyote, actually). This is the README in our lib-hacks CVS dir:
>
> "
> This directory contains a patch for tomcat/coyote 4.1.29 as shipped with
jboss
> 3.2.3. It will set the default encoding to UTF-8 as opposed to
ISO-8859-1,
> and will set the encoding on the query string as well as on the request
body.
>
> The build script will compile the patched files, and add the patched
classes
> to the tomcat jars stored in jboss/server/deploy/jbossweb-tomcat41.sar.
> "
>
> Could this be his problem?
>
> JdV!!
>
> --
> --------------------------------------------------------------
> Jan de Visser jdevisser(at)digitalfairway(dot)com
>
> Baruk Khazad! Khazad ai-menu!
> --------------------------------------------------------------
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings