Saxon Documentation

Full Contents

About Saxon

Changes in this Release

Notices

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
	Introduction
	xsl:analyze-string
	xsl:apply-imports
	xsl:apply-templates
	xsl:attribute
	xsl:attribute-set
	xsl:call-template
	xsl:character-map
	xsl:choose
	xsl:comment
	xsl:copy
	xsl:copy-of
	xsl:decimal-format
	xsl:document
	xsl:element
	xsl:fallback
	xsl:for-each
	xsl:for-each-group
	xsl:function
	xsl:if
	xsl:include
	xsl:import
	xsl:import-schema
	xsl:key
	xsl:matching-substring
	xsl:message
	xsl:namespace
	xsl:namespace-alias
	xsl:next-match
	xsl:non-matching-substring
	xsl:number
	xsl:otherwise
	xsl:output
	xsl:output-character
	xsl:param
	xsl:perform-sort
	xsl:preserve-space
	xsl:processing-instruction
	xsl:result-document
	xsl:sequence
	xsl:sort
	xsl:strip-space
	xsl:stylesheet
	xsl:template
»	xsl:text
	xsl:value-of
	xsl:variable
	xsl:when
	xsl:with-param
	Literal Result Elements
	XSLT Patterns

XPath 2.0 Expression Syntax

Function Library

Standards Conformance

xsl:text

The xsl:text element causes its content to be output.

The main reason for enclosing text within an xsl:text element is to allow white space to be output. White space nodes in the stylesheet are ignored unless they appear immediately within an xsl:text element.

The optional disable-output-escaping attribute may be set to "yes" or "no"; the default is "no". If set to "yes", special characters such as "<" and "&" will be output as themselves, not as entities. Be aware that in general this can produce non-well-formed XML or HTML. It is useful, however, when generating things such as ASP or JSP pages. Escaping may not be disabled when writing to a result tree fragment.

Saxon 7.4 has reverted to the XSLT 1.0 specification of xsl:text: the instruction must contain only text, it cannot contain a child element.