Actually I found a solution for a subset of characters of our interest
with Tomcat 3.2.1.
We made a patch for the euro symbol by setting the character set with:
response.setContentType("text/html; charset=UTF-8");
and manually decoding from responses an "intermediate" 8859_1 codepage.
This is due to the 3.2.1 implementation wich ALWAYS opens a reader
from the request with 8859_1 enconding.
I think you can do the same with the characters you are interested in.
I'm interested of alternative solutions while waiting for a 2.3 compliant
servlet container where one can specify with which encoding the request is
formed
(the browser doesn't tell anything about it) or how other servlet containers
behave.
Reference:
Search "charset used for parameters decoding on HTTP request Tomcat3.x,4 "
in [EMAIL PROTECTED]
Regards,
Marco
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
