Announcing Saxon 13.0!

The first release of Saxon 13 has just been published. This is a new release for Java, C#, C/C++, PHP, and Python. The highlights in this release are:

• A redesigned Schema API that allows multiple schemas to coexist. You can now validate an input document with one schema and the result with another, even for the same namespace.
• More than 175 features from the draft 4.0 specifications are now available in Saxon-PE and Saxon-EE, including:
  • JNodes, path navigation over trees of JSON maps and arrays,
  • Lookahead and lookbehind in regular expressions,
  • Functions for CSV parsing,
  • Functions for parsing with Invisible XML, and
  • More flexible XML-to-JSON conversions with fn:element-to-map.
• On the topic of 4.0,
  • Mike recently published a list of 101 new things you can do with Saxon using 4.0 features!
  • (For more information about 4.0, see QT4CG.)
• Support for SaxonC extension functions written in C++, Python, and PHP.
• SaxonCS-HE, our first release of the free Saxon HE product built for .NET with C#.

Download products:

• Binaries for SaxonJ, SaxonC, and SaxonCS are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our Maven repository.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS-EE and SaxonCS-EE are available on NuGet
• Saxon-HE is available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

At the time of publication, a technical issue prevents us from publishing Python wheels for Windows. We will update the PyPI repository with those wheels as soon as they are available. Also, the resources release is not yet ready.

For more details, please consult the documentation.

If you encounter any issues with Saxon 13.0, please report them on our issue tracker.

P.S. See you in Prague!

Saxonica is pleased to announce that we’re having a user group meeting on the pre-conference day at XML Prague. Everyone is welcome!

We have a very loose agenda prepared, but this will be an informal event with lots of opportunities to ask questions and explore what’s new with Saxonica, our products, and the standards.

The proposed line up is:

• Introductions, products, product roadmap, and maybe a bit of a peek at what’s been going on in QT4CG as it relates to Saxonica.
• An overview of the new features under development for Saxon 13.
• A presentation of some of the exciting new developments in SaxonC, Python, and PHP.
• A demonstration of some of the new capabilities of Saxon 13.
• Lots of opportunity to chat with the whole Saxonica team!

Please come join us in room RB211 starting at 10:00am on Thursday, 4 June 2026.

Announcing Saxon 12.9!

The Saxon 12.9 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that fixes a number of issues that have been raised since 12.8 was released.

Saxon 12.9 was released on 12 September 2025. This release has been uploaded to the usual locations on the Saxonica website, GitHub, and Maven, PyPi, and NuGet. SaxonCS 12.9 is built with .NET 8.

For a list of the issues resolved in this release, please visit the issue trackers for SaxonJ and SaxonCS or SaxonC on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• SaxonC releases for HE, PE, and EE are also available from our download pages.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS is available on NuGet
• Saxon-HE is available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

Issues resolved in SaxonJ

This release fixes about twenty issues in SaxonJ and SaxonCS.

• 6893 Corrected an error in the Gizmo help messages
• 6892 Fixed expression tree corruption after a rewrite optimization
• 6891 Fixed an issue with regex flags when using the Java regex engine
• 6889 Fixed an infinite loop when using trace listeners with try/catch and function variables
• 6887 Added synchronization to avoid an exception
• 6883 Corrected an error where the xsl:catch errors attribute didn’t accept EQNames
• 6881 Fixed an exception when using 'position() eq last()' with no context item
• 6878 Changed parse-xml() so that validation is never attempted
• 6866 Corrected a namespace handling error when using the Domino tree model
• 6864 Implemented a performance improvement for slash expressions and simple step expressions
• 6863 Corrected a navigation error in snapshot trees
• 6860 Corrected errors in how character maps were handled when using adaptive serialization
• 6858 Improved error location information for some exceptions
• 6856 Corrected an API error distinguishing between empty maps and empty sequences
• 6840 Fixed an incorrect type inference for call on abs()
• 6824 Fixed an error in how the retained static context is managed
• 6818 Corrected an exception that could arise if attempting to serialize a free-standing attribute
• 6809 Fixed the line number of errors in a free-standing XPath expression
• 6805 Fixed a streaming bug related to comment handling
• 6799 Fixed an exception on number-formatter option function of xml-to-json using xsl:value-of

Issues in SaxonC

This release includes a number of improvements in memory management and support for multi-threaded execution.

• 6897 Fixed a bug where the XQueryProcessor.setQueryBaseURI() method had no effect
• 6885 Corrected a Python bug where getting the parent of the root node threw an exception
• 6880 Fixed a bug where XsltExexutable.getXslMessages() did not release memory
• 6879 Fixed a bug where XsltExecutable.callFunctionReturningValue() did not release memory
• 6859 Corrected an error where saxonc-core.h header was missing from source zip
• 6843 Fixed a bug where XsltExecutable.clone() did not work correctly with multiple threads

If you encounter any issues with Saxon 12.9, please report them on our issue tracker.

With the recent release of Python 3.14.0rc1, the ABI for Python 3.14 is final, and any SaxonC Python wheels we build against it will also work with the final 3.14 release. The TL;DR is that we’ve done that, and you can pip install saxonche (or saxoncee / saxoncpe) with the 3.14.0rc1 release right now.

