This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: doe alternative?
- From: "Michael Kay" <michael dot h dot kay at ntlworld dot com>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Wed, 11 Sep 2002 14:34:22 +0100
- Subject: RE: [xsl] doe alternative?
- Reply-to: xsl-list at lists dot mulberrytech dot com
Neither the XPath data model, nor XML itself, allows a comment to
contain an element.
If an XML comment looks like <!-- <a/> -->, then the <a/> is not an
element, it is just four characters of text. It could equally be <!--
<1!> -->, and the parser wouldn't complain.
Since XML comments can't contain elements (only text that looks like
elements), you wouldn't expect the XSLT result tree to allow a comment
node to contain an element node, would you?
Michael Kay
Software AG
home: Michael.H.Kay@ntlworld.com
work: Michael.Kay@softwareag.com
> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com] On Behalf Of
> DPawson@rnib.org.uk
> Sent: 11 September 2002 12:56
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] doe alternative?
>
>
> I want to output
>
>
> <xsl:otherwise>
> <xsl:comment>
> <meta>
> <xsl:copy-of select="@*"/>
> </meta>
> </xsl:text>
> </xsl:otherwise>
>
>
> I have some input which 'may' be needed in the output.
> Ideally I'd like to have it available in the output,
> but commented out for manual intervention later.
>
> XSLT 1.0 says no!
>
> How can I sneak it through Saxon please :-)
>
> And why is that rule in place please?
> Other than nested comments, I can't see any rationale in
> disallowing it?
>
> Regards DaveP
>
> -
>
> NOTICE: The information contained in this email and any
> attachments is
> confidential and may be legally privileged. If you are not the
> intended recipient you are hereby notified that you must not use,
> disclose, distribute, copy, print or rely on this email's content. If
> you are not the intended recipient, please notify the sender
> immediately and then delete the email and any attachments from your
> system.
>
> RNIB has made strenuous efforts to ensure that emails and any
> attachments generated by its staff are free from viruses. However, it
> cannot accept any responsibility for any viruses which are
> transmitted. We therefore recommend you scan all attachments.
>
> Please note that the statements and views expressed in this email
> and any attachments are those of the author and do not necessarily
> represent those of RNIB.
>
> RNIB Registered Charity Number: 226227
>
> Website: http://www.rnib.org.uk
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list