• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

XSLT Processor

Cormyr

Member
Which XSLT processor is used for custom output?

Seems that XLST 2.0 is not supported, which is not completely surprising, but seems also that exslt (extension) are not supported also.

Is this just a basic 1.0 XSLT processor?
 
I'm on Mac. But it s seems that this is also only 1.0.

You should change your XSLT processor as 2.0 add a lot a useful functions, in particular string functions, which are missing.
In addition, some other new capabilities would be useful.

Are you considering upgrading this processor? It should not change for main program but help for custom output.
 
Assuming this is needed for .NET, Microsoft doesn't support any versions of XSLT beyond 1.0. Something I'm very disappointed to see, BTW, because I use alot of XSL transformations in my company's code that I would really love to have the functionality of XSLT 2.0. Unfortunately, MS has not added any additional XSLT support up to 4.5, though .NET 5.0 Framework is out very soon, maybe then. Aww, who am I kidding. It is what it is.

I do hear tell that some third party XSLT processes can be referenced in some .NET class that will allow similar processes to XSLT 2.0, but since I haven't used any of them, I can't really verify it.
 
On the mac, we're using the native XSLT functions built into the OS. Apple's developer side doesn't give any information one way or the other, but it looks like we're limited to version 1.0 there too, I'm afraid. :(
 
Back
Top