RE: [xsl] RE: [SPAM] - RE: [xsl] RE: [SPAM] - Re: [xsl] characters in xsl - Bayesian Filter detected spam - Bayesian Filter detected spam

Subject: RE: [xsl] RE: [SPAM] - RE: [xsl] RE: [SPAM] - Re: [xsl] characters in xsl - Bayesian Filter detected spam - Bayesian Filter detected spam
From: "Bradley, Peter" <PBradley@xxxxxxxxxx>
Date: Thu, 11 Nov 2004 16:31:55 -0000
Nope.  I haven't got it.  Never mind.  I'll go back to the spec and do some
reading.  If I still can't work it out, I'll perhaps ask again.

Thanks for trying.  Sorry for being so dumb!

Cheers

Peter

 -----Original Message-----
From: 	David Carlisle [mailto:davidc@xxxxxxxxx]
Sent:	11 November 2004 16:29
To:	xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject:	Re: [xsl] RE: [SPAM] - RE: [xsl] RE: [SPAM] - Re: [xsl] characters in
xsl - Bayesian Filter detected spam - Bayesian Filter detected spam

  So, if I say:

  <xsl:template match="//stone">
  ...
  </xsl:template>

  I specify a template for every <stone> element regardless of where it
  appears in the file?

yes, although

 <xsl:template match="stone">

would match the same elements. It's never useful to start a match
pattern with //.

   Meaning that:

  /stone

  and

  /stone/*/stone

  would activate the same template?  Is that right?


I don't understand this last part. /stone and /stone/*/stone
are very different expressions and woul dselect different nodes in a
select expression and match different nodes if used in a match pattern.

David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Current Thread