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, 09 Oct 2004 11:19:14 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





------- Additional Comments From markt@apache.org  2004-10-09 11:19 -------
1. If performance is an issue, pre-compile your JSPs. If you can quote the 
part of the spec tomcat isn't following and the patch addresses this issue 
I'll commit it. However, having read the spec, and the errata, I believe 
tomcat is spec compliant.

2. I wasn't aware of this. Thanks for pointing this out. This is clearly not 
an option.

3. I think you mis-understood me. I was not trying to address one file with 
multiple encodings. My point is that your patch assumes (as does the current 
tomcat code) that ALL static files for all webapps will have the same 
encoding. Is this sufficient to address your i18n issues? Is it not possible 
to have one webapp with html files using one encoding and one webapp with thml 
files using a different one?

---------------------------------------------------------------------
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