The Python 3.13 release was trickier for us to deal with than it should have been – our build processes required a lot more manual intervention for different Python versions than we liked, and we had to wait for a new Saxon release to get wheels built for Python 3.13, which was frustrating.

We’ve been working on improving our build processes and making it easier to build Python wheels across all the platforms and Python versions we support. Easy enough, in fact, that we were able to test Python 3.14 support back at the beta stage, and were ready to build SaxonC Python 12.8 against 3.14 as soon as the RC dropped and the ABI was stable.

These new wheels were built from the same commit as the all the other SaxonC Python 12.8 wheels for Python 3.9-3.13. We’d love for you to install 12.8 for 3.14 and kick the tires: since Python 3.14 is still RC and not at the final release stage, there may be some problems we haven't come across. If you run into any problems, please report them on the SaxonC issue tracker.

There are wheels for the same platforms as always – macOS x86_64 and arm64, Linux x86_64 and aarch64, and Windows x86_64. For macOS x86_64, Python 3.14 now requires macOS 11 or later. As a result, Python 3.14 wheels of SaxonC Python 12.8 require macOS 11 or later on x86_64 too.

The accompanying release announcements for Saxon 11.7 and Saxon 12.8 describe those releases in detail. This post summarizes why we decided that we needed to release them both this week.

Some applications are known to use Saxon to run untrusted, user-submitted stylesheets or queries. Running untrusted code always entails some risk. Saxon provides two features designed to help mitigate this risk: ALLOWED_PROTOCOLS and ALLOW_EXTERNAL_FUNCTIONS. Setting ALLOWED_PROTOCOLS can limit what resources a stylesheet or query can access; it can for example, forbid access to file: URIs. The ALLOW_EXTERNAL_FUNCTIONS feature can disable access to reflexive Java extension functions, some system properties, and some other extension functions. (The remit of the ALLOW_EXTERNAL_FUNCTIONS feature is a little wider than you might expect.)

Unfortunately, we discovered a function in Saxon 11 and 12 that was not adequately controlled by these features. In principle, a stylesheet or query running in Saxon-PE or Saxon-EE could access the local filesystem even if the ALLOWED_PROTOCOLS feature was set to forbid such access. The risk is small: it only applies to untrusted code running in Saxon-PE or Saxon-EE (it does not apply to Saxon-HE) on a system where reading from the local filesystem would be deemed a risk. (We would encourage anyone running untrusted code to use a sandboxed environment where there is no data on the filesystem that needs to be protected from read access.)

Although we judge the risk to be small, At Saxonica, we take security seriously and we are publishing maintenance releases of Saxon 11 and Saxon 12 to close this gap. We urge anyone running untrusted stylesheets or queries under Saxon-PE or Saxon-EE to move to version 11.7 or 12.8 immediately.

This bug is present in the Java, C#, C, C++, Python and PHP products. It is not present in Saxon 10 (including the Saxon.NET 10) or in earlier releases. It is not present in SaxonJS.

Announcing Saxon 12.8!

The Saxon 12.8 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that fixes a security gap and a few other issues that have been addressed since 12.7 was released.

Saxon 12.8 was released on 3 July 2025. This release has been uploaded to the usual locations on the Saxonica website, GitHub, and Maven, PyPi, and NuGet. SaxonCS 12.8 is built with .NET 8.

For a list of the issues resolved in this release, please visit the issue trackers for SaxonJ and SaxonCS or SaxonC on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS is available on NuGet
• Saxon-HE is available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

Issues resolved

In addition to the security issue, only a few other issues have been fixed; our focus was on getting the security release out promptly.

Issues in SaxonJ

Only one additional issue was fixed in SaxonJ:

• 6804 String index out-of-bounds in parse-xml()

Issues in SaxonC

A few small issues were fixed in SaxonC:

• 6835 SaxonC PHP @@VERSION@@
• 6830 SaxonC HE 12.7.0 - PHP - XdmNode->getColumnNumber() returns the line number
• 6823 DocumentBuilder memory not deleted
• 6803 Please provide parseJsonFromString example
• 6802 Remove XdmAtomicValue::getStringValue
• 6801 PRIMITIVE_TYPE defined, but not used?
• 6800 Implement operator== for XdmItem or make it private
• 6785 Instructions in Python README for running pytest are missing the use of a pytest.ini

If you encounter any issues with Saxon 12.8, please report them on our issue tracker.

Announcing Saxon 11.7!

The Saxon 11.7 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that fixes a security gap and a number of other issues that have been addressed since 11.6 was released.

Saxon 11.7 was released on 3 July 2025. This release has been uploaded to the usual locations on the Saxonica website, GitHub, Maven, and NuGet. SaxonCS 11.7 is built with .NET 8.

For a list of the issues resolved in this release, please visit the issue tracker on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• SaxonCS is available on NuGet
• Saxon-HE is no longer distributed on SourceForge. It is now available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

If you encounter any issues with Saxon 11.7, please report them on our issue tracker.

Announcing SaxonJS-HE 3.0.0-beta2!

