Go on, I'll ask :-)
How does this help please David?
DaveP.
well I was refering to the "fact" that
in the xml output method an xslt 1 system can write #10 in a system
specific manner (ie do the opposite of what an xml parser does
in normalising line endings to #10)
so in xml output
<xsl:text>
</xsl:text>
(or equivalently>
<xsl:text> </xsl:text>
)
may produce an msdos style #13 #10 pair on output if on a windows
machine and a single #10 on unix and a single #13 on macs, etc.
however I've just read that section of xslt1 again and it doesn't
explictly say that a system may do that although it doesn't say it
can't and doing so would still meet the constraint that
In addition, the output should be such that if a new tree was
constructed by parsing the wrapper as an XML document as specified in
[3 Data Model], and then removing the document element, making its
children instead be children of the root node, then the new tree would
be the same as the result tree, with the following possible
exceptions:
hmm..
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list