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 [EMAIL PROTECTED] 2004-10-09 09:29 ------- 1. Converting HTML files into JSPs has following problems. - Since the JSP compile is needed, a performance may become a problem. - HTML files must be included correctly in JSP spec. I think requiring converting HTML into JSP means not fulfilling specification. 2."file.encoding" option does not operate depending on the version of JVM. 1.1 OK 1.2 NG 1.3 - 1.4.1 OK 1.4.2 NG "file.encoding" is determined by default locale at the time of JVM execution. I recommend you to see the following page. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4163515 3. The best solution for including HTML files of multiple encodings is changing the JSP spec. First of all, a browser cannot display if multiple encodings are contained in 1 page. In this case, in a HTML file, you should use comprehensive encodings, such as UTF8. However, do you want to use UTF8 as default locale? This patch can separate encodings of default locale and web app. This patch extends options without any undesireble effects. Other options are still effective even if this patch is accepted. reagrds, Takayuki Kaneko --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
