>> Unfortunately, I use another engine.
>
> Hmm...  Did I say that a specific "engine" was necessary for the solution?
>

Or did you think that FXSL was an "engine"?

It most certainly isn't an "engine".

FXSL is a library of functions/templates, written in pure XSLT. As such, its 
functions can be used under any compliant XSLT 2.0 processor or any 
compliant XSLT 1.0 processor that either implements the exsl:node-set() 
extension function, or is one of the following XSLT 1.0 processors: MSXML 
(3,4,6), Xalan, Saxon.

Cheers,
Dimitre Novatchev

"Dimitre Novatchev" <dnovatchev@c...> wrote in message 
news:49165fc4$0$17067$6e1ede2f@r......
>
> "Ebenezer" <vaciapairat@s...> wrote in message 
> news:AAkRk.188514$FR.475337@t......
>> Dimitre Novatchev ha scritto:
>>> "Ebenezer" <vaciapairat@s...> wrote in message 
>>> news:5j_Qk.187764$FR.474551@t......
>>> Using FXSL 1.x and its "str-split-to-words" template, such processing is 
>>> trivial.
>>
>> Unfortunately, I use another engine.
>
> Hmm...  Did I say that a specific "engine" was necessary for the solution?
>
> FXSL 1.x  works with *any* XSLT 1.0 processor that supports the 
> exsl:node-set() extension function.
>
> There are 3 separate versions for MSXML, Xalan and Saxon, although the 
> last two XSLT 1.0 processors implement exsl:node-set().
>
> For MSXML, there is a way to implement exslt:node-set() (and in any XSLT 
> processor that supports extension functions written in inline-JavaScript). 
> See:
>
>    http://www.jenitennison.com/blog/node/24
>
> Lastly, FXSL 2.0 is the latest (since the last 4-5 years) version of FXSL 
> which is written in and for XSLT 2.0. It doesn't use any extension 
> functions at all.
>
>