Mukul Gandhi created XALANJ-2813: ------------------------------------ Summary: Xalan-J's XSL 3 xsl:analyze-string implementation status as per W3C XSLT 3.0 test suite Key: XALANJ-2813 URL: https://issues.apache.org/jira/browse/XALANJ-2813 Project: XalanJ2 Issue Type: Task Security Level: No security risk; visible to anyone (Ordinary problems in Xalan projects. Anybody can view the issue.) Components: Xalan-interpretive Reporter: Mukul Gandhi Attachments: xsl_analyze_string_test_results.xml
I'm creating this jira issue to track, Xalan-J's XSL 3 xsl:analyze-string instruction's implementation status as per W3C XSLT 3.0 test suite. W3C's XSLT 3.0 test suite is available at link, https://github.com/w3c/xslt30-test from where that may be downloaded and configured locally. Xalan-J's XSL 3 implementation on it's github repos branch, has a working test driver for W3C XSLT 3.0 test suite. I've attached an XML document with this jira issue, which has tests report information about Xalan-J's XSL 3 xsl:analyze-string instruction implementation compliance with respect to W3C XSLT 3.0 test suite. There are various reported test failures as well as mentioned within attached XML document, which I think we need to collectively fix, because this is lot of bug fixing work I believe. Anyone wishing to help improve Xalan-J's XSL 3 implementation compliance for xsl:analyze-string instruction is welcome to take this task, or atleast help Xalan-J team fix one or more related bugs and also make design improvements if needed. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org