RE: AW: struggling with <xsl:analyze-string>

No, these two are not equivalent. The matches() solution passes the whole of
the text node that matches the regex to the called template; the
xsl:analyze-string solution only passes that part of the text node that
matches the regex.

(note that in both cases the match is unanchored, that is it will succeed if
any part of the text node matches)

(off-topic: is Jdnner the Austrian equivalent of Januar?)

Michael Kay
http://www.saxonica.com/


> -----Original Message-----
> From: David Carlisle [mailto:davidc@xxxxxxxxx]
> Sent: 26 January 2005 16:26
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: AW:  struggling with <xsl:analyze-string>
>
>
> > Would be nice to know if matches() would get me the same result...
>
>
> <xsl:for-each
> select="part/section/par[@class='45_UeberschrPara' and
> contains(text(), 'In-Kraft-Treten')]/following::text()">
> 	<xsl:analyze-string select="." regex="\d{{1,2}}.+\d{{4}}">
> 		<xsl:matching-substring>
> 			<xsl:call-template name="get.date">
> 				<xsl:with-param name="text"
> select="." as="xs:string"/>
> 			</xsl:call-template>
> 		</xsl:matching-substring>
> 	</xsl:analyze-string>
> </xsl:for-each>
>
> should be equivalent to
>
>
> <xsl:for-each
> select="part/section/par[@class='45_UeberschrPara' and
> contains(text(),
> 'In-Kraft-Treten')]/following::text()[matches(.,\d{1,2}.+\d{4})">
> 			<xsl:call-template name="get.date">
> 				<xsl:with-param name="text"
> select="." as="xs:string"/>
> 			</xsl:call-template>
> </xsl:for-each>
>
>
> (untested)
>
> 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
> ______________________________________________________________
> __________