Re: 5.0.16 and 5.0.18 international character support

Antonio Fiol Bonnín Fri, 20 Feb 2004 08:26:08 -0800

What Adam said was:
Look in the response headers to see it.

I think he *really* meant the response headers, not the html code.

To do that on IE, you need a plugin called ieHTTPheaders or something like that.

On Netscape/Mozilla, use LiveHTTPHeaders.

Otherwise, if you are not on HTTPS, you can use a network sniffer.

Antonio Fiol

Trygve Hardersen wrote:

Thanks for the reply. Project never ran on 4.x, developed on 5.x starting
from 5.0.14. Using JSTL 1.1.
5.0.14:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; lang="en" xml:lang="en">
<meta http-equiv="Content-Type" content="application/xhtml+xml;
charset=utf-8" />
5.0.18:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; lang="en" xml:lang="en">
<meta http-equiv="Content-Type" content="application/xhtml+xml;
charset=utf-8" />
That is equal. However, the characters æøå are in plain text in the page,
but IE displays them incorrectly. I can't find any difference in the source
of the pages between 5.0.14 and later, which makes me wonder if the problem
is IE oriented. Thing is though, that IE displays everything correct on
5.0.14..... Installing Netscape now, Opera does not support xhtml with
script elements. Idea?
milx

-----Original Message-----
From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Friday, February 20, 2004 2:43 PM
To: Tomcat Users List
Subject: Re: 5.0.16 and 5.0.18 international character support

On 02/20/2004 01:17 PM Trygve Hardersen wrote:

I'm having a silly problem with 5.0.16 and 5.0.18, regarding the
Scandinavian characters æ, ø and å (probably others to). I've developed a
project using tomcat and struts, where both message resources and actual
data in the database contain these characters. Using 5.0.14 and prior,

I've

not paid attention to the characters; just used plain text for both
resources and data. This has worked out just fine, regardless of user

locale

(and thereby the lang option of the page), the characters have been

rendered
properly. Attempting to stay up-to-date, I upgraded to 5.0.16 and later
5.0.18, but now the characters are Chinese-like (unreadable for a
Scandinavian). Anyone knows the cause of this?
The pages are all UTF-8, xhtml and there is no difference in handling of
message resources and model data.
Are you sure about that? Could it be that you actually did have this problem with tomcat 5.0.x but just didn't notice? When did you upgrade from tomcat 4.x?

There are issues going from tomcat 4 to 5 that could affect this, but none that I know of, just from 5.0.14 -> 16.

Check the character encoding of your pages in the browser. Look in the response headers to see it. What is it & what do you want it to be?

Adam

smime.p7s
Description: S/MIME Cryptographic Signature

Re: 5.0.16 and 5.0.18 international character support

Reply via email to