SaxonJS 3.0 is a major update to the SaxonJS product. In June 2025, we are publishing a second preview release, version 3.0.0-beta2. This is a preview release of the SaxonJS 3.0 HE (Home Edition) product. An EE (Enterprise Edition) product is in the works.

Announcing Saxon 12.7!

The Saxon 12.7 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that addresses a few significant shortcomings in the Saxon 12.6 release.

Saxon 12.7 was released on 16 May 2025. This release has been uploaded to the usual locations on the Saxonica website, GitHub, and Maven, PyPi, and NuGet. SaxonCS 12.7 is built with .NET 8.

For a list of the issues resolved in this release, please visit the issue trackers for SaxonJ and SaxonCS or SaxonC on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS is available on NuGet
• Saxon-HE is available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

Issues resolved

The substantial changes in this release are:

1. We’ve returned to supporting JDK 8 in 12.7. The decision to move to JDK 11 in 12.6 was intentional, but perhaps too eager. Fair warning: it is very unlikely that Saxon 13 will be released with support for JDK 8.
2. We worked around a bug that caused the SaxonC products to fail under X86 emulation on Windows/ARM. (The bug is that Windows emulation doesn’t support some modern instructions that GraalVM was generating. We worked around it by turning down some GraalVM optimizations in that environment.)

Issues in SaxonJ and SaxonCS

These are just the release highlights, for a full list, see the issue tracker.

• 6547 Resolved some schema loading performance regressions
• 6771 Restored JDK 8 compatibility to the class files
• 6776 Resolved a null pointer exception
• 6778 Fixed the class name in the javax.xml.validation.SchemaFactory service

Issues in SaxonC

In addition to the X86 emulation problem, we resolved a few more issues in SaxonC. For a full list, see the issue tracker.

• 6443 Fixed a bug in Python PySaxonProcessor.make_atomic_value
• 6522 The documentation for Saxon\SchemaValidator is incorrect
• 6525 Fixed XdmNode::getChildren()
• 6526 Fixed xdmNode->axisNodes(3) on PHP
• 6536 Fixed segmentation fault with Python SaxonCHE 12.5
• 6780 Accepted suggestion to set sxn_environ values to NULL after allocation
• 6781 Fixed crash on Windows 11 under x86 emulation on ARM
• 6787 The setCatalogFiles method was missing from the C API

If you encounter any issues with Saxon 12.7, please report them on our issue tracker.

Announcing Saxon 12.6!

The Saxon 12.6 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that addresses well over 100 issues and feature requests reported since the Saxon 12.5 release.

Saxon 12.6 was released on 2 May 2025. This release has been uploaded to the usual locations on the Saxonica website, GitHub, and Maven, PyPi, and NuGet. SaxonCS 12.6 is built with .NET 8.

For a list of the issues resolved in this release, please visit the issue trackers for SaxonJ and SaxonCS or SaxonC on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS is available on NuGet
• Saxon-HE is available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

Partial list of issues resolved

This section is a subset of the complete list of resolved issues. It’s curated to bring attention to the bugs that seem most likely to impact customers.

Issues in SaxonJ and SaxonCS

In addition to the individual issues listed below, this release fixes several issues related to streaming transformations and several issues related to tracing.

For a full list, see the issue tracker.

• 6748 Updated xsl:array to track the evolving QT4CG specifications
• 6746 Resolved errors related to version ranges in xsl:use-package/@package-version
• 6724 Clarified limitations on importing schemas for reserved namespaces (such as fn:)
• 6711 Clarified how setting allowedProtocols to restrict parse-xml is handled
• 6696 Resolved a concurrency issue during lazy evaluation
• 6688 Fixed a bug where the coverage report from XSpec creates XML that is not well formed
• 6682 Resolved an issue in XSD uniqueness constraints vs. key constraints
• 6679 Fixed a bug where an incorrect variable was accessed when using xsl:iterate within xsl:accumulator
• 6671 Resolved an issue during schema load with multiple imports
• 6652 parse-xml no longer fails if the string it’s parsing begins with a BOM
• 6621 Clarified how reflexive extension functions and varargs work
• 6597 Fixed a bug where calling getBaseUri() in the Axiom tree model triggers infinite recursion
• 6577 Resolved an issue related to xsl:where-populated and namespace fixup
• 6565 Fixed a performance regression in DocumentFn with Java 12 or higher
• 6544 Fixed a bug where ID/IDREF attributes were not recognized when using the StAX parser
• 6543 Fixed a bug where whitespace text nodes were reported incorrectly when using a pull parser
• 6537 Fixed incorrect rounding of negative xs:double values
• 6504 Clarified how collection() and uri-collection() handle invalid URIs
• 6502 Fixed a bug where several invalid patterns were accepted
• 6494 Fixed a bug where whitespace text output disappeared when indenting
• 6489 Fixed Gizmo issue with prefix, precede, suffix, and follow commands
• 6480 Cardinality of sequences returned by extension functions are now validated
• 6472 Fixed a bug related to sort order in xsl:for-each-group in named templates
• 6471 Corrected the operator precedence of validate expressions
• 6452 Fixed round#2 and round-half-to-even#2 to give correct results on large negative integers

Issues in SaxonC

