Saxonica Developer Community

This fixes the spurious warning that SaxonJS 2.5 has been issuing for a week or so and about a dozen other bugs. See https://blog.saxonica.com/announcements/2023/10/saxonjs-2.6.html

Saxonica is pleased to announce the release of SaxonJS 2.5 for both Node.js and the browser.

The SaxonJS 2.5 release is a maintenance release containing about a twenty bug fixes.

Notable bug fixes in this SaxonJS release:

• Fixed #5695 where sorting produced different results on Firefox and Chromium-based browsers
• Fixed #5677 where the XX compiler didn’t handle literal sequences of some atomic types
• Fixed #5667 where a newline at the beginning of a string sent to ixsl:eval caused an error
• Fixed #5653 where an empty array was not deemed empty in xsl:where-populated
• Fixed #5597 where a ixsl:schedule-action without a child xsl:call-template failed at runtime
• Fixed #5563 where element content in was allowed xsl:copy-of when a select attribute was also provided
• Fixed #5560 where “intersect” didn’t work correctly on attributes, and some related issues
• Fixed #5554 where some initialization errors were not handled correctly on asynchronous transforms
• Fixed #5544 where setting logLevel on SaxonJS.transform had a global effect
• Fixed #5494 where the ‘parent’ property wasn’t being correctly exposed in the API
• Fixed #5493 where some forms of secondary result documents weren’t supported correctly
• Fixed #5490 where chained transformations raised an runtime type error
• Fixed #4704 where parse-xml failed on the browser if a CDATA section included an XML declaration
• Fixed #5673 where ixsl:set-property couldn’t access properties with names that contained a “.”
• Fixed #5662 where a spurious runtime error could be generated by an invalid axis step
• Fixed #5389 where in-scope namespaces could be constructed incorrectly
• Fixed #5083 where we added support for data: and blob: URIs in the browser

Note: if you’re using Saxon-EE 11 to produce SEFs for use with SaxonJS 2, please use version 11.3 or later, as a number of bugs in compiling to SEF were fixed in the 11.3 maintenance release.

Saxonica is pleased to announce the release of SaxonJS 2.4 for both Node.js and the browser.

The SaxonJS 2.4 release is a maintenance release containing about 30 bug fixes. If you’re using Saxon-EE 11 to produce SEFs for use with SaxonJS 2, please use version 11.3 or later, as a number of bugs in compiling to SEF were fixed in the 11.3 maintenance release.

Notable bug fixes in this SaxonJS release:

• 4755 Pattern x/(a | b) is rejected
• 5036 key() doesn't work on ixsl:page() after ixsl:replace-content?
• 5039 Chaining two XSLTs in the browser doesn’t work
• 5042 xslt3 fails to type check return values from templates
• 5066 Element.localName is not implemented in saxon-js 2.3
• 5074 "XML Parsing Error" when loading SEF file with Saxon-JS 2.3
• 5079 resolve-uri doesn't take static-base-uri of included module into account, even with relocate:off Saxon EE compiled/exported XSLT
• 5081 The omit-xml-declaration serialization property was not always respected
• 5162 Failure when using collations in SaxonJS.XPath.evaluate
• 5190 Incorrect handling of shadowed variable/parameter names in some cases
• 5193 Problems with the arrow operator and fold-left
• 5230 Difficulty using xsl:xpath-default-namespace in conjunction with the key attribute of xsl:map-entry
• 5338 Problem with accumulator access from global variables
• 5387 Adaptive serialization only escapes the first quotation mark in a string
• 5390 document() doesn't remove duplicates
• 5414 Saxon-JS 2.3 doesn't reject xsl:map-entry key="()"
• 5430 Use of deliverResultDocument in SaxonJS.transform options causes error "Unsupported result-document destination undefined"
• 5458 Replacing an HTML document's root element leaves duplicated/empty head/body elements
• 5462 Add "-relocate" command line option for XX compiler (xslt3 package)
• 5464 unparsed-text() with an empty file throws a TypeError
• 5471 Results object from asynchronous SaxonJS.transform does not contain stylesheetInternal

For a more detailed summary of bug fixes, see the release notes: https://www.saxonica.com/saxon-js/release-notes.xml

Saxonica is pleased to announce the release of Saxon-JS 2.3 for both Node.js and the browser.

The Saxon-JS 2.3 release is a maintenance release containing bug fixes. Notable bug fixes in this release:

• 4748, support additional headers with SaxonJS.getResource()
• 5008, resolved XX compiler bug that caused spurious errors
• 5010, make sure base URI has a trailing “/” when used with -xp command line option
• 5017, prefer XML in content negotiation with the document() function
• 5019, fix bug where xml: attributes caused errors in HTML
• 5021, a number of issues involving options to SaxonJS.getResource() and SaxonJS.transform were resolved
• 5024, resolved XX compiler bug that allowed expand-text to slip into imported modules
• 5031, clarify how dots in names are interpreted in ixsl:get and ixsl:set-property
• 5037, resolved XX compiler bug with respect to AVTs
• 5038, resolved XX compiler bug where the base URI could incorrectly be null
• 5046, throw errors if ixsl: functions try to navigate “through” dotted names where the key is absent
• 5058, update the Closure compiler to include DOM 2 functions “createElementNS” and similar as externs so that they don’t get renamed.

For a more detailed summary of bug fixes, see the release notes: https://www.saxonica.com/saxon-js/release-notes.xml

Saxonica is pleased to announce the release of Saxon-JS 2.1 for both Node.js and the browser.

The latest version, Saxon-JS 2.1, is a maintenance release, focused mostly on bug fixes, although there are a few new added features:

• On Node.js, the command line option -json has been added as an alternative to -s. It allows the principal input to be a JSON document. A corresponding API change allows this to be done programmatically.
• On Node.js, the -xp command line option has been added, somewhat experimentally, to allow an XPath expression to be evaluated directly over an XML document.
• On the browser, the set of Window events that an XSLT event handler can respond to has been extended to include the resize and focus events.

This release includes fixes for more than 60 bugs in areas related to JavaScript method invocation, transformation chaining, namespace handling, initial templates and the global context item, HTML responses to scheduled actions, default collations, regular expressions, higher order functions, resource headers, encoding, and serialization.

For a more detailed summary of bug fixes, see the release notes: https://www.saxonica.com/saxon-js/release-notes.xml

For some years we have offered online purchasers the option of buying a single Saxon Enterprise Edition license (product code EE001) at £360, with additional licenses (code EE002) offered at a reduced price of £180. In addition we have offered reduced-cost licenses EET01 (which excludes XQuery-related functionality), EEQ01 (which excludes XSLT-related functionality), and EEV01 (which excludes both).

Navigating your way around the online shop to select these options has never been easy. The software that we now use to create the online shop offers better ways of configuring our product offerings which we haven't been fully exploiting. From 1st December 2020 we will therefore be switching to a new product structure for individual Enterprise Edition licenses:

There will be a single product code that you order.

The headline price for a single license remains at £360 (you can also choose to pay in Euros or US Dollars).

If you choose to buy multiple licenses, the price per license drops to £300 when you buy 2 to 4 licenses, £270 if you buy 5, or £240 if you buy 6 or more.

You can get a 20% saving by excluding XSLT-related functionality, and/or 20% by excluding XQuery-related functionality The standard purchase gives you upgrade and support rights for one year from the date of purchase. You can increase this to two years (premium +50%) or 5 years (premium +150%).

These changes keep the base price for a single license unchanged. The discount for multiple licenses is reduced (for example, buying 5 licenses now costs £1350, compared with £1080 previously), and the discount for choosing reduced functionality is also reduced. But the cost over 2 or 5 years comes down if you choose to extend your upgrade and support rights up front.

The same prices will apply if you order offline via a corporate purchase order.

The price of other licenses (including Professional Edition, site licenses, and redistribution licenses) is unaffected for the time being. We will review these in due course.

We will no longer be accepting purchase orders for individual Professional Edition licenses; these will be available only through the online shop. Site licenses and redistribution licenses for Professional Edition remain available, and can be bought using a corporate purchase order.

To receive notification of new Saxon/C product releases, click on "Watch".

This blog will be used only for routine announcement of new major and minor releases of the software.

To receive notification of new Saxon JS product releases, click on "Watch".

This blog will be used only for routine announcement of new major and minor releases of the software.

List prices for Saxonica's products have been increased today (24 June 2016), in most cases by 20%. This is the first price change since November 2008. During that period the UK retail price index has increased by 22%.

The immediate trigger for the change is of course the volatility in the currency markets caused by the UK's decision to leave the European Union. Saxonica is based in the UK and sets its prices in GBP, but over 90% of our business comes from outside the UK, and many of our contracts with long-term customers are priced in USD or EUR. We don't want to be in the position where these customers are locked into a price that is higher than the price paid by new clients, and an increase in our list prices also reduces our exposure to the uncertainties of rapidly fluctuating currency rates.

Existing contracts, quotations, and invoices will of course be honoured whatever currency they are written in.

We do not expect the UK's decision to leave the EU to have any adverse effect on our business, other than the short-term problems caused by uncertainty and speculation. We have always traded globally, and we have never found that doing business with EU countries is significantly easier (or harder) than with any other country in the world. We benefit greatly from a world in which there are no trade barriers, but our business is global rather than regional.

To receive notification of new Saxon product releases, click on "Watch" (a five-pointed star, top-right of screen)

This news item is used only for routine announcement of new major and minor releases of the software.

For the latest announcements, please scroll to the bottom.