Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-user@jakarta.apache.org
From: =?iso-8859-2?Q?Marcin_Jasku=B3a?= <jaskula@expro.pl>
To: <tomcat-user@jakarta.apache.org>
Subject: RE: Problem with page encoding for ISO-8859-2
Date: Mon, 20 Aug 2001 21:00:14 +0200
Message-ID: <OPEALAGDNEGGDPPBOINMEEEKCAAA.jaskula@expro.pl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: 8bit
Importance: Normal
In-Reply-To: <NDBBLDFNNODMICGNKHGICECFNLAA.martin@isallineed.org>

Hi

Yes, the data in the dB are stored as Latin2 so it should be the same like
for ISO-8859-2.
There was no this problem with JServ so the problem is in encoding the data
by Tomcat (I think).

Moreover, Tomcat writes new data to the dB changing characters to the
Unicode:
� -> &#322;   (6 characters!!!)
so I cannot sort the data now in the SQL!

Marcin

>-----Original Message-----
>From: Martin van den Bemt [mailto:martin@isallineed.org]
>Sent: Monday, August 20, 2001 8:42 PM
>To: tomcat-user@jakarta.apache.org
>Subject: RE: Problem with page encoding for ISO-8859-2
>
>
>
>- Is the data in the db stored as ISO-8859-2 ? (looks like it is stored is
>8859-1)
>- Use UTF-8 to store the data, this way you can use UTF-8 as well
>as the ISO
>content type that corresponds with the data.
>
>If you gonna use utf 8 and run into a lot of MalformedInputExceptions you
>can be sure that the data is stored as 8859-1..
>
>Mvgr,
>Martin
>