In the SaxonC 12.6 release, we have included a compiled C++ API library (.dll, .so, .dylib as appropriate) along with accompanying CMake files to simplify integration into C++ applications. This is provided in addition to the core SaxonC library, which continues to be cross-compiled using GraalVM.

To use SaxonC in a C++ project, users now only need the two compiled library files and the header files—greatly reducing setup complexity. Integrating with a project already using CMake is as simple as using FindPackage(SaxonCHE 12.6.0) (Or SaxonCEE, or SaxonCPE, if using the EE or PE editions). A sample CMake project is provided with the samples in the download ZIP.

This change applies only to the C++ API. It does not affect the PHP or Python extensions:

PHP

Installation instructions are included in the README file in the download ZIP and also available in the online documentation.

Python

The extension is distributed as pre-built wheels via PyPI, making installation straightforward using pip.

In addition to the individual issues listed below, this release fixes a number of multithreading issues, encoding problems, and memory leaks. API support has been added for getcwd, getProperty/getProperties, and getJustInTimeCompilation on several objects. There have also been a number of documentation improvements.

For a full list, see the issue tracker.

• 6731 Support adding properties to the Processor in the Saxon C API
• 6695 Fixed an issue related to creating maps of strings in Python
• 6677 Improve error messages associated with Xslt30Processor::compileFromString
• 6676 Support initial template invocation with a combination of tunnel and non-tunnel parameters
• 6668 Support setOutputFile() on SchemaValidator
• 6657 Fixed line and column numbers in PySaxonApiError message
• 6656 Fixed a bug where multiple calls to XdmNode.getParent() could leads to an exception
• 6649 Improved error message associated with an expired license
• 6634 Added support for getcwd and getProperties
• 6628 Fixed a bug where the copy constructor for Xdm objects failed
• 6620 Fixed a double-free bug in clearSettings
• 6619 Resolved missing calls to super constructors
• 6618 Fixed a bug where getDoubleValue crashed for text strings in XdmAtomicValue class
• 6615 Fixed a bug where isEmpty crashed for new empty XdmMap
• 6614 Fixed a bug where the XdmValue::XdmValue constructor crashed
• 6606 Fixed a bug related to cwd and static-base-uri() in XPath
• 6605 Fixed a bug in static-base-uri() when compiling a query from a string
• 6575 Resolved a bug where som exception messages were empty in the PHP API
• 6573 Added isMap, isArray and isFunction methods to the PHP API
• 6562 Fixed issues related to mapSize when casting XdmValue from parseJson to XdmMap
• 6556 Fixed a bug where the standardErrorOutputFile feature was ignored
• 6539 Support PyXdmMap and PyXdmArray on PySaxonProcessor.parse_json
• 6475 Fixed a bug where the PySchemaValidator did not handle an XdmNode input correctly

If you encounter any issues with Saxon 12.6, please report them on our issue tracker.

Announcing SaxonJS-HE 3.0.0-beta1!

SaxonJS 3.0 is a major update to the SaxonJS product. In December 2024, it is being published as a preview release, version 3.0.0-beta1. This is a preview release of the SaxonJS 3.0 HE (Home Edition) product. An EE (Enterprise Edition) product is in the works.

Announcing SaxonJS 2.7!

The SaxonJS 2.7 maintenance release has been published. This is a maintenance release for NodeJS and the browser. It fixes a number of bugs. (Including that one about the spurious warning message. Again.)

Highlights include:

• #4991: Support JSON indentation in xml-to-json
• #5540: Namespace context is reset before each XSLT transformation
• #5743: Text nodes are no longer lost in xsl:catch instruction
• #6234: Corrected the behavior of a map called as a function
• #6318: Fixed an error in parsing regular expressions
• #6352: Resolved a performance issue introduced in SaxonJS 2.6
• #6393: Fixed a string/number comparison bug
• #6418: Improve behavior when attempting to use IXSL extensions on Node.js
• #6516: Fixed some XPath parsing errors related to uncommon expressions (like /[x])

For a complete list of the issues resolved in this release, please visit the issue tracker on the Saxonica support site.

SaxonJS 2.7 was released on 17 October 2024. This release has been uploaded to the usual locations on the Saxonica website and the NPM repository. For more details, please consult the documentation.

If you encounter any issues with SaxonJS 2.7, please report them on our issue tracker.

Announcing Saxon 12.5!

The Saxon 12.5 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that fixes a number of issues reported since previous Saxon 12.4 releases.

Saxon 12.5 was released on 1 July 2024. This release has been uploaded to the usual locations on the Saxonica website, GitHub, and Maven, PyPi, and NuGet. SaxonCS 12.5 is built with .NET 6. This release includes SaxonC and Python releases for the ARM 64 architecture as well as X86-64 architecture.

For a list of the issues resolved in this release, please visit the issue trackers for SaxonJ and SaxonCS or SaxonC on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS is available on NuGet
• Saxon-HE is available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

Partial list of issues resolved

This section is a subset of the complete list of resolved issues. It’s curated to bring attention to the bugs that seem most likely to impact customers.

Issues in SaxonJ and SaxonCS

For a full list, see the issue tracker.

