You are most welcome, but something still doesn't sit quite right regarding
your situation based on your response to my comments.
Note that the SGML conventions are used only when HTML element types are
recognized in the result tree, and HTML element types are recognized only
when the output method is HTML, and HTML is the default output method
*only* when the document element of the result tree is named with only the
four letters H, T, M, and L. Without the specific condition of the
document element of the result tree, the default output method is XML which
would have given you the end tags.
Therefore, since you didn't have an <xsl:output/> instruction, that means
that you must have had either "html" or "HTML" as the element type of your
document element of your result tree.
Therefore ... your result is probably HTML which doesn't need an end tag
for <link> or <img>. If your output isn't HTML then using any other
document element in the result would have given you your desired end tags
without needing <xsl:output/>.
So I'm curious why you do need end tags for elements of these two element
types in a result that begins with the "html" document element.
...................... Ken
At 2004-01-06 22:48 -0800, Brendan Moran wrote:
That explained it nicely, thank you. The two tags where this happened
noticeably were <link> and <img>, and I hadn't used an output instruction,
which would explain the problem.
--Brendan
That is not conformant behaviour.
If your output method is HTML and the element type is an HTML element
type, then that *is* the expected output because in that case SGML
conventions are used, but otherwise a conforming processor would put out
the following XML conventions for the default XML output method:
Please check your <xsl:output/> instruction for the use of HTML ... but
your report is not at all consistent with my expectations of MSXML and
Xalan, both of which should be producing a properly constructed empty element.
If you think you are engaging everything properly, then please post a
short (15 line?) complete stylesheet that illustrates your results so
that others can run your stylesheet on their system.
I hope this helps.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
--
North America (Washington, DC): 3-day XSLT/2-day XSL-FO 2004-02-09
Instructor-led on-site corporate, government & user group training
for XSLT and XSL-FO world-wide: please contact us for the details
G. Ken Holman mailto:gkholman(_at_)CraneSoftwrights(_dot_)com
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/
Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
ISBN 0-13-065196-6 Definitive XSLT and XPath
ISBN 0-13-140374-5 Definitive XSL-FO
ISBN 1-894049-08-X Practical Transformation Using XSLT and XPath
ISBN 1-894049-11-X Practical Formatting Using XSL-FO
Member of the XML Guild of Practitioners: http://XMLGuild.info
Male Breast Cancer Awareness http://www.CraneSoftwrights.com/s/bc
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list