Subject:Impove the built-in XSLT processor. Author:Vasil Rangelov Date:04 Oct 2006 03:25 PM
I know Stylus Studio's XSLT processor is only for testing purposes, but I think it needs some impovement.
The first thing I noticed when running one of my (previously written and tested) XSLT stylesheet was that element-available() is supported, but there isn't a single (standart nor EXSLT extension) XSLT instruction to return true. All return false so practically, the abilities of this processor remain partically a mystery.
Are there any EXSLT functions supported? If not, I would like to see some at one point.
Or better yet- a second built-in XSLT processor with EXSLT support. That way, developers can test their stylesheets in both extension and non-extension awared environments.
Subject:Impove the built-in XSLT processor. Author:Vasil Rangelov Date:04 Oct 2006 04:08 PM Originally Posted: 04 Oct 2006 04:01 PM
The stylesheet I tested is a benchmark for testing all (E)XSLT elements and functions. It was designed with browsers' and server side scripts' XSLT processors in mind. I tested it in Saxon too and it works great.
The Stylus Studio's XSLT processor is the first one I've seen to actually return false to every element.
By the way, XalanJ seems to fail reverting to XSLT 1.0 and thus fails the test. The stylesheet tests XSLT 2.0 elements and functions too (it's XSLT 2.0 stylesheet), but it's designed to work in both XSLT 1.0 and 2.0 processors as long as the processor is automatically using XSLT 1.0 behaviour when higher is not supported. Changing the version from 2.0 to 1.0 is the only fix for this. Surprisingly (for me at least), XalanC (in Dreamwaver 8) doesn't have this problem.