• 6450 CollectionFinder parsesd ALLOWED_PROTOCOLS incorrectly
• 6449 SaxonCS failure when using collection function to pull a collection catalog file over HTTP(S)
• 6448 Saxon-HE 12.4J has wrong column number in trace, unlike Saxon-EE
• 6446 Improved performance of XQuery group by some circumstances
• 6435 Resolve concurrency issue in the use of accumulators behind the scenes in xsl:for-each
• 6428 Output of xsl:on-non-empty changes when using TraceListener
• 6426 fn:matches surprisingly returns false for fn:matches("AB", "^(.*)+B")
• 6420 -Tout filename not used when set on command line
• 6419 Union of nodes in a Template Match produces wrong output in Trace
• 6415 Improved results for trace of an unreferenced XSLT variables
• 6407 Tree Model option -tree seems to be ignored for initial source documents
• 6406 A collection cannot contain the same document more than once
• 6405 Improve saxon:column-number() for text nodes not inside xsl:text
• 6394 Resolve "Duplicate definition of global variable" exception when using compileLibrary on modules which import a common module
• 6386 Resolve inadvertant backwards incompatibility in some uses of Configuration#setFeature
• 6381 set_unprefixed_element_matching_policy(1) doesn't seem to work
• 6380 Internal error when match pattern invoked by xsl:next-match refers to global variable
• 6378 Resolved problem with tracing a variable declared abstract
• 6377 Resolved exception that could be thrown by format-time in some circumstances
• 6370 XSD based validation finds a validation throws NullPointerException when trying to generate a validation report
• 6365 Fixed bug where Gizmo could fail if no license was provided
• 6363 Incorrect result comparing untypedAtomic value to NaN
• 6348 Fixed multi-threading bug related to xsl:result-document operating asynchronously
• 6340 Fixed exception that sometimes arose when using saxon:capture="yes" in an accumlator rule
• 6339 Describe fix and workaround for ArrayIndexOutOfBoundsException in saxon:transform()
• 6313 Static type error from fn:remove()
• 6302 Improved trace output when the transform function is used
• 6286 Resolved problem where $connection?close() could throw an error
• 6279 Incorrect optimization of generate-id() comparisons
• 6256 function-name returns an empty sequence for node-name#0, string#0 and more?
• 6183 Improved documentation for debugging errors when using "fallback=no" on UCA collation

Issues in SaxonC

Memory management in SaxonC, PHP, and Python has been greatly improved. This resolved a number of issues (6338, 6349, 6357, 6396, and 6397). In addition, the following issues were resolved. (For a full list, see the issue tracker.)

• 6439 Fixed bug in Python extension that could cause an AttributeError on PyXdmFunctionItem
• 6402 Added clearXslMessages to clear accumulated xsl:message messages
• 6401 Resolved bug when setting a filename on an executable in Python
• 6372 Updated build to include all character sets (will enable Windows-1252 encoded XML files to be parsed on Linux)
• 6360 Fixed bug where setOutputFile did not work with transformToFile()
• 6356 Fixed argument count error in executable in PHP
• 6351 Added methods for getting the line and column number of a node
• 6342 Fixed bug where in compileFromAssociatedFile PHP might fail
• 6341 Support try/catch in PHP for underlying parse errors
• 6336 Fixed bug when passing array values as parameters in Python
• 6327 Fixed bug where an empty XdmValue in Python might throw a TypeError
• 6297 Fixed build issue on CentOS 7
• 6276 Fixed bug where proc.version did not include the patch version

If you encounter any issues with Saxon 12.5, please report them on our issue tracker.

Announcing SaxonC 12.4.2!

A SaxonC 12.4.2 maintenance release has been published. This release fixes several issues:

• 6197 A segmentation fault in the PHP extension
• 6273 A change in the way whitespace is handled in filenames
• 6274 An problem with the “encoding” keyword in the python saxon processor
• 6277 A build configuration issue for the SaxonC HE Python processor
• 6288 A build issue for the SaxonC PHP extension
• 6294 A segmentation fault parsing JSON
• 6301 A compile error related to memory allocation with some C++ compilers
• 6306 Unreleased memory in the Python processor
• 6324 A segmentation fault in the Python extension

Some efforts have also been made to improve the way dynamic libraries are referenced when using the C/C++ APIs directly. These changes are reflected in the builds and in the scripts that compile the “command” and “samples” applications.

In brief: on macOS, the dynamic library can be accessed through @rpath and on Linux, the dynamic library can be placed in a standard location or accessed with the LD_LIBRARY_PATH environment variable. On Windows, apparently the standard practice is to place the DLL in the same directory as the executable.

For a more complete list of what’s new in 12.4, please see the original release announcement and the SaxonC release notes on the main website.

Announcing SaxonC 12.4.1!

A SaxonC 12.4.1 maintenance release has been published. This release fixes a build error on the Windows platform and includes one additional patch.

I’m an ardent believer in build automation and reproducibility through scripting. We’ve made a lot of progress in this area, but Windows is still a bit “hands on.” Problem is, it was my hands and I messed up.

A while back, we considered upgrading to a newer version of GraalVM. In the course of testing that, I upgraded the version on the Windows build machine. But ultimately, we decided not to make that upgrade.

Despite having an explicit note in my release checklist:

