This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Using XPath expressions in modes
- To: xsl-list at lists dot mulberrytech dot com
- Subject: RE: [xsl] Using XPath expressions in modes
- From: sara dot mitchell at ps dot ge dot com
- Date: Wed, 25 Apr 2001 14:07:29 -0400
- Reply-To: xsl-list at lists dot mulberrytech dot com
If you're taking votes, then let me add mine. This would
greatly benefit modularity and sharing (at least in
my environment :),
Sara Mitchell
> -----Original Message-----
> From: DPawson@rnib.org.uk [mailto:DPawson@rnib.org.uk]
> Sent: Wednesday, April 25, 2001 2:25 AM
> To: xsl-list@lists.mulberrytech.com
> Subject: RE: [xsl] Using XPath expressions in modes
>
>
> > From: Oliver Becker
>
> > <xsl:template match="*">
> > <xsl:message><xsl:value-of select="name()"> not
> > processed</xsl:message>
> > </xsl:template>
> >
> > So the problem is: if the included stylesheet uses modes to
> > process the
> > input, my templates wont be used. I have no way to find
> out, for which
> > modes I need to provide my additional templates, except I
> > look into the
> > stylesheet code.
>
> Were we able to have
> <xsl:template match="*" mode="*">
> Exception processing
> </xsl:template>
>
> Which had a low priority, and was naturally overridden
> by any existant templates, that would resolve the problem.
>
> I guess, carrying on with that logic
> <xsl:template match="*:*" mode="*">
> Exception processing
> </xsl:template>
>
> Would do the same where you had forgotten namespace foo:new-element ?
>
> Is that a reasonable request for 2.0?
>
> Regards DaveP
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list