Hello All,

I've been working on a XSLT driven search engine for my website. I am getting stuck on a hit count. My search engine uses VB.NET and XSLT to display the results so I am forced to use XSLT 1.0.

I've cut out most of the XSLT to keep it simple:
How do I count the number of times the word is found in the document?

Thanks

A quick aside - Saxon and AltovaXML can both be used with .Net, so you are not restricted to XSLT 1.0 along just because you are using VB.Net.

The contains function takes two strings as arguments, therefore the above will create the the string representation of the node set containing every node in the document - which seeing as in XSLT 1.0 this will simply be the text value of the first node, which will probably be the root node, and hence the text value of the entire tree the following will probably do the same test="contains(., $search)"

Also a 'feature' is that the contains function would return true if the XML input contained "<root><element>1</element><element>2</element></root>" and you searched for "12".

Lastly your inner for-each will just loop through every node in the tree and output the <xsl:number> for each.

Perhaps <xsl:for-each select="//*[contains(text(), $search)"> might be a better way of doing this.

/- Sam Judson : Wrox Technical Editor -/

Counting the number of occurrences requires a recursive template with the logic (in pesudo-code)

countOccurrences(x, str) {
  if (contains(x, str))
  then 1 + countOccurrences(substring-after(x, str), str)
  else 0
}

But you might find that you can get by with counting the number of text nodes that contain the string, which would be

count(//text()[contains(., $str)])

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference

Thank you very much.

I should have been more clear. I am using VB.NET and XSLT for a web application and doing the transformation with Internet Explorer.

Michael, the following worked:

count(//text()[contains(., $str)])

Thank you,

Bones

So the reason you can't use XSLT 2.0 is because you are using IE, not because you are using .Net.

/- Sam Judson : Wrox Technical Editor -/

Hi Sam,

Yes, I am doing the transformation with IE.

I do use Saxon 9.0 with my .NET apps. I only wish IE had the same functionality as SAXON.