• ☑ Check the version of GraalVM

I missed it on the Windows box. A lot of good detective work went into trying to figure out what was going on, but in the end, just building with the “right” version of GraalVM fixed it. Apologies to the team and everyone else for that.

The 12.4.1 release also includes a partial fix for issues relating to UTF-8 string-based C API functions. Unfortunately, a more complete fix was deemed too risky for what was otherwise an “emergency” release. That fix will have to wait for next time.

For a more complete list of what’s new in 12.4, please see the original release announcement.

Announcing Saxon 12.4!

The Saxon 12.4 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that fixes a number of issues reported since the Saxon 12.3 release. (Note: A 12.4.1 maintenance release of SaxonC was published on 1 December 2023.)

Saxon 12.4 was released on 29 November 2023. This release has been uploaded to the usual locations on the Saxonica website, GitHub, and Maven, PyPi, and NuGet. SaxonCS 12.4 is built with .NET 6. This release includes SaxonC and Python releases for the ARM 64 architecture as well as X86-64 architecture.

For a list of the issues resolved in this release, please visit the issue trackers for SaxonJ and SaxonCS or SaxonC on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS is available on NuGet
• Saxon-HE is available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

Partial list of issues resolved

This section is a subset of the complete list of resolved issues. It’s curated to bring attention to the bugs that seem most likely to impact customers.

Issues in SaxonJ and SaxonCS

For a full list, see the issue tracker.

• 5792 ICU spellout numbering
• 5896 Intermittent failure in multi-threading with XSLT
• 5914 Performance regression in SaxonJ 12, searching for context properties
• 5949 A resource loaded via the resolver vs one loaded "directly" is a different source with different options
• 6049 Does XQueryEvaluator for SaxonCS lack the API to set an ErrorReporter?
• 6082 Saxon 12 XQuery: Issue with compile-time error checking
• 6090 Performance regression SaxonCS 12
• 6094 saxon:eval and saxon:expression no longer available with Saxon 12
• 6116 UncheckedXPathException and missing error codes in output with Saxon-HE 12J
• 6117 Transformation using memo functions fails if the source is an XdmDocument.asSource()
• 6128 Unwanted diagnostic output when validating notations
• 6130 No error is reported for schema-element(*:foo)
• 6131 Unexpected function call triggers cardinality check and error
• 6146 Relative URI resolution in XQuery vs XSLT
• 6147 Incorrect fingerprint for XML_SPACE_TYPE
• 6148 xsi:type and xsi:schemaLocation on same element
• 6149 $connection?close() throws NullPointerException
• 6153 XSD blockDefault effect on complex types
• 6157 xsl:array instruction does not perform fallback processing
• 6158 Errors in xsl:fallback not detected
• 6159 sql:query() throws NullPointerException when retrieving a column with null value
• 6160 Key type in a MapTest cannot be a union type
• 6161 ReportingSingletonIterator.next throws NullPointerException - race condition
• 6165 Spurious template rule ambiguity reported
• 6166 Public fields in a Java instance object cannot be accessed from XSLT
• 6167 Enclosing modes do not work with JIT enabled
• 6168 mode="#all" failures with JIT enabled
• 6176 Failure to test for UncheckedXPathException
• 6186 IndexOutOfBounds exception during stylesheet compilation when package is overridden
• 6196 Functions of wrong arity: arguments → parameters
• 6198 SCM export fails for a schema containing namespace prefixes in an XPath expression
• 6199 SCM export/import sometimes fails for an xs:alternative
• 6201 configuration file: option for unparsed text URI Resolver
• 6202 Invalid attribute names in configuration files are ignored
• 6207 Filter expression not working properly
• 6210 Format of numbers generated by fn:json-to-xml
• 6211 Saxon return wrong error position in XPath expression
• 6212 Serializer tries to guess doctype from content and fails at it.
• 6215 SQL extension: returning the results of a join query
• 6217 Sliding windows: finished windows not output if windows that started earlier are unfinished
• 6221 Static error in XPath expression supplied to xsl:evaluate
• 6225 Significant performance problem for case insensitive regex matching under high concurrency
• 6226 Race condition initialising UnicodeBlocks class
• 6230 fn:transform doesn't use the resource resolver from the XPathContext
• 6231 Saxon does not recognise function annotations written using Q{uri}local syntax
• 6232 Error message: "An empty sequence is not allowed as the result of a call to map"
• 6236 Expected XPathException but got AssertionError 'No current component'
• 6237 HTTP redirection expects an absolute URI in the location field
• 6238 XPath error information is lost in XSLT
• 6239 Function conversion rules: xs:anyURI to xs:string conversion
• 6249 xsl:evaluate/@context-item expression is present, but evaluates to empty sequence
• 6253 Atomized item type for an array (test CastableAs667)
• 6256 function-name returns an empty sequence for node-name#0, string#0 and more?
• 6257 Gizmo quits after certain errors
• 6258 Repeated failures from unparsed-text() / unparsed-text-available()
• 6260 Operator || and fn:concat are not exactly equivalent
• 6265 NPE in net.sf.saxon.functions.Contains

Issues in SaxonC

For a full list, see the issue tracker.

