As per Dr. Kay’s announcement earlier today on the Saxon-Help mailing list,
SourceForge.net: saxon-help
Saxon 8.8 is available: see http://saxon.sf.net/There’s a long list of changes at
http://www.saxonica.com/documentation/changes/intro.html but most of them
taken individually are fairly small. Saxon now achieves 100% pass rates in
both the W3C XQuery and XSLT 2.0 test suites (a unique achievement), and
many of the changes that were needed to reach this target are in obscure
corner cases that very few users are likely to notice. (Do you really care
about the difference between a float NaN and a double NaN? - the conformance
tests do.)A few highlights:
* the release includes an initial implementation of the draft XQJ interface
(XQuery API for Java)* default collation for XSLT sorting is now Unicode codepoint collation. The
simplest way to revert to the previous collation is to add a lang attribute
to xsl:sort, for example lang=”en”. This change is made so that the default
collation is the same for all interfaces, and for performance reasons: some
sort-intensive stylesheets run at four times the speed with codepoint
collation.*
in the .NET product, extension functions written in C# or other .NET
languages can now be invoked* In XSLT, the namespace URI for newly-constructed elements and attributes
must now be a valid URI* In Saxon-SA there are enhancements to the “streaming” optimization for
handling large documents in XSLT* The serialization pipeline is now highly configurable, by means of a
user-specified SerializerFactory classI have created a Subversion repository on the SourceForge site and my
intention is to maintain patches for bug fixes in the “latest8.8″ branch on
this repository. I’d recommend that users who habitually build Saxon
themselves and apply the latest patches should check out this branch. I
don’t intend to commit my development changes to the SourceForge site until
they’re ready for release - although I may use it for a prerelease when I
feel the code would benefit from early exposure.
Oh, and just in case you missed it,
*
in the .NET product, extension functions written in C# or other .NET
languages can now be invoked
WOOOOOOOOOOOOHOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!!
Gracias Dr. MHK! >:D
