tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31201] - Encoding bug when using <jsp:include ...> action
Date Sat, 02 Oct 2004 14:47:32 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31201>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31201

Encoding bug when using <jsp:include ...> action

markt@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From markt@apache.org  2004-10-02 14:47 -------
The patch suggested above would be a Tomcat specific solution to a wider i18n 
problem. Whilst it would work for Tomcat I would not wish to encourage an 
approach such as this as if you ever need to move to an alternative container, 
it will break again. Therefore, this patch will not be applied. (Hence the 
WONTFIX).

There are, however, a number of alternative approaches that are spec compliant 
and are hence container neutral.

The simplest approach is to convert the HTML to JSPs and specify the correct 
page encoding in the new JSPs using <%@ page pageEncoding=... %>.

There are other approaches and if the one suggested above isn't appropriate I 
suggest that you post a question on the tomcat-user mailing list rather than 
this bug report.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message