• 6241: Python 3.12 wheels
• 6195: Sources node objects not deleted in the C++ Schema validation samples
• 6174: ICU localization is currently not supported
• 6162: SaxonC does not accept multiple catalog files
• 6144: PyXPathProcessor object has no attribute thisxqptr
• 6143: White space in file path causing an error
• 6118: parseJson API current not supported in SaxonC
• 6109: Give SaxonC XPath API a counterpart to SaxonJ setUnprefixedElementMatchingPolicy
• 6099: Import xslt package currently not available

If you encounter any issues with Saxon 12.4, please report them on our issue tracker.

Announcing SaxonJS 2.6!

The SaxonJS 2.6 maintenance release has been published. This is a maintenance release for NodeJS and the browser. It fixes more than a dozen bugs (including that one about the spurious warning message). Highlights include:

• #5597: ixsl:schedule-action fails without xsl:call-template
• #5714: Update documentation to mention the backtick escaping mechanism
• #5739: Space in string in text template not output as element content
• #5761: fn:transform called from XPath with simplified stylesheet gives an error
• #5855: map:merge with duplicates=combine gives wrong answer
• #5925: Dynamic function lookup runs very slowly
• #5974: SaxonJS documentation does not address namespaces
• #6037: ixsl:schedule-action return objects
• #6107: Can't use namespaced attributes on the root element of the body of a SaxonJS http-request
• #6134: Partial function application call to function in ixsl namespace fails
• #6216: base-uri() value empty for documents async-loaded with ixsl:schedule-action/@http-request
• #6219: base-uri(ixsl:page()) returns empty value

For a complete list of the issues resolved in this release, please visit the issue tracker on the Saxonica support site.

SaxonJS 2.6 was released on 13 October 2023. This release has been uploaded to the usual locations on the Saxonica website and the NPM repository. For more details, please consult the documentation.

If you encounter any issues with SaxonJS 2.6, please report them on our issue tracker.

Announcing Saxon 11.6!

The Saxon 11.6 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that fixes almost 40 issues reported since the 11.5 release.

Saxon 11.6 was released on 24 August 2023. This release has been uploaded to the usual locations on the Saxonica website, GitHub, Maven, and NuGet. SaxonCS 11.6 is built with .NET 6.

For a list of the issues resolved in this release, please visit the issue tracker on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• SaxonCS is available on NuGet
• Saxon-HE is no longer distributed on SourceForge. It is now available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

If you encounter any issues with Saxon 11.6, please report them on our issue tracker.

Announcing Saxon 12.3!

The Saxon 12.3 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that fixes a number of issues reported since the Saxon 12.2 release.

Saxon 12.3 was released on 4 July 2023. This release has been uploaded to the usual locations on the Saxonica website, GitHub, and Maven, PyPi, and NuGet. SaxonCS 12.3 is built with .NET 6. This release includes SaxonC and Python releases for the ARM 64 architecture as well as X86-64 architecture.

For a list of the issues resolved in this release, please visit the issue trackers for SaxonJ and SaxonCS or SaxonC on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS is available on NuGet
• Saxon-HE is no longer distributed on SourceForge. It is now available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

Partial list of issues resolved

This section is a subset of the complete list of resolved issues. It’s curated to bring attention to the bugs that seem most likely to impact customers.

Issues in SaxonJ and SaxonCS

For a full list, see the issue tracker.

• 6003: Inline function expression evaluated using xsl:evaluate
• 6018: UnicodeString - indexWhere does not start from the expected position
• 6022: Eager evaluation prematurely throws exception in analyze-string/non-matching-string.
• 6024: java.lang.NoClassDefFoundError: org/jdom2/Document
• 6033: Invalid warning about field in xs:key
• 6034: Problems with saxon:slice()
• 6036: Undeclaration of default namespace is not reported to a SAXResult
• 6040: Invalid warning displayed when map:contains() is used
• 6054: NamedNodeMap.getNamedItem throw UnsupportedOperationException
• 6059: Bug on "-" castable to xs:duration
• 6061: Crash in SaxonCS using ";n" in regex flags
• 6063: Incorrect attribute indentation
• 6067: Fixed NPE in Saxon HE 12.2
• 6076: Fixed NPE in Saxon HE 12.2
• 6085: Fixed an incomplete path in error messages in a validation report
• 6086: Updated the validation-reports.xsd
• 6091: Fixed an NPE in ContextStackIterator.getMajorCaller
• 6092: Fixed a bug in defaultOpenContent/@appliesToEmpty in XML Schema support
• 6093: Fixed a bug in a predicate with last()
• 6095: Fixed an index out-of-bounds exception when using an accumulator-rule match with variables

Issues in SaxonC

For a full list, see the issue tracker.

• 6017: Interrupted by signal 11: SIGSEGV when PyDocumentBuilder.set_schema_validator is set to None
• 6023: Thread 1 "python3" received signal SIGSEGV, Segmentation fault
• 6025: Python Saxon not releasing memory
• 6053: PydmNode object gets deleted before reuse
• 6075: Unable to read unicodeBlocks.xml file
• 6077: Axis Iterator required on the XdmNode
• 6078: Undefined reference to dlopen@GLIBC_2.34
• 6084: Exception: Initial template parameters can only be of type PyXdmValue
• 6098: SaxonApiException::getSystemId() throws NullPointerException

