> > 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.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx 


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list