Note that the "3.0" branch, in addition to being experimental/under development, is still very much a subset. Think if it as Xalan with some XSLT3 features, rather than a full XSLT 3.0 processor.
I'm sure Mukul would appreciate bug reports and feature requests against that branch, but please check his documentation first so you know what is and isn't expected to be working, and if you do open a Jira ticket please be very explicit about what branch you're using and when you downloaded it. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________ From: Martin Honnen <martin.hon...@gmx.de> Sent: Thursday, December 7, 2023 12:39:27 PM To: j-users@xalan.apache.org <j-users@xalan.apache.org> Subject: Question on use of XSLT 3 branch of Xalan Hi, thanks to various of Mukul's articles I have become aware of the XSLT 3 development branch of Xalan; I think I have found it on Github at https://github.com/apache/xalan-java/tree/xalan-j_xslt3.0 and I have managed to download, build and try it. I understand it is work in progress and I am not sure what to do if I encounter bugs; I guess as there is an existing test suite of the W3C most problems I might run to might be known so I am not sure filing bugs or asking about them here is useful in progressing the development. Let me know what you think, whether at this stage you want bug reports or not. The concrete case I have found is using exclude-result-prefixes="#all" (I tend to use that a lot with XSLT 3) where the build done with a download of the branch from yesterday tells me "org.xml.sax.SAXException: prefix of namespace could not be resolved: #all". (Note that is my translation to English that my JRE installation gave me in German, due to my system's OS locale).
