This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: Re: needing clarification about XSL transformation
On Mon, 3 Mar 2003 09:07:53 -0500 (EST)
"Robert P. J. Day" <rpjday at mindspring dot com> wrote:
<skipped/>
> before this gets even further afield, let me stress that i
> *know* how to add extra rules to ensure processing of comments
> and processing instructions. what i was baffled by was the
> clearly differing behaviour between xsltproc and saxon, using
> the following stylesheet (shown in its entirety):
>
> ---------------------------
>
> <?xml version="1.0" encoding="utf-8"?>
> <xsl:stylesheet
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> version="1.0">
>
> <xsl:template match="@*">
> <xsl:copy/>
> </xsl:template>
>
> <xsl:template match="node()">
> <xsl:copy>
> <xsl:apply-templates select="@* | node()" />
> </xsl:copy>
> </xsl:template>
>
> </xsl:stylesheet>
>
> ----------------------------------------
>
> given that i'm not trying to do anything fancy, it
> seems to me that using *any* XSL transformation tool
> should give me the same output.
>
> but xsltproc does *not* copy over comments or
> processing instructions, while saxon *does*. ergo,
> at least one of them is incorrect.
With this style xslt-processor must not copy comments and PI.
This style not overriding built-in templates, so saxon is
incorrect.
> so my question is, given that the node() function
> is defined as matching comment and processing instruction
> nodes, which of these tools is behaving incorrectly?
Saxon.
<skipped/>
--
Regards, Vyt
mailto: vyt at vzljot dot ru
JID: vyt at vzljot dot ru