Colin Paul Adams wrote:
"Michael" == Michael Kay <mike(_at_)saxonica(_dot_)com> writes:
Michael> Unfortunately the XML parser doesn't tell the XSLT
Michael> processor what DOCTYPE declaration was present, so the
This is true. But ...
Michael> XSLT processor can't reproduce it in the output.
... doesn't necessarily follow, since in XSLT 2.0 you can call
unparsed-text on the document and read the DOCTYPE by hand.
So *you* reproduce the DOCTYPE, not the XSLT processor, don't you?
You can also use a parameter to do that. But the processor itself
can't reproduce the DOCTYPE. And even if some processor can (§2.6):
Users should be aware, however, that since the input to
the transformation is a tree conforming to the XDM data
model as described in [Data Model], constructs that
might exist in the original XML document, or in the DOM,
but which are not within the scope of the data model,
cannot be processed by the stylesheet and cannot be
guaranteed to remain unchanged in the transformation
output. Such constructs include CDATA section
boundaries, the use of entity references, and the
DOCTYPE declaration and internal DTD subset.
Regards,
--drkm
___________________________________________________________________________
Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs
exceptionnels pour appeler la France et l'international.
Téléchargez sur http://fr.messenger.yahoo.com
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--