This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Partial Implementation of XInclude include element
- From: "W. Eliot Kimber" <eliot at isogen dot com>
- To: XSL List <xsl-list at lists dot mulberrytech dot com>
- Date: Tue, 24 Sep 2002 09:58:38 -0500
- Subject: Re: [xsl] Partial Implementation of XInclude include element
- Organization: ISOGEN International
- References: <3D8E3D7C.C5CF2362@isogen.com> <115236485157.20020923084434@jenitennison.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
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@isogen.com
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