DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13125>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13125 Lack of character-set while using <html:html > tag [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Status|NEW |RESOLVED Resolution| |LATER ------- Additional Comments From [EMAIL PROTECTED] 2002-10-04 02:52 ------- A few issues related to doing this: * There is an implicit assumption that there is only one relevant character set for each possible Locale. I'm not sure that is true in all cases; even if it is, we would need to define the mapping table for all reasonable Locales. Do you have such a list? * The JSP page compiler will have already set the character encoding for the page, based on the contentType and/or pageEncoding settings of the <%@ page %> directive, which get translated into a "Content-Type" HTTP header. It is browser dependent whether or not a meta tag definition of the character set will override one that was set on a Content-Type header. * Ideally, the <html:html> tag would actually call setContentType() itself, to ensure that the Content-Type header also contained the correct character encoding. Unfortunately, this is not allowed in JSP 1.1 (the required minimum platform for Struts 1.x) -- although it would be allowed under JSP 1.2. Because it cannot be dealt correctly in a JSP 1.1 environment, I'm going to mark this issue as an enhancement (not a bug) and resolve it with a "LATER" value, so that it will be addressed in a future version of Struts that is based on JSP 1.2 or later. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
