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 36591] - <%@page pageEncoding="UTF-8"%> doesn't work within included JSP Fragment
Date Sun, 18 Dec 2005 23:15:30 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=36591>.
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=36591





------- Additional Comments From dawid.weiss@cs.put.poznan.pl  2005-12-19 00:15 -------
Ok, it was my fault. I'll explain anyway -- maybe it'll help someone.

Jasper (JSP compiler) uses an algorithm to determine the encoding of every
single JSP page. This also applies to all resources included with <%@include
file="" %>) (the encoding is determined for each one of these files). So, unless
you have an explicit page encoding directive in all included files (<@%page
pageEncoding="UTF-8" %>), you will encounter problems with corrupted input
encoding (because included files will be read with the default encoding,
regardless of the encoding of the main page).

I still think the encoding of the main page should be the default to switch to
for all included resources if they don't declare any other explicit encoding...
but I guess it's not that important. Sorry for false alarm.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message