Michael, Thank you for your detaild answers!!!
Now, I am going to re-read XSLT spec ... it's clear that I forgot some critical
points!! :-P
Bye!!
Quoting Michael Kay <michael(_dot_)h(_dot_)kay(_at_)ntlworld(_dot_)com>:
So, What's wrong in using disable-output-escaping?
The quick answer is that it's an optional feature of the spec and
doesn't work on all processors.
The deeper answer, if you're interested in software engineering rather
than hacking code, is that it breaks the architectural boundary between
the XSLT tree-to-tree transformation process and the subsequent
tree-to-bytestream serialization process. Breaking architectural
boundaries is always bad news, because it reduces your ability to
reconfigure the components of your system. To be more concrete, it means
that your transformation will stop working if you want to add a
component to your system that uses the result tree rather than its
serialized representation.
Michael Kay
Software AG
home: Michael(_dot_)H(_dot_)Kay(_at_)ntlworld(_dot_)com
work: Michael(_dot_)Kay(_at_)softwareag(_dot_)com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list