SAXONICA

Saxon Documentation
Full Contents
About Saxon
Changes in this Release
| Version 8.9 (2007-02-12)
| Version 8.8 (2006-09-05)
| Version 8.7.3 (2006-06-13)
| Version 8.7.2 (2006-04-19)
| Version 8.7.1 (2006-04-13)
| Version 8.7 (2006-02-24)
| Version 8.6.1 (24 November 2005)
| Version 8.6 (3 November 2005)
| Version 8.5.1 (26 August 2005)
| Version 8.5 (2 August 2005)
| Version 8.4 (4 April 2005)
| Version 8.3 (11 February 2005)
| Version 8.2 (21 December 2004)
| Version 8.1.1 (8 October 2004)
| Version 8.1 (24 September 2004)
» | Version 8.0 (1 June 2004)
Conditions of Use
Using XSLT 2.0
Using XQuery
Handling Source Documents
XML Schema Processing
XPath API for Java
Saxon on .NET
Extensibility
Saxon Extensions
Sample Saxon Applications
The Saxon SQL Extension
XSLT Elements
XPath 2.0 Expression Syntax
Function Library
Standards Conformance

# XSLT changes

The `as` attribute in `xsl:sequence` has been dropped.

The `unparsed-text()` function returns an empty sequence if the first argument is an empty sequence.

The `xsl:number` instruction now handles numbers that are too large or too small, or values that cannot be converted to integers, as recoverable errors, as described in the current XSLT 2.0 specification. The range of values that can be formatted using the requested format picture is from 1 to 2^63; other values are output as if the string() function were used.

The rules for handling types in `xsl:key` have been brought into line with the current rules in the specification. Because of the way that `eq` is now defined in XPath, a numeric argument to the `key()` function will no longer match an untypedAtomic key value.

The use of a separate name pool for use at compile time has been discontinued. Since standard element and attribute names are no longer stored in the name pool, this technique is no longer needed.

The `xsl:for-each-group` instruction now handles heterogeneous grouping keys as defined in the current specification. Non-comparable grouping key values (for example an integer and a string) are treated as being distinct values.

In backwards compatibility mode (that is, with `version="1.0"`), attribute value templates now observe the first-item rule. That is, `<a val="{1,2,3}"/>` outputs `<a val="1 2 3"/>` in 2.0 mode, but `<a val="1"/>` in 1.0 mode.

Next