I have it on reasonably good authority (somebody at a high level at
Altova)
that the internal XSL engine used in XML Spy 5.* for debugging is a
variant
of Saxon, not of MSXML. I haven't done any experiments to prove this
to
myself, but many of the behaviors I have seen (e.g., white space
handling)
are rather like Saxon's behaviors and not MSXML's.
this would also be logical in the light of all those functions for
calling java I found.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list