If you encounter any issues with Saxon 12.3, please report them on our issue tracker.

Announcing Saxon 12.2!

The Saxon 12.2 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that fixes a number of issues reported since the Saxon 12.1 release.

Saxon 12.2 was released on 2 May 2023. This release has been uploaded to the usual locations on the Saxonica website, GitHub, and Maven, PyPi, and NuGet. SaxonCS 12.2 is built with .NET 6. This release includes SaxonC and Python releases for the ARM 64 architecture as well as X86 64 architecture.

For a list of the issues resolved in this release, please visit the issue trackers for SaxonJ and SaxonCS or SaxonC on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS is available on NuGet
• Saxon-HE is no longer distributed on SourceForge. It is now available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

Partial list of issues resolved

This section is a subset of the complete list of resolved issues. It’s curated to bring attention to the bugs that seem most likely to impact customers.

Issues in SaxonJ and SaxonCS

For a full list, see the issue tracker.

• 5997: XSLT version for fn:transform
• 5996: Union types extension is available in Saxon-PE
• 5995: JavaDoc for XPathCompiler.setLanguageVersion should mention 4.0 is accepted
• 5978: StackOverflow during multithreaded schema processing
• 5970: DirectResourceResolver - unresolved XML classpath resources
• 5957: Disabling DTD validation
• 5953: JAXP ValidatorHandler throws an exception if the document is invalid
• 5952: unparsed-text-available throws an un-catchable IllegalCharsetNameException
• 5939: Using -u and a file: URI as the source argument for a query doesn't work
• 5937: Extension function gives NullPointerException in 12.1 when returning empty sequence
• 5931: Remove outdated xml-apis from the Maven artifacts

Issues in SaxonC

For a full list, see the issue tracker.

• 5983: Saxon.C.API/SaxonApiException.cpp calculates wrong strlen
• 5954: The XPath 4.0 function parse-html not available
• 5944: set_cwd on PySchemaValidator seems to be ignored under some circumstances
• 5941: SaxonC EE 12.1 Validate command line tool seems broken; doesn't give any output
• 5938: Trying to compile XSLT from file after setting allowedProtocols raises an NPE
• 5936: Fix exception reporting for Python on Windows
• 5934: Python wheels don’t work in a virtual environment on Windows

If you encounter any issues with Saxon 12.2, please report them on our issue tracker.

Announcing Saxon 12.1!

The Saxon 12.1 maintenance release has been published. This is a maintenance release for Java, C#, C/C++, PHP, and Python that fixes a number of issues reported since the first Saxon 12.0 release, in particular it now runs on Java 8.

Saxon 12.1 was released on 21 March 2023. This release has been uploaded to the usual locations on the Saxonica website, GitHub, and Maven, PyPi, and NuGet. SaxonCS 12.1 is built with .NET 6.

For a list of the issues resolved in this release, please visit the issue trackers for SaxonJ and SaxonCS or SaxonC on the Saxon support site.

Download products:

• Binaries for PE and EE are available from our download pages.
• SaxonJ-HE is available on the Maven Central repository.
• SaxonJ-HE, PE, and EE can also be found on our experimental Maven repository.
• Python wheels for SaxonC (HE, PE, and EE) are available from PyPI.
• SaxonCS is available on NuGet
• Saxon-HE is no longer distributed on SourceForge. It is now available from our open source GitHub repository. The GitHub repository also provides source code for those who need it.

For more details, please consult the documentation.

Partial list of issues resolved

This section is a subset of the complete list of resolved issues. It’s curated to bring attention to the bugs that seem most likely to impact customers.

Issues in SaxonJ and SaxonCS

For a full list, see the issue tracker.

• 5624: SaxonCS validate problem
• 5801: Dependency on axiom pom causes maven-dependency-plugin error
• 5805: Set locator to XmlProcessingIncident
• 5809: NPE on failure to load user-supplied collation class
• 5823: The implemented fn:slice function signature differs from the Saxonica docs and the specification
• 5824: SaxonJ 12.0 does not run with Java 8
• 5839: SaxonCS query problem
• 5852: XML Transformer generates invalid XHTML
• 5880: XQuery error with -p:on command line option
• 5884: SaxonCS 12 doesn't find elements in HTML DOM based on [@class = 'foo'] predicate
• 5906: C# context item absent
• 5908: saxon:for-each-member was dropped in Saxon 11
• 5910: Double reporting of template execution in timing profile
• 5911: SaxonCS crashes when package version number is wrong
• 5913: Tail recursion overwrites value of variable
• 5920: Java reflexive API fails to run, throws ClassNotFoundException

Issues in SaxonC

For a full list, see the issue tracker.

• 5849: transform_to_file() in PyXslt30Processor not working.
• 5850: Error when compiling XSLT that uses "i" flag in regular expressions.
• 5856: Compilation/build issue PHP 8
• 5868: C samples don't build with Ubuntu
• 5869: For Windows SaxonC HE 12.0 there is no bat file to build the C samples

If you encounter any issues with Saxon 12.1, please report them on our issue tracker.