The saxon tokenize() works for me in this case.
I find it a little hard to see why anyone would want to use Saxon extension
functions with XSLT 1.0.
I can see why some projects might feel that they want to stick with XSLT 1.0
for the time being, and why some projects might be stuck with XSLT 1.0
because of their unfortunate choice of platform. But if you are able to use
an extension function like saxon:tokenize(), then I would have thought that
in nearly all cases you were better off moving to Saxon 8.x and the standard
XSLT 2.0 tokenize() function.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--