On 8/7/09 16:11, Daniel Henrique Alves Lima wrote:
On Wed, 2009-07-08 at 14:58 +0100, Pid wrote:
Hi, P. Thanks for your answer.
If you're using JSP have you also checked that you've got:
<%@ page contentType="text/html; charset=utf-8"
and not:
<%@ page contentType="text/html; charset=iso-8859-1"
The jsps in our application already include this page directive.
Encoding is a really mess/boring issue for non-US apps :-(
Encoding issues come up on the list fairly frequently. There is no "one
size fits all" answer.
The first thing to do is ensure that your app is absolutely, definitely,
100%, doing what you think it should be doing, every single time.
It may be worth building a small test app to develop against.
Also it's worth checking the request/response headers between each
browser type to check that there aren't any unexpected behaviours.
I will take a look.
How about this "accept-charset" ? I've never used before...
http://www.w3.org/TR/html401/interact/forms.html#adef-accept-charset
AFAIK this is not reliably supported by all browsers.
From recent-ish memory, I think, it was reported to the list that
browser clients tend to send content in the encoding format that the
previous document was received in - but I have experienced unpredictable
variations recently myself.
URL encoding can be set on the Connector element in server.xml too -
just to complicate matters even further.
p
Firefox has a plugin called something like: LiveHttpHeaders, IE has an
equivalent, Safari has a development mode& tool.
Ok. Thanks !
Please keep us posted.
p
Any suggestions or ideas ?
Thanks in advance !
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
