[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

[xsl] Patterns and scoped variables (or rather lack thereof)

Subject: [xsl] Patterns and scoped variables (or rather lack thereof)
From: Ihe Onwuka <ihe.onwuka@xxxxxxxxx>
Date: Sat, 15 Feb 2014 20:42:12 +0000

Transforming this sort of markup

<div class="fr small subtle">Transaction date: Sep 26, 2013</div>

into a key value pair.

<Transactiondate>Sep 26, 2013</Transactiondate>

However if there are too many words before the colon separator (the
key part) then it probably isn't suitable for the key value treatment
(the code below uses 3 words as the cutoff point).

Talking of the code below and the thread title, the issue is how many
times I've had to (or think I've had to ) tokenize the string on colon
because I cannot (or think I cannot) introduce a let scoped variable
into the pattern.

 <xsl:template match="text()[count(tokenize(.,':')) eq 2 and
count(tokenize(tokenize(.,':')[1],'\s+')) lt 4]">

    <xsl:variable name="keyValue" select="tokenize(.,':')"/>

    <xsl:element name="{replace($keyValue[1],'\s+','')}"> .....key.....
      <xsl:value-of select="$keyValue[2]"/>


How else do I think I could do this.

<xsl:template match="text()">
  <xsl:call-template name="dealWithText"

<xsl:template name="dealWithText">
  <xsl:variable name="keyValue" select=tokenize ...etc>
    <xsl:when etc

which of course camouflages the matchng rule inside the call template.

Is this the best that can be done  or have I missed something.

Current Thread