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

# Serializer changes

There has been some internal reorganization of the serializer, mainly to perform the various processing steps in the order defined in the W3C specification. One effect is to ensure, as required by the specification, that character maps are not applied to attributes affected by URI escaping in the HTML and XHTML output methods. There are other minor effects on corner cases, for example when Unicode normalization and character maps are used in conjunction.

In the XML serializer, comments and processing instructions are now indented when indentation is requested. Indentation of comments and PIs is now aligned better with the spec; for example the spec does not allow whitespace to be added between a comment and an adjacent text node. In addition, the serializer now tries harder to avoid adding indentation whitespace if there is already suitable whitespace present in the result tree.

If the `method` attribute of `xsl:result-document` is not specified, Saxon now attempts to determine the method to use at compile time when possible - specifically, when the first child of the `xsl:result-document` element is a literal result element.

Next