How do you (or do you?) handle parse="text"?
I did a little more research, and I don't see a solution
using anything other than a purpose-built XSLT extension
function. Easy enough to write but would be specific to a
particular XSLT engine.
XSLT 2.0 has an unparsed-text() function, though it may not be 100%
compatible (yet) with XInclude in matters such as guessing the encoding
of the file.
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