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 XHTML output method is not used by default (that is, not unless explicitly requested) if the principal stylesheet module specifies `version="1.0"`.

If an `xsl:key` definition is in backwards compatible mode (that is, if the stylesheet specifies `version="1.0"`) then the value of the `use` expression in the key definition and the value supplied in the second argument of the `key()` function are both converted to strings before comparison.

In `<xsl:number level="any"/>`, where a `from` pattern is specified that does not match any preceding or ancestor node, Saxon has in the past behaved as if the from pattern selected the root of the tree. In fact the specification is that the instruction should return an empty sequence in this case, and Saxon has been changed to conform to this. (Note that the XSLT 1.0 specification is unclear what should happen here, and XSLT 1.0 processors give varying results.)

Next