A
Andy Dingley
From a thread over in c.i.w.a.h
"RFC: From XHTML to HTML via XSLT"
http://groups.google.co.uk/group/comp.infosystems.www.authoring.html/msg/f112c230061ffe86
As is well-known, the XSLT HTML output method should generate <br>
rather than <br /> or <br></br>
From: <http://www.w3.org/TR/xslt#section-HTML-Output-Method>
:> The html output method should not output an end-tag for empty
elements. For HTML 4.0, the empty elements
:> are area, base, basefont, br, col, frame, hr, img, input,
isindex, link, meta and param. For example, an element
:> written as <br/> or <br></br> in the stylesheet should be output
as <br>.
So what happens if this "br" element is generated by an <xsl:copy>
from an XHTML input document, bound to the XHTML namespace URI ?
What do practical transform engines do here? Are they consistent?
"RFC: From XHTML to HTML via XSLT"
http://groups.google.co.uk/group/comp.infosystems.www.authoring.html/msg/f112c230061ffe86
As is well-known, the XSLT HTML output method should generate <br>
rather than <br /> or <br></br>
From: <http://www.w3.org/TR/xslt#section-HTML-Output-Method>
:> The html output method should not output an end-tag for empty
elements. For HTML 4.0, the empty elements
:> are area, base, basefont, br, col, frame, hr, img, input,
isindex, link, meta and param. For example, an element
:> written as <br/> or <br></br> in the stylesheet should be output
as <br>.
So what happens if this "br" element is generated by an <xsl:copy>
from an XHTML input document, bound to the XHTML namespace URI ?
Should the XSLT transfrom treat it "as HTML" ( said:
What do practical transform engines do here? Are they consistent?