|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Partial Implementation of XInclude include element
Jeni Tennison wrote: > I think that it's probably better to use an identity template here, > namely: > > <xsl:template match="node() | @*" mode="xinclude"> > <xsl:copy> > <xsl:apply-templates select="@* | node()" mode="xinclude" /> > </xsl:copy> > </xsl:template> > > First, it's simpler. Second, it copies over comments and PIs, which > you probably should do. Third, and most important, it manages > namespaces correctly. As you currently have it, say you were > including: Hmm. What doesn't happen when I use this improved code is copying of the namespace nodes from the xsl:stylesheet document, as happens in normal output (that is, if I don't go through this initial xinclude step). Is that simply unavoidable or is there some other namespace subtlety that I'm overlooking? Thanks, E. -- W. Eliot Kimber, eliot@xxxxxxxxxx Consultant, ISOGEN International 1016 La Posada Dr., Suite 240 Austin, TX 78752 Phone: 512.656.4139 XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








