On 07/08/2024 21:44, ohaya ohaya@xxxxxxxxx wrote:
> Martin,
>
> I don't remember mentioning Xalan, and actually THAT (which XSLT
> processor was being used) was a question I had.
>
>
I think in a previous thread it was stated that you use xsltproc to test
but in your product you have (probably) Xalan C++ 1.2. I am not going to
search the archives, perhaps I don't remember that right and it was a
different user although these days there is not much traffic.


>
> Given what I just found and posted about the testing on the product
> (that it worked, but with the exslt: prefix and NOT with msxsl:
> prefix) - can we conclude that the XSLT processor/engine on the
> product is Xalan?
>

Most XSLT processors (for 1.0 or later) are usually cross platform so
the lack of support of the MS prefix/namespace suggests it is not a
Microsoft processor (although at some stages I think other products like
Altova and/or XmlPrime also supported the MS namespace) but you can run
Xalan Java, Saxon 6.5 Java, Xalan C++, xsltproc/libxslt under Windows,
so I wouldn't conclude anything but use

 B  system-property('xsl:vendor')

and

 B  system-property('xsl:vendor-url')

to check.