This is in reference to a thread Chris Davis started in December last year, 'Unexpected output for XSLT'. I've just found a solution/workaround to the problem of forcing XSLT transformations to use the non-shortened syntax for empty elements.
If you define the xsl:output method as 'html', rather than the default 'xml', the transformation will always create <foo></foo> rather than <foo /> Here's the extra line you need, immediately after the xsl:stylesheet declaration: <xsl:output method = "html"/> This problem came up when we upgraded an application to use the native XML features in ColdFusion MX, rather than the Microsoft XML parser. It seems that transformations in MSXML default to the expanded syntax, while Xalan transformations (used by MX) default to the abbreviated version. While most parsers don't distinguish between the two syntaxes, the abbreviated type can cause problems with browser recognition of some HTML elements. <br /> works fine, but Internet Explorer chokes on a <textarea> without an explicit closing </textarea>. Best wishes Tom -----------------+ tom dyson t: +44 (0)1608 811870 m: +44 (0)7958 752657 http://torchbox.com -----------------------+ cf-xml mailing list list: [EMAIL PROTECTED] admin: [EMAIL PROTECTED] home: http://torchbox.com/xml
