[ http://issues.apache.org/jira/browse/XALANJ-611?page=comments#action_12368308 ]
Nick Fitzsimons commented on XALANJ-611: ---------------------------------------- This is a serious flaw in Xalan, and I can't believe it has been around since 2001. The simple fact is that Xalan, when used with output method HTML, fails to produce valid HTML, and therefore fails to correctly implement XSLT 1.0. I'm not sure why the matter was "extensively debated" as it takes about two minutes reading the XSLT 1.0 and HTML 4.01specs to determine that: 1. The XSLT 1.0 spec is rather vague about outputting character entities in HTML [XSLT 1.0 section 16.2]; 2. Nonetheless, it clearly states that the processor should produce valid HTML, defaulting to HTML 4 if no version is specified [XSLT 1.0 section 16.2]; 3. Unescaped ampersands in href attributes are not valid HTML 4 (or 4.01) [HTML 4.0 section 5.3.2] and [HTML 4.01 section 5.3.2]. Is there likely to be any progress on this issue soon? As was noted in 2002, Saxon and MSXML both manage to work correctly on this one. > HTML output serializes ampersand as "&" in HREF attributes > ---------------------------------------------------------- > > Key: XALANJ-611 > URL: http://issues.apache.org/jira/browse/XALANJ-611 > Project: XalanJ2 > Type: Bug > Components: Serialization > Versions: Latest Development Code > Environment: Operating System: All > Platform: All > Reporter: julian.reschke > Assignee: Xalan Developers Mailing List > > Using the HTML output method, an ampersand is serialized as "&". It should > be "&". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
