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 27517] - The pageEncoding attribute is not used, when charset value is set.
Date Mon, 08 Mar 2004 15:42:27 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=27517>.
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=27517

The pageEncoding attribute is not used, when charset value is set.

petr.pisl@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From petr.pisl@sun.com  2004-03-08 15:42 -------
There is part of the specification:

JSP.4.1
...
For JSP pages in standard syntax, the page character encoding is determined from
the following sources:
-A JSP configuration element page-encoding value whose URL pattern matches the page.
-The pageEncoding attribute of the page directive of the page. It is a
translation- time error to name different encodings in the pageEncoding
attribute of the page directive of a JSP page and in a JSP configuration element
whose URL pattern matches the page.
- The charset value of the contentType attribute of the page directive. This is
used to determine the page character encoding if neither a JSP configuration
element page-encoding nor the pageEncoding attribute are provided.
- If none of the above is provided, ISO-8859-1 is used as the default character
encoding.




Appendix JSP.D
Page Encoding Detection
....

3. If the file is a JSP page in standard syntax, use these steps. 

a. Check whether there is a JSP configuration element <page-encoding> whose URL
pattern matches this file. 

b. Read the file using the initial encoding and search for a pageEncoding
attribute in a page declaration. The specification requires the attribute to be
found only if it is not preceded by non-ASCII characters, so simplified
implementations are allowed. 

c. Report an error if there are a <page-encoding> configuration element whose
URL pattern matches this file and a pageEncoding attribute, and the two name
different encodings. 

d. If there is a <page-encoding> configuration element whose URL pattern matches
this file, the page character encoding is the one named in this element. 

e. Otherwise, if there is a pageEncoding attribute, the page character encoding
is the one named in this attribute. 

f. Otherwise, read the file using the initial encoding and search for a charset
value within a contentType attribute in a page declaration. If it exists, the
page character encoding is the one named in this charset value. The
specification requires the attribute to be found only if it is not preceded by
non-ASCII characters, so simplified implementations are allowed. 

g. Otherwise, the page character encoding is ISO-8859-1.

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