> one weird problem that I had was that I *had* to use the
> string function, I
> thought that (//parentCategory) would have been fine as is, but I was
> mistaken.

Not at all weird: the uriEncode function expects a string, it doesn't know
what do do if you give it a node-set. The XSLT processor doesn't know that
it expects a string, because JavaScript is untyped. If you were calling a
Java external function, the type conversion from node-set to string would be
done for you.

Mike Kay
Software AG


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list