DO NOT REPLY [Bug 14681] - Invalid XHTML closure for empty attribute and element objects in SerializeToHTML.java

[bu...@apache.org]

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=14681>.
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=14681

Invalid XHTML closure for empty attribute and element objects in SerializeToHTML.java





------- Additional Comments From keshlam@us.ibm.com  2002-11-19 16:32 -------
HTML output mode is HTML, not XHTML. XSLT 1.0 didn't standardize a way to 
request XHTML output. The closest we come is a semi-undocumented custom feature 
which half-support XHTML -- if you request xml output, and have specified an 
output doctype whose public ID happens to start with "-//W3C//DTD XHTML", we 
will serialize as XML but will put a space before the /> as you've requested. 
However this will serialize as XML outside of that change, meaning it won't do 
the entity conversion or URI escaping that is applied to HTML output, and it's 
emphatically not a portable solution.

I believe XSLT 2.0 intends to add xhtml as an officially supported output mode. 
I don't think our XSLT 2.0 prototype handles that yet, though I'd have to check.

So I think this is INVALID as submitted, though it might be legitimate if 
reported specifically against the xslt20 branch.