Until now, our solution was indeed to put
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=windows-1256" />
into the html code. (----> Tomcat 4.1.24)
But since Tomcat 4.1.29, an encoding is always set in the HTTP header:
[Set-Cookie: JSESSIONID=8BAD9C0C001FAF4478B12B3A6323DB83; Path=/examples
, Content-Type: text/html;charset=windows-1256
, Content-Length: 65
, Date: Tue, 13 Jan 2004 16:45:42 GMT
, Server: Apache-Coyote/1.1
]
or similar.

If the browser finds a content type in the HTTP header, it
ignores the HTML header.

-Thomas





-----Original Message-----
From: Christopher Schultz [mailto:christopher.d.schultz@(protected)]
Sent: Mittwoch, 14. Januar 2004 15:16
To: Tomcat Users List
Subject: Re: problem with arabic in multilanguage jsp


Thomas,

> we are running a tomcat instance that uses common jsps for all languages.
If
> no encoding is set in the http-header tomcat 4.1.29 sets iso-8859-1 by
> default. Arabic users must then configure their browsers themselves
> (unacceptable).
>
> (1)
> If I set the encoding in the jsp like this:
> <%@(protected)"%>
> everything is fine. But as I told, our jsps are multilingual.
>
> (2)
> If I set the encoding in the jsp like this:
> <%
>  response.setContentType("text/html;charset=windows-1256");
> %>
> the results are just question marks. The same thing happens if the arabic
> text is not hardcoded in the jsp but comes from a varable.

Have you tried using:
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=windows-1256" />

Does this trigger the browser to display the text properly? If so, you
might consider adding this for some languages (like Arabic).

-chris

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)