+
+This is the name of the software product that the topic
+ discussed on the reference page belongs to. For example UNIX
+ commands are part of the SunOS x.x
+ release.
+
+
+
+
+
+
+In practice, there are many pages that simply have a version
+ number in the "source" field. So, it looks like what we have is a
+ two-part field,
+ NameVersion,
+ where:
+
+
+
+ Name
+
+
+product name (e.g., BSD) or org. name (e.g., GNU)
+
+
+
+
+ Version
+
+
+version name
+
+
+
+
+
+ Each part is optional. If the Name is a
+ product name, then the Version is probably
+ the version of the product. Or there may be no
+ Name, in which case, if there is a
+ Version, it is probably the version of the
+ item itself, not the product it is part of. Or, if the
+ Name is an organization name, then there
+ probably will be no Version.
+
+
+ Parameters
+
+
+
+ refname
+
+
+The first refname in the refentry
+
+
+
+
+ info
+
+
+A set of info nodes (from a refentry
+ element and its ancestors)
+
+
+
+
+ prefs
+
+
+A node containing users preferences (from global
+ stylesheet parameters)
+
+
+
+
+
+ Returns
+
+Returns a source node.
+
+
+
+
+
+get.refentry.source.name
+Gets source-name metadata for a refentry
+
+
+<xsl:template name="get.refentry.source.name">
+<xsl:param name="refname"/>
+<xsl:param name="info"/>
+<xsl:param name="prefs"/>
+ ...
+</xsl:template>
+
+
+
+A "source name" is one part of a (potentially) two-part
+ NameVersion
+ source field. For more details, see the documentation for the
+ get.refentry.source template.
+
+ Parameters
+
+
+
+ refname
+
+
+The first refname in the refentry
+
+
+
+
+ info
+
+
+A set of info nodes (from a refentry
+ element and its ancestors)
+
+
+
+
+ prefs
+
+
+A node containing users preferences (from global
+ stylesheet parameters)
+
+
+
+
+
+ Returns
+
+Depending on what output method is used for the
+ current stylesheet, either returns a text node or possibly an element
+ node, containing "source name" data.
+
+
+
+
+
+get.refentry.version
+Gets version metadata for a refentry
+
+
+<xsl:template name="get.refentry.version">
+<xsl:param name="refname"/>
+<xsl:param name="info"/>
+<xsl:param name="prefs"/>
+ ...
+</xsl:template>
+
+
+
+A "version" is one part of a (potentially) two-part
+ NameVersion
+ source field. For more details, see the documentation for the
+ get.refentry.source template.
+
+ Parameters
+
+
+
+ refname
+
+
+The first refname in the refentry
+
+
+
+
+ info
+
+
+A set of info nodes (from a refentry
+ element and its ancestors)
+
+
+
+
+ prefs
+
+
+A node containing users preferences (from global
+ stylesheet parameters)
+
+
+
+
+
+ Returns
+
+Depending on what output method is used for the
+ current stylesheet, either returns a text node or possibly an element
+ node, containing "version" data.
+
+
+
+
+
+get.refentry.manual
+Gets source metadata for a refentry
+
+
+<xsl:template name="get.refentry.manual">
+<xsl:param name="refname"/>
+<xsl:param name="info"/>
+<xsl:param name="prefs"/>
+ ...
+</xsl:template>
+
+
+
+The man(7) man page describes this as "the
+ title of the manual (e.g., Linux Programmer's
+ Manual)". Here are some examples from existing man pages:
+
+
+
+
+dpkg utilities
+ (dpkg-name)
+
+
+
+
+User Contributed Perl Documentation
+ (GET)
+
+
+
+
+GNU Development Tools
+ (ld)
+
+
+
+
+Emperor Norton Utilities
+ (ddate)
+
+
+
+
+Debian GNU/Linux manual
+ (faked)
+
+
+
+
+GIMP Manual Pages
+ (gimp)
+
+
+
+
+KDOC Documentation System
+ (qt2kdoc)
+
+
+
+
+
+
+
+
+The solbook(5) man page describes
+ something very much like what man(7) calls
+ "manual", except that solbook(5) names it
+ "sectdesc" and describes it like this:
+
+
+This is the section title of the reference page; for
+ example User Commands.
+
+
+
+
+
+ Parameters
+
+
+
+ refname
+
+
+The first refname in the refentry
+
+
+
+
+ info
+
+
+A set of info nodes (from a refentry
+ element and its ancestors)
+
+
+
+
+ prefs
+
+
+A node containing users preferences (from global
+ stylesheet parameters)
+
+
+
+
+
+ Returns
+
+Returns a manual node.
+
+
+
+
+
+get.refentry.metadata.prefs
+Gets user preferences for refentry metadata gathering
+
+
+<xsl:template name="get.refentry.metadata.prefs"/>
+
+
+
+The DocBook XSL stylesheets include several user-configurable
+ global stylesheet parameters for controlling refentry
+ metadata gathering. Those parameters are not read directly by the
+ other refentry metadata-gathering
+ templates. Instead, they are read only by the
+ get.refentry.metadata.prefs template,
+ which assembles them into a structure that is then passed to
+ the other refentry metadata-gathering
+ templates.
+
+
+
+So the, get.refentry.metadata.prefs
+ template is the only interface to collecting stylesheet parameters for
+ controlling refentry metadata gathering.
+
+ Parameters
+
+There are no local parameters for this template; however, it
+ does rely on a number of global parameters.
+
+ Returns
+
+Returns a manual node.
+
+
+
+
+
+set.refentry.metadata
+Sets content of a refentry metadata item
+
+
+<xsl:template name="set.refentry.metadata">
+<xsl:param name="refname"/>
+<xsl:param name="info"/>
+<xsl:param name="contents"/>
+<xsl:param name="context"/>
+<xsl:param name="preferred"/>
+ ...
+</xsl:template>
+
+
+
+The set.refentry.metadata template is
+ called each time a suitable source element is found for a certain
+ metadata field.
+
+ Parameters
+
+
+
+ refname
+
+
+The first refname in the refentry
+
+
+
+
+ info
+
+
+A single *info node that contains the selected source element.
+
+
+
+
+ contents
+
+
+A node containing the selected source element.
+
+
+
+
+ context
+
+
+A string describing the metadata context in which the
+ set.refentry.metadata template was
+ called: either "date", "source", "version", or "manual".
+
+
+
+
+
+ Returns
+
+Returns formatted contents of a selected source element.
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/common/refentry.xsl b/doc/reference/lib/docbook-xsl-snapshot/common/refentry.xsl
new file mode 100644
index 00000000..5a04b60c
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/common/refentry.xsl
@@ -0,0 +1,1352 @@
+
+
+
+
+
+
+
+
+ Common » Refentry Metadata Template Reference
+
+ $Id: refentry.xsl 7867 2008-03-07 09:54:25Z xmldoc $
+
+
+
+
+ Introduction
+ This is technical reference documentation for the “refentry
+ metadata” templates in the DocBook XSL Stylesheets.
+ This is not intended to be user documentation. It is provided
+ for developers writing customization layers for the stylesheets.
+
+ Currently, only the manpages stylesheets make use of these
+ templates. They are, however, potentially useful elsewhere.
+
+
+
+
+
+
+ Gathers metadata from a refentry and its ancestors
+
+ Reference documentation for particular commands, functions,
+ etc., is sometimes viewed in isolation from its greater "context". For
+ example, users view Unix man pages as, well, individual pages, not as
+ part of a "book" of some kind. Therefore, it is sometimes necessary to
+ embed "context" information in output for each refentry.
+
+ However, one problem is that different users mark up that
+ context information in different ways. Often (usually), the
+ context information is not actually part of the content of the
+ refentry itself, but instead part of the content of a
+ parent or ancestor element to the refentry. And
+ even then, DocBook provides a variety of elements that users might
+ potentially use to mark up the same kind of information. One user
+ might use the productnumber element to mark up version
+ information about a particular product, while another might use
+ the releaseinfo element.
+
+ Taking all that in mind, the
+ get.refentry.metadata template tries to gather
+ metadata from a refentry element and its ancestor
+ elements in an intelligent and user-configurable way. The basic
+ mechanism used in the XPath expressions throughout this stylesheet
+ is to select the relevant metadata from the *info element that is
+ closest to the actual refentry – either on the
+ refentry itself, or on its nearest ancestor.
+
+
+ The get.refentry.metadata
+ template is actually just sort of a "driver" template; it
+ calls other templates that do the actual data collection,
+ then returns the data as a set.
+
+
+
+
+
+
+ refname
+
+ The first refname in the refentry
+
+
+
+ info
+
+ A set of info nodes (from a refentry
+ element and its ancestors)
+
+
+
+ prefs
+
+ A node containing user preferences (from global
+ stylesheet parameters)
+
+
+
+
+
+ Returns a node set with the following elements. The
+ descriptions are verbatim from the man(7) man
+ page.
+
+
+ title
+
+ the title of the man page (e.g., MAN)
+
+
+
+ section
+
+ the section number the man page should be placed in (e.g.,
+ 7)
+
+
+
+ date
+
+ the date of the last revision
+
+
+
+ source
+
+ the source of the command
+
+
+
+ manual
+
+ the title of the manual (e.g., Linux
+ Programmer's Manual)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Gets title metadata for a refentry
+
+ The man(7) man page describes this as "the
+ title of the man page (e.g., MAN). This differs
+ from refname in that, if the refentry has a
+ refentrytitle, we use that as the title;
+ otherwise, we just use first refname in the first
+ refnamediv in the source.
+
+
+
+
+ refname
+
+ The first refname in the refentry
+
+
+
+
+
+ Returns a title node.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Gets section metadata for a refentry
+
+ The man(7) man page describes this as "the
+ section number the man page should be placed in (e.g.,
+ 7)". If we do not find a manvolnum
+ specified in the source, and we find that the refentry is
+ for a function, we use the section number 3
+ ["Library calls (functions within program libraries)"]; otherwise, we
+ default to using 1 ["Executable programs or shell
+ commands"].
+
+
+
+
+ refname
+
+ The first refname in the refentry
+
+
+
+ quiet
+
+ If non-zero, no "missing" message is emitted
+
+
+
+
+
+ Returns a string representing a section number.
+
+
+
+
+
+
+
+
+
+
+
+
+ Note
+
+ meta manvol
+
+ no refentry/refmeta/manvolnum
+
+
+
+ Note
+
+ meta manvol
+
+ see http://docbook.sf.net/el/manvolnum
+
+
+
+
+
+
+
+
+
+ Note
+
+ meta manvol
+
+ Setting man section to 3
+
+
+
+
+ 3
+
+
+ 1
+
+
+
+
+
+
+
+
+ Gets date metadata for a refentry
+
+ The man(7) man page describes this as "the
+ date of the last revision". If we cannot find a date in the source, we
+ generate one.
+
+
+
+
+ refname
+
+ The first refname in the refentry
+
+
+
+ info
+
+ A set of info nodes (from a refentry
+ element and its ancestors)
+
+
+
+ prefs
+
+ A node containing users preferences (from global stylesheet parameters)
+
+
+
+
+
+ Returns a date node.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Gets source metadata for a refentry
+
+ The man(7) man page describes this as "the
+ source of the command", and provides the following examples:
+
+
+ For binaries, use something like: GNU, NET-2, SLS
+ Distribution, MCC Distribution.
+
+
+ For system calls, use the version of the kernel that you are
+ currently looking at: Linux 0.99.11.
+
+
+ For library calls, use the source of the function: GNU, BSD
+ 4.3, Linux DLL 4.4.1.
+
+
+
+
+ The solbook(5) man page describes
+ something very much like what man(7) calls
+ "source", except that solbook(5) names it
+ "software" and describes it like this:
+
+ This is the name of the software product that the topic
+ discussed on the reference page belongs to. For example UNIX
+ commands are part of the SunOS x.x
+ release.
+
+
+
+ In practice, there are many pages that simply have a version
+ number in the "source" field. So, it looks like what we have is a
+ two-part field,
+ NameVersion,
+ where:
+
+
+ Name
+
+ product name (e.g., BSD) or org. name (e.g., GNU)
+
+
+
+ Version
+
+ version name
+
+
+
+ Each part is optional. If the Name is a
+ product name, then the Version is probably
+ the version of the product. Or there may be no
+ Name, in which case, if there is a
+ Version, it is probably the version of the
+ item itself, not the product it is part of. Or, if the
+ Name is an organization name, then there
+ probably will be no Version.
+
+
+
+
+
+ refname
+
+ The first refname in the refentry
+
+
+
+ info
+
+ A set of info nodes (from a refentry
+ element and its ancestors)
+
+
+
+ prefs
+
+ A node containing users preferences (from global
+ stylesheet parameters)
+
+
+
+
+
+ Returns a source node.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Warn
+
+ meta source
+
+ using
+ "
+
+ "
+ for "source"
+
+
+
+
+
+
+
+ [FIXME: source]
+
+
+ Warn
+
+ meta source
+
+ no fallback for source, so inserted a fixme
+
+
+
+
+
+
+
+
+
+ [FIXME: source]
+
+
+ Warn
+
+ meta source
+
+ no source fallback given, so inserted a fixme
+
+
+
+
+
+
+
+
+
+ Gets source-name metadata for a refentry
+
+ A "source name" is one part of a (potentially) two-part
+ NameVersion
+ source field. For more details, see the documentation for the
+ get.refentry.source template.
+
+
+
+
+ refname
+
+ The first refname in the refentry
+
+
+
+ info
+
+ A set of info nodes (from a refentry
+ element and its ancestors)
+
+
+
+ prefs
+
+ A node containing users preferences (from global
+ stylesheet parameters)
+
+
+
+
+
+ Depending on what output method is used for the
+ current stylesheet, either returns a text node or possibly an element
+ node, containing "source name" data.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ source
+
+
+
+
+
+
+
+ source
+ productname
+
+
+
+
+
+
+
+ source
+ productname
+
+
+
+
+
+
+
+ source
+ productname
+
+
+
+
+
+
+
+ source
+ productname
+
+
+
+
+
+
+
+ source
+ productname
+
+
+
+
+
+
+
+
+
+
+
+
+ Note
+
+ meta source
+
+ no *info/productname or alternative
+
+
+
+ Note
+
+ meta source
+
+ see http://docbook.sf.net/el/productname
+
+
+
+ Note
+
+ meta source
+
+ no refentry/refmeta/refmiscinfo@class=source
+
+
+
+ Note
+
+ meta source
+
+ see http://docbook.sf.net/el/refmiscinfo
+
+
+
+
+
+
+ Gets version metadata for a refentry
+
+ A "version" is one part of a (potentially) two-part
+ NameVersion
+ source field. For more details, see the documentation for the
+ get.refentry.source template.
+
+
+
+
+ refname
+
+ The first refname in the refentry
+
+
+
+ info
+
+ A set of info nodes (from a refentry
+ element and its ancestors)
+
+
+
+ prefs
+
+ A node containing users preferences (from global
+ stylesheet parameters)
+
+
+
+
+
+ Depending on what output method is used for the
+ current stylesheet, either returns a text node or possibly an element
+ node, containing "version" data.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ version
+
+
+
+
+
+
+
+ version
+ productnumber
+
+
+
+
+
+
+
+ version
+ productnumber
+
+
+
+
+
+
+
+
+
+
+
+
+ Note
+
+ meta version
+
+ no *info/productnumber or alternative
+
+
+
+ Note
+
+ meta version
+
+ see http://docbook.sf.net/el/productnumber
+
+
+
+ Note
+
+ meta version
+
+ no refentry/refmeta/refmiscinfo@class=version
+
+
+
+ Note
+
+ meta version
+
+ see http://docbook.sf.net/el/refmiscinfo
+
+
+
+
+
+
+ Gets source metadata for a refentry
+
+ The man(7) man page describes this as "the
+ title of the manual (e.g., Linux Programmer's
+ Manual)". Here are some examples from existing man pages:
+
+
+ dpkg utilities
+ (dpkg-name)
+
+
+ User Contributed Perl Documentation
+ (GET)
+
+
+ GNU Development Tools
+ (ld)
+
+
+ Emperor Norton Utilities
+ (ddate)
+
+
+ Debian GNU/Linux manual
+ (faked)
+
+
+ GIMP Manual Pages
+ (gimp)
+
+
+ KDOC Documentation System
+ (qt2kdoc)
+
+
+
+
+ The solbook(5) man page describes
+ something very much like what man(7) calls
+ "manual", except that solbook(5) names it
+ "sectdesc" and describes it like this:
+
+ This is the section title of the reference page; for
+ example User Commands.
+
+
+After building a PDF file with this sort of odd-looking index, you can
+extract the text from the PDF file and the result is a proper index expressed in
+XML.
+
+Now you have data that's amenable to processing and a simple Perl script
+(such as fo/pdf2index) can
+merge page ranges and generate a proper index.
+
+Finally, reformat your original document using this literal index instead of
+an automatically generated one and bingo!
+
+
+
+
+
+
+index.method
+list
+basic
+kosek
+kimber
+
+
+index.method
+Select method used to group index entries in an index
+
+
+
+
+<xsl:param name="index.method">basic</xsl:param>
+
+
+
+Description
+
+This parameter lets you select which method to use for sorting and grouping
+ index entries in an index.
+Indexes in Latin-based languages that have accented characters typically
+sort together accented words and unaccented words.
+Thus Á (U+00C1 LATIN CAPITAL LETTER A WITH ACUTE) would sort together
+with A (U+0041 LATIN CAPITAL LETTER A), so both would appear in the A
+section of the index.
+Languages using other alphabets (such as Russian, which is written in the Cyrillic alphabet)
+and languages using ideographic chararacters (such as Japanese)
+require grouping specific to the languages and alphabets.
+
+
+The default indexing method is limited.
+It can group accented characters in Latin-based languages only.
+It cannot handle non-Latin alphabets or ideographic languages.
+The other indexing methods require extensions of one type or
+another, and do not work with
+all XSLT processors, which is why they are not used by default.
+
+The three choices for indexing method are:
+
+
+basic
+
+
+(default) Sort and groups words based only on the Latin alphabet.
+Words with accented Latin letters will group and sort with
+their respective primary letter, but
+words in non-Latin alphabets will be
+put in the Symbols section of the index.
+
+
+
+
+kosek
+
+
+This method sorts and groups words based on letter groups configured in
+the DocBook locale file for the given language.
+See, for example, the French locale file common/fr.xml.
+This method requires that the XSLT processor
+supports the EXSLT extensions (most do).
+It also requires support for using
+user-defined functions in xsl:key (xsltproc does not).
+
+This method is suitable for any language for which you can
+list all the individual characters that should appear
+in each letter group in an index.
+It is probably not practical to use it for ideographic languages
+such as Chinese that have hundreds or thousands of characters.
+
+
+To use the kosek method, you must:
+
+
+
+Use a processor that supports its extensions, such as
+Saxon 6 or Xalan (xsltproc and Saxon 8 do not).
+
+
+
+Set the index.method parameter's value to kosek.
+
+
+
+Import the appropriate index extensions stylesheet module
+fo/autoidx-kosek.xsl or
+html/autoidx-kosek.xsl into your
+customization.
+
+
+
+
+
+
+
+kimber
+
+
+This method uses extensions to the Saxon processor to implement
+sophisticated indexing processes. It uses its own
+configuration file, which can include information for any number of
+languages. Each language's configuration can group
+words using one of two processes. In the
+enumerated process similar to that used in the kosek method,
+you indicate the groupings character-by-character.
+In the between-key process, you specify the
+break-points in the sort order that should start a new group.
+The latter configuration is useful for ideographic languages
+such as Chinese, Japanese, and Korean.
+You can also define your own collation algorithms and how you
+want mixed Latin-alphabet words sorted.
+
+
+For a whitepaper describing the extensions, see:
+http://www.innodata-isogen.com/knowledge_center/white_papers/back_of_book_for_xsl_fo.pdf.
+
+
+
+To download the extension library, see
+http://www.innodata-isogen.com/knowledge_center/tools_downloads/i18nsupport.
+
+
+
+
+To use the kimber method, you must:
+
+
+
+Use Saxon (version 6 or 8) as your XSLT processor.
+
+
+
+Install and configure the Innodata Isogen library, using
+the documentation that comes with it.
+
+
+
+Set the index.method parameter's value to kimber.
+
+
+
+Import the appropriate index extensions stylesheet module
+fo/autoidx-kimber.xsl or
+html/autoidx-kimber.xsl into your
+customization.
+
+
+
+
+
+
+
+
+
+
+
+
+
+index.on.type
+boolean
+
+
+index.on.type
+Select indexterms based on type
+attribute value
+
+
+
+
+<xsl:param name="index.on.type" select="0"></xsl:param>
+
+
+
+Description
+
+
+If non-zero,
+then an index element that has a
+type attribute
+value will contain only those indexterm
+elements with a matching type attribute value.
+If an index has no type
+attribute or it is blank, then the index will contain
+all indexterms in the current scope.
+
+
+
+If index.on.type is zero, then the
+type attribute has no effect
+on selecting indexterms for an index.
+
+
+For those using DocBook version 4.2 or earlier,
+the type attribute is not available
+for index terms. However, you can achieve the same
+effect by using the role attribute
+in the same manner on indexterm
+and index, and setting the stylesheet parameter
+index.on.role to a nonzero value.
+
+
+
+
+
+
+
+index.on.role
+boolean
+
+
+index.on.role
+Select indexterms based on role value
+
+
+
+
+<xsl:param name="index.on.role" select="0"></xsl:param>
+
+
+
+Description
+
+
+If non-zero,
+then an index element that has a
+role attribute
+value will contain only those indexterm
+elements with a matching role value.
+If an index has no role
+attribute or it is blank, then the index will contain
+all indexterms in the current scope.
+
+
+If index.on.role is zero, then the
+role attribute has no effect
+on selecting indexterms for an index.
+
+
+If you are using DocBook version 4.3 or later, you should
+use the type attribute instead of role
+on indexterm and index,
+and set the index.on.type to a nonzero
+value.
+
+
+
+
+
+
+
+index.preferred.page.properties
+attribute set
+
+
+index.preferred.page.properties
+Properties used to emphasize page number references for
+significant index terms
+
+
+
+
+<xsl:attribute-set name="index.preferred.page.properties">
+ <xsl:attribute name="font-weight">bold</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Properties used to emphasize page number references for
+significant index terms (significance=preferred). Currently works only with
+XEP.
+
+
+
+
+
+
+index.entry.properties
+attribute set
+
+
+index.entry.properties
+Properties applied to the formatted entries
+in an index
+
+
+
+
+<xsl:attribute-set name="index.entry.properties">
+ <xsl:attribute name="start-indent">0pt</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+This attribute set is applied to the block containing
+the entries in a letter division in an index. It can be used to set the
+font-size, font-family, and other inheritable properties that will be
+applied to all index entries.
+
+
+
+
+
+
+index.div.title.properties
+attribute set
+
+
+index.div.title.properties
+Properties associated with the letter headings in an
+index
+
+
+
+
+<xsl:attribute-set name="index.div.title.properties">
+ <xsl:attribute name="margin-left">0pt</xsl:attribute>
+ <xsl:attribute name="font-size">14.4pt</xsl:attribute>
+ <xsl:attribute name="font-family"><xsl:value-of select="$title.fontset"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="font-weight">bold</xsl:attribute>
+ <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
+ <xsl:attribute name="space-before.optimum"><xsl:value-of select="concat($body.font.master,'pt')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="space-before.minimum"><xsl:value-of select="concat($body.font.master,'pt * 0.8')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="space-before.maximum"><xsl:value-of select="concat($body.font.master,'pt * 1.2')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="start-indent">0pt</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+This attribute set is used on the letter headings that separate
+the divisions in an index.
+
+
+
+
+
+
+index.number.separator
+string
+
+
+index.number.separator
+Override for punctuation separating page numbers in index
+
+
+
+
+<xsl:param name="index.number.separator"></xsl:param>
+
+
+
+Description
+
+This parameter permits you to override the text to insert between
+page references in a formatted index entry. Typically
+that would be a comma and a space.
+
+
+Because this text may be locale dependent,
+this parameter's value is normally taken from a gentext
+template named 'number-separator' in the
+context 'index' in the stylesheet
+locale file for the language
+of the current document.
+This parameter can be used to override the gentext string,
+and would typically be used on the command line.
+This parameter would apply to all languages.
+
+
+So this text string can be customized in two ways.
+You can reset the default gentext string using
+the local.l10n.xml parameter, or you can
+override the gentext with the content of this parameter.
+The content can be a simple string, or it can be
+something more complex such as a call-template.
+
+
+In HTML index output, section title references are used instead of
+page number references. This punctuation appears between
+such section titles in an HTML index.
+
+
+
+
+
+
+
+index.range.separator
+string
+
+
+index.range.separator
+Override for punctuation separating the two numbers
+in a page range in index
+
+
+
+
+<xsl:param name="index.range.separator"></xsl:param>
+
+
+
+Description
+
+This parameter permits you
+to override the text to insert between
+the two numbers of a page range in an index.
+This parameter is only used by those XSL-FO processors
+that support an extension for generating such page ranges
+(such as XEP).
+
+Because this text may be locale dependent,
+this parameter's value is normally taken from a gentext
+template named 'range-separator' in the
+context 'index' in the stylesheet
+locale file for the language
+of the current document.
+This parameter can be used to override the gentext string,
+and would typically be used on the command line.
+This parameter would apply to all languages.
+
+
+So this text string can be customized in two ways.
+You can reset the default gentext string using
+the local.l10n.xml parameter, or you can
+override the gentext with the content of this parameter.
+The content can be a simple string, or it can be
+something more complex such as a call-template.
+
+
+In HTML index output, section title references are used instead of
+page number references. So there are no page ranges
+and this parameter has no effect.
+
+
+
+
+
+
+
+index.term.separator
+string
+
+
+index.term.separator
+Override for punctuation separating an index term
+from its list of page references in an index
+
+
+
+
+<xsl:param name="index.term.separator"></xsl:param>
+
+
+
+Description
+
+This parameter permits you to override
+the text to insert between
+the end of an index term and its list of page references.
+Typically that might be a comma and a space.
+
+
+Because this text may be locale dependent,
+this parameter's value is normally taken from a gentext
+template named 'term-separator' in the
+context 'index' in the stylesheet
+locale file for the language
+of the current document.
+This parameter can be used to override the gentext string,
+and would typically be used on the command line.
+This parameter would apply to all languages.
+
+
+So this text string can be customized in two ways.
+You can reset the default gentext string using
+the local.l10n.xml parameter, or you can
+fill in the content for this normally empty
+override parameter.
+The content can be a simple string, or it can be
+something more complex such as a call-template.
+For fo output, it could be an fo:leader
+element to provide space of a specific length, or a dot leader.
+
+
+
+
+
+
+
+xep.index.item.properties
+attribute set
+
+
+xep.index.item.properties
+Properties associated with XEP index-items
+
+
+
+
+<xsl:attribute-set name="xep.index.item.properties" use-attribute-sets="index.page.number.properties">
+ <xsl:attribute name="merge-subsequent-page-numbers">true</xsl:attribute>
+ <xsl:attribute name="link-back">true</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Properties associated with XEP index-items, which generate
+page numbers in an index processed by XEP. For more info see
+the XEP documentation section "Indexes" in
+http://www.renderx.com/reference.html#Indexes.
+
+This attribute-set also adds by default any properties from the
+index.page.number.properties
+attribute-set.
+
+
+
+
+
+toc.section.depth
+integer
+
+
+toc.section.depth
+How deep should recursive sections appear
+in the TOC?
+
+
+
+<xsl:param name="toc.section.depth">2</xsl:param>
+
+
+Description
+
+Specifies the depth to which recursive sections should appear in the
+TOC.
+
+
+
+
+
+
+
+toc.max.depth
+integer
+
+
+toc.max.depth
+How many levels should be created for each TOC?
+
+
+
+<xsl:param name="toc.max.depth">8</xsl:param>
+
+
+Description
+
+Specifies the maximal depth of TOC on all levels.
+
+
+
+
+
+
+toc.indent.width
+float
+
+
+toc.indent.width
+Amount of indentation for TOC entries
+
+
+
+
+<xsl:param name="toc.indent.width">24</xsl:param>
+<!-- inconsistant point specification? -->
+
+
+
+Description
+
+Specifies, in points, the distance by which each level of the
+TOC is indented from its parent.
+
+This value is expressed in points, without
+a unit (in other words, it is a bare number). Using a bare number allows the stylesheet
+to perform calculations that would otherwise have to be performed by the FO processor
+because not all processors support expressions.
+
+
+
+
+
+
+toc.line.properties
+attribute set
+
+
+toc.line.properties
+Properties for lines in ToC and LoTs
+
+
+
+
+<xsl:attribute-set name="toc.line.properties">
+ <xsl:attribute name="text-align-last">justify</xsl:attribute>
+ <xsl:attribute name="text-align">start</xsl:attribute>
+ <xsl:attribute name="end-indent"><xsl:value-of select="concat($toc.indent.width, 'pt')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="last-line-end-indent"><xsl:value-of select="concat('-', $toc.indent.width, 'pt')"></xsl:value-of></xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Properties which are applied to every line in ToC (or LoT). You can
+modify them in order to change appearance of all, or some lines. For
+example in order to make lines for chapters in bold specify the
+following in your customization layer.
+
+<xsl:attribute-set name="toc.line.properties">
+ <xsl:attribute name="font-weight">
+ <xsl:when test="self::chapter | self::preface | self::appendix">bold</xsl:when>
+ <xsl:otherwise>normal</xsl:otherwise>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+
+
+
+toc.margin.properties
+attribute set
+
+
+toc.margin.properties
+Margin properties used on Tables of Contents
+
+
+
+
+<xsl:attribute-set name="toc.margin.properties">
+ <xsl:attribute name="space-before.minimum">0.5em</xsl:attribute>
+ <xsl:attribute name="space-before.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">2em</xsl:attribute>
+ <xsl:attribute name="space-after.minimum">0.5em</xsl:attribute>
+ <xsl:attribute name="space-after.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-after.maximum">2em</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+This attribute set is used on Tables of Contents. These attributes are set
+on the wrapper that surrounds the ToC block, not on each individual lines.
+
+
+
+
+
+bridgehead.in.toc
+boolean
+
+
+bridgehead.in.toc
+Should bridgehead elements appear in the TOC?
+
+
+
+<xsl:param name="bridgehead.in.toc" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, bridgeheads appear in the TOC. Note that
+this option is not fully supported and may be removed in a future
+version of the stylesheets.
+
+
+
+
+
+
+
+simplesect.in.toc
+boolean
+
+
+simplesect.in.toc
+Should simplesect elements appear in the TOC?
+
+
+
+<xsl:param name="simplesect.in.toc" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, simplesects will be included in the TOC.
+
+
+
+
+
+
+
+generate.section.toc.level
+integer
+
+
+generate.section.toc.level
+Control depth of TOC generation in sections
+
+
+
+
+<xsl:param name="generate.section.toc.level" select="0"></xsl:param>
+
+
+
+Description
+
+The generate.section.toc.level parameter
+controls the depth of section in which TOCs will be generated. Note
+that this is related to, but not the same as
+toc.section.depth, which controls the depth to
+which TOC entries will be generated in a given TOC.
+If, for example, generate.section.toc.level
+is 3, TOCs will be generated in first, second, and third
+level sections, but not in fourth level sections.
+
+
+
+
+
+
+
+
+
+Processor Extensions
+
+
+arbortext.extensions
+boolean
+
+
+arbortext.extensions
+Enable Arbortext extensions?
+
+
+
+<xsl:param name="arbortext.extensions" select="0"></xsl:param>
+
+
+Description
+
+If non-zero,
+Arbortext
+extensions will be used.
+
+This parameter can also affect which graphics file formats
+are supported
+
+
+
+
+
+
+axf.extensions
+boolean
+
+
+axf.extensions
+Enable XSL Formatter extensions?
+
+
+
+
+<xsl:param name="axf.extensions" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero,
+XSL Formatter
+extensions will be used. XSL Formatter extensions consists of PDF bookmarks,
+document information and better index processing.
+
+This parameter can also affect which graphics file formats
+are supported
+
+
+
+
+
+
+fop.extensions
+boolean
+
+
+fop.extensions
+Enable extensions for FOP version 0.20.5 and earlier
+
+
+
+<xsl:param name="fop.extensions" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, extensions intended for
+FOP
+version 0.20.5 and earlier will be used.
+At present, this consists of PDF bookmarks.
+
+
+This parameter can also affect which graphics file formats
+are supported.
+
+If you are using a version of FOP beyond
+version 0.20.5, then use the fop1.extensions parameter
+instead.
+
+
+
+
+
+
+fop1.extensions
+boolean
+
+
+fop1.extensions
+Enable extensions for FOP version 0.90 and later
+
+
+
+<xsl:param name="fop1.extensions" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, extensions for
+FOP
+version 0.90 and later will be used.
+
+
+This parameter can also affect which graphics file formats
+are supported.
+
+The original fop.extensions parameter
+should still be used for FOP version 0.20.5 and earlier.
+
+
+
+
+
+
+passivetex.extensions
+boolean
+
+
+passivetex.extensions
+Enable PassiveTeX extensions?
+
+
+
+<xsl:param name="passivetex.extensions" select="0"></xsl:param>
+
+
+Description
+
+If non-zero,
+PassiveTeX
+extensions will be used. At present, this consists of PDF bookmarks
+and sorted index terms.
+
+
+This parameter can also affect which graphics file formats
+are supported
+
+
+ PassiveTeX is incomplete and development has ceased. In most cases,
+another XSL-FO engine is probably a better choice.
+
+
+
+
+
+
+
+tex.math.in.alt
+list
+plain
+latex
+
+
+tex.math.in.alt
+TeX notation used for equations
+
+
+
+
+<xsl:param name="tex.math.in.alt"></xsl:param>
+
+
+
+Description
+
+If you want type math directly in TeX notation in equations,
+this parameter specifies notation used. Currently are supported two
+values -- plain and latex. Empty
+value means that you are not using TeX math at all.
+
+Preferred way for including TeX alternative of math is inside of
+textobject element. Eg.:
+
+<inlineequation>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="eq1.gif"/>
+</imageobject>
+<textobject><phrase>E=mc squared</phrase></textobject>
+<textobject role="tex"><phrase>E=mc^2</phrase></textobject>
+</inlinemediaobject>
+</inlineequation>
+
+If you are using graphic element, you can
+store TeX inside alt element:
+
+<inlineequation>
+<alt role="tex">a^2+b^2=c^2</alt>
+<graphic fileref="a2b2c2.gif"/>
+</inlineequation>
+
+If you want use this feature, you should process your FO with
+PassiveTeX, which only supports TeX math notation. When calling
+stylsheet, don't forget to specify also
+passivetex.extensions=1.
+
+If you want equations in HTML, just process generated file
+tex-math-equations.tex by TeX or LaTeX. Then run
+dvi2bitmap program on result DVI file. You will get images for
+equations in your document.
+
+
+ This feature is useful for print/PDF output only if you
+ use the obsolete and now unsupported PassiveTeX XSL-FO
+ engine.
+
+
+
+
+Related Parameters
+ tex.math.delims,
+ passivetex.extensions,
+ tex.math.file
+
+More information
+ For how-to documentation on embedding TeX equations and
+ generating output from them, see
+ DBTeXMath.
+
+
+
+
+
+tex.math.delims
+boolean
+
+
+tex.math.delims
+Should equations output for processing by TeX be
+surrounded by math mode delimiters?
+
+
+
+
+<xsl:param name="tex.math.delims" select="1"></xsl:param>
+
+
+
+Description
+
+For compatibility with DSSSL based DBTeXMath from Allin Cottrell
+you should set this parameter to 0.
+
+
+Related Parameters
+ tex.math.in.alt,
+ passivetex.extensions
+
+
+See Also
+ You can also use the dbtex delims processing
+ instruction to control whether delimiters are output.
+
+More information
+ For how-to documentation on embedding TeX equations and
+ generating output from them, see
+ DBTeXMath.
+
+
+
+
+
+xep.extensions
+boolean
+
+
+xep.extensions
+Enable XEP extensions?
+
+
+
+<xsl:param name="xep.extensions" select="0"></xsl:param>
+
+
+Description
+
+If non-zero,
+XEP
+extensions will be used. XEP extensions consists of PDF bookmarks,
+document information and better index processing.
+
+
+This parameter can also affect which graphics file formats
+are supported
+
+
+
+
+Stylesheet Extensions
+
+
+linenumbering.everyNth
+integer
+
+
+linenumbering.everyNth
+Indicate which lines should be numbered
+
+
+
+
+<xsl:param name="linenumbering.everyNth">5</xsl:param>
+
+
+
+Description
+
+If line numbering is enabled, everyNth line will be
+numbered. Note that numbering is one based, not zero based.
+
+
+
+
+
+
+
+linenumbering.extension
+boolean
+
+
+linenumbering.extension
+Enable the line numbering extension
+
+
+
+
+<xsl:param name="linenumbering.extension" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, verbatim environments (address, literallayout,
+programlisting, screen, synopsis) that specify line numbering will
+have line numbers.
+
+
+
+
+
+
+
+linenumbering.separator
+string
+
+
+linenumbering.separator
+Specify a separator between line numbers and lines
+
+
+
+
+<xsl:param name="linenumbering.separator"><xsl:text> </xsl:text></xsl:param>
+
+
+
+Description
+
+The separator is inserted between line numbers and lines in the
+verbatim environment. The default value is a single white space.
+ Note the interaction with linenumbering.width
+
+
+
+
+
+
+
+linenumbering.width
+integer
+
+
+linenumbering.width
+Indicates the width of line numbers
+
+
+
+
+<xsl:param name="linenumbering.width">3</xsl:param>
+
+
+
+Description
+
+If line numbering is enabled, line numbers will appear right
+justified in a field "width" characters wide.
+
+
+
+
+
+
+
+tablecolumns.extension
+boolean
+
+
+tablecolumns.extension
+Enable the table columns extension function
+
+
+
+
+<xsl:param name="tablecolumns.extension" select="1"></xsl:param>
+
+
+
+Description
+
+The table columns extension function adjusts the widths of table
+columns in the HTML result to more accurately reflect the specifications
+in the CALS table.
+
+
+
+
+
+
+
+ textinsert.extension
+ boolean
+
+
+ textinsert.extension
+ Enables the textinsert extension element
+
+
+
+ <xsl:param name="textinsert.extension" select="1"></xsl:param>
+
+
+ Description
+ The textinsert extension element inserts the contents of
+ a file into the result tree (as text).
+
+ To use the textinsert extension element, you must use
+ either Saxon or Xalan as your XSLT processor (it doesn’t
+ work with xsltproc), along with either the DocBook Saxon
+ extensions or DocBook Xalan extensions (for more
+ information about those extensions, see DocBook Saxon Extensions and DocBook Xalan Extensions), and you must set both
+ the use.extensions and
+ textinsert.extension parameters to
+ 1.
+ As an alternative to using the textinsert element,
+ consider using an Xinclude element with the
+ parse="text" attribute and value
+ specified, as detailed in Using XInclude for text inclusions.
+
+
+ See Also
+ You can also use the dbhtml-include href processing
+ instruction to insert external files — both files containing
+ plain text and files with markup content (including HTML
+ content).
+
+ More information
+ For how-to documentation on inserting contents of
+ external code files and other text files into output, see
+ External code files.
+ For guidelines on inserting contents of
+ HTML files into output, see Inserting external HTML code.
+
+
+
+
+
+textdata.default.encoding
+string
+
+
+textdata.default.encoding
+Default encoding of external text files which are included
+using textdata element
+
+
+
+
+<xsl:param name="textdata.default.encoding"></xsl:param>
+
+
+
+Description
+
+Specifies the encoding of any external text files included using
+textdata element. This value is used only when you do
+not specify encoding by the appropriate attribute
+directly on textdata. An empty string is interpreted as the system
+default encoding.
+
+
+
+
+
+
+use.extensions
+boolean
+
+
+use.extensions
+Enable extensions
+
+
+
+
+<xsl:param name="use.extensions" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, extensions may be used. Each extension is
+further controlled by its own parameter. But if
+use.extensions is zero, no extensions will
+be used.
+
+
+
+
+
+
+Automatic labelling
+
+
+appendix.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+appendix.autolabel
+Specifies the labeling format for Appendix titles
+
+
+
+
+<xsl:param name="appendix.autolabel">A</xsl:param>
+
+
+
+Description
+
+If non-zero, then appendices will be numbered using the
+parameter value as the number format if the value matches one of the
+following:
+
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+
+Any nonzero value other than the above will generate
+the default number format (upperalpha).
+
+
+
+
+
+
+
+chapter.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+chapter.autolabel
+Specifies the labeling format for Chapter titles
+
+
+
+
+<xsl:param name="chapter.autolabel" select="1"></xsl:param>
+
+
+Description
+
+If non-zero, then chapters will be numbered using the parameter
+value as the number format if the value matches one of the following:
+
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+
+Any nonzero value other than the above will generate
+the default number format (arabic).
+
+
+
+
+
+
+
+part.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+part.autolabel
+Specifies the labeling format for Part titles
+
+
+
+
+<xsl:param name="part.autolabel">I</xsl:param>
+
+
+
+Description
+
+If non-zero, then parts will be numbered using the parameter
+value as the number format if the value matches one of the following:
+
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+
+Any nonzero value other than the above will generate
+the default number format (upperroman).
+
+
+
+
+
+
+
+
+reference.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+reference.autolabel
+Specifies the labeling format for Reference titles
+
+
+
+ <xsl:param name="reference.autolabel">I</xsl:param>
+
+
+Description
+If non-zero, references will be numbered using the parameter
+ value as the number format if the value matches one of the
+ following:
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+Any non-zero value other than the above will generate
+the default number format (upperroman).
+
+
+
+
+
+
+preface.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+preface.autolabel
+Specifices the labeling format for Preface titles
+
+
+
+<xsl:param name="preface.autolabel" select="0"></xsl:param>
+
+
+Description
+
+If non-zero then prefaces will be numbered using the parameter
+value as the number format if the value matches one of the following:
+
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+
+Any nonzero value other than the above will generate
+the default number format (arabic).
+
+
+
+
+
+
+
+
+section.autolabel
+boolean
+
+
+section.autolabel
+Are sections enumerated?
+
+
+
+<xsl:param name="section.autolabel" select="0"></xsl:param>
+
+
+Description
+
+If true (non-zero), unlabeled sections will be enumerated.
+
+
+
+
+
+
+
+section.autolabel.max.depth
+integer
+
+
+section.autolabel.max.depth
+The deepest level of sections that are numbered.
+
+
+
+
+<xsl:param name="section.autolabel.max.depth">8</xsl:param>
+
+
+
+Description
+
+When section numbering is turned on by the
+section.autolabel parameter, then this
+parameter controls the depth of section nesting that is
+numbered. Sections nested to a level deeper than this value will not
+be numbered.
+
+
+
+
+
+
+
+section.label.includes.component.label
+boolean
+
+
+section.label.includes.component.label
+Do section labels include the component label?
+
+
+
+<xsl:param name="section.label.includes.component.label" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, section labels are prefixed with the label of the
+component that contains them.
+
+
+
+
+
+
+
+label.from.part
+boolean
+
+
+label.from.part
+Renumber components in each part?
+
+
+
+
+<xsl:param name="label.from.part" select="0"></xsl:param>
+
+
+
+Description
+
+If label.from.part is non-zero, then
+ numbering of components — preface,
+ chapter, appendix, and
+ reference (when reference occurs at the
+ component level) — is re-started within each
+ part.
+If label.from.part is zero (the
+ default), numbering of components is not
+ re-started within each part; instead, components are
+ numbered sequentially throughout each book,
+ regardless of whether or not they occur within part
+ instances.
+
+
+
+
+
+
+component.label.includes.part.label
+boolean
+
+
+component.label.includes.part.label
+Do component labels include the part label?
+
+
+
+<xsl:param name="component.label.includes.part.label" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, number labels for chapter,
+appendix, and other component elements are prefixed with
+the label of the part element that contains them. So you might see
+Chapter II.3 instead of Chapter 3. Also, the labels for formal
+elements such as table and figure will include
+the part label. If there is no part element container, then no prefix
+is generated.
+
+
+This feature is most useful when the
+label.from.part parameter is turned on.
+In that case, there would be more than one chapter
+1, and the extra part label prefix will identify
+each chapter unambiguously.
+
+
+
+
+
+
+XSLT Processing
+
+
+rootid
+string
+
+
+rootid
+Specify the root element to format
+
+
+
+
+<xsl:param name="rootid"></xsl:param>
+
+
+Description
+
+If rootid is not empty, it must be the
+value of an ID that occurs in the document being formatted. The entire
+document will be loaded and parsed, but formatting will begin at the
+element identified, rather than at the root. For example, this allows
+you to process only chapter 4 of a book.
+Because the entire document is available to the processor, automatic
+numbering, cross references, and other dependencies are correctly
+resolved.
+
+
+
+
+
+Meta/*Info
+
+
+make.single.year.ranges
+boolean
+
+
+make.single.year.ranges
+Print single-year ranges (e.g., 1998-1999)
+
+
+
+
+<xsl:param name="make.single.year.ranges" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, year ranges that span a single year will be printed
+in range notation (1998-1999) instead of discrete notation
+(1998, 1999).
+
+
+
+
+
+
+make.year.ranges
+boolean
+
+
+make.year.ranges
+Collate copyright years into ranges?
+
+
+
+<xsl:param name="make.year.ranges" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, multiple copyright year elements will be
+collated into ranges.
+This works only if each year number is put into a separate
+year element. The copyright element permits multiple
+year elements. The stylesheet will not successfully parse
+a complex year element such as <year>2001,2002,2003</year> into
+a range.
+
+
+
+
+
+
+author.othername.in.middle
+boolean
+
+
+author.othername.in.middle
+Is othername in author a
+middle name?
+
+
+
+
+<xsl:param name="author.othername.in.middle" select="1"></xsl:param>
+
+
+Description
+
+If non-zero, the othername of an author
+appears between the firstname and
+surname. Otherwise, othername
+is suppressed.
+
+
+
+
+
+
+Reference Pages
+
+
+funcsynopsis.decoration
+boolean
+
+
+funcsynopsis.decoration
+Decorate elements of a funcsynopsis?
+
+
+
+
+<xsl:param name="funcsynopsis.decoration" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, elements of the funcsynopsis will be
+decorated (e.g. rendered as bold or italic text). The decoration is controlled by
+templates that can be redefined in a customization layer.
+
+
+
+
+
+
+
+funcsynopsis.style
+list
+ansi
+kr
+
+
+funcsynopsis.style
+What style of funcsynopsis should be generated?
+
+
+
+<xsl:param name="funcsynopsis.style">kr</xsl:param>
+
+
+Description
+
+If funcsynopsis.style is ansi,
+ANSI-style function synopses are generated for a
+funcsynopsis, otherwise K&R-style
+function synopses are generated.
+
+
+
+
+
+
+
+function.parens
+boolean
+
+
+function.parens
+Generate parens after a function?
+
+
+
+
+<xsl:param name="function.parens" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the formatting of a function element
+will include generated parentheses.
+
+
+
+
+
+
+
+refentry.generate.name
+boolean
+
+
+refentry.generate.name
+Output NAME header before 'RefName'(s)?
+
+
+
+
+<xsl:param name="refentry.generate.name" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, a "NAME" section title is output before the list
+of 'RefName's. This parameter and
+refentry.generate.title are mutually
+exclusive. This means that if you change this parameter to zero, you
+should set refentry.generate.title to non-zero unless
+you want get quite strange output.
+
+
+
+
+
+
+
+refentry.generate.title
+boolean
+
+
+refentry.generate.title
+Output title before 'RefName'(s)?
+
+
+
+
+<xsl:param name="refentry.generate.title" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the reference page title or first name is
+output before the list of 'RefName's. This parameter and
+refentry.generate.name are mutually exclusive.
+This means that if you change this parameter to non-zero, you
+should set refentry.generate.name to zero unless
+you want get quite strange output.
+
+
+
+
+
+
+
+refentry.pagebreak
+boolean
+
+
+refentry.pagebreak
+Start each refentry on a new page
+
+
+
+<xsl:param name="refentry.pagebreak" select="1"></xsl:param>
+
+
+Description
+
+If non-zero (the default), each refentry
+element will start on a new page. If zero, a page
+break will not be generated between refentry elements.
+The exception is when the refentry elements are children of
+a part element, in which case the page breaks are always
+retained. That is because a part element does not generate
+a page-sequence for its children, so each refentry must
+start its own page-sequence.
+
+
+
+
+
+
+
+refentry.title.properties
+attribute set
+
+
+refentry.title.properties
+Title properties for a refentry title
+
+
+
+
+<xsl:attribute-set name="refentry.title.properties">
+ <xsl:attribute name="font-family">
+ <xsl:value-of select="$title.font.family"></xsl:value-of>
+ </xsl:attribute>
+ <xsl:attribute name="font-size">18pt</xsl:attribute>
+ <xsl:attribute name="font-weight">bold</xsl:attribute>
+ <xsl:attribute name="space-after">1em</xsl:attribute>
+ <xsl:attribute name="hyphenate">false</xsl:attribute>
+ <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
+ <xsl:attribute name="space-before.minimum">0.8em</xsl:attribute>
+ <xsl:attribute name="space-before.optimum">1.0em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">1.2em</xsl:attribute>
+ <xsl:attribute name="space-after.optimum">0.5em</xsl:attribute>
+ <xsl:attribute name="space-after.minimum">0.4em</xsl:attribute>
+ <xsl:attribute name="space-after.maximum">0.6em</xsl:attribute>
+ <xsl:attribute name="start-indent"><xsl:value-of select="$title.margin.left"></xsl:value-of></xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Formatting properties applied to the title generated for the
+refnamediv part of output for
+refentry when the value of the
+refentry.generate.title parameter is
+non-zero. The font size is supplied by the appropriate section.levelX.title.properties
+attribute-set, computed from the location of the
+refentry in the section hierarchy.
+
+
+ This parameter has no effect on the the title generated for
+ the refnamediv part of output for
+ refentry when the value of the
+ refentry.generate.name parameter is
+ non-zero. By default, that title is formatted with the same
+ properties as the titles for all other first-level children of
+ refentry.
+
+
+
+
+
+
+
+refentry.xref.manvolnum
+boolean
+
+
+refentry.xref.manvolnum
+Output manvolnum as part of
+refentry cross-reference?
+
+
+
+
+<xsl:param name="refentry.xref.manvolnum" select="1"></xsl:param>
+
+
+
+Description
+
+if non-zero, the manvolnum is used when cross-referencing
+refentrys, either with xref
+or citerefentry.
+
+
+
+
+
+
+
+refclass.suppress
+boolean
+
+
+refclass.suppress
+Suppress display of refclass contents?
+
+
+
+
+<xsl:param name="refclass.suppress" select="0"></xsl:param>
+
+
+Description
+
+If the value of refclass.suppress is
+non-zero, then display of refclass contents is
+suppressed in output.
+
+
+
+
+
+Tables
+
+
+default.table.width
+length
+
+
+default.table.width
+The default width of tables
+
+
+
+<xsl:param name="default.table.width"></xsl:param>
+
+
+Description
+If non-zero, this value will be used for the
+width attribute on tables that do not specify an
+alternate width (with the dbhtml table-width or
+dbfo table-width processing instruction).
+
+
+
+
+
+nominal.table.width
+length
+
+
+nominal.table.width
+The (absolute) nominal width of tables
+
+
+
+
+<xsl:param name="nominal.table.width">6in</xsl:param>
+
+
+
+Description
+
+In order to convert CALS column widths into HTML column widths, it
+is sometimes necessary to have an absolute table width to use for conversion
+of mixed absolute and relative widths. This value must be an absolute
+length (not a percentage).
+
+
+
+
+
+
+default.table.frame
+string
+
+
+default.table.frame
+The default framing of tables
+
+
+
+
+<xsl:param name="default.table.frame">all</xsl:param>
+
+
+
+Description
+
+This value will be used when there is no frame attribute on the
+table.
+
+
+
+
+
+
+table.cell.padding
+attribute set
+
+
+table.cell.padding
+Specifies the padding of table cells
+
+
+
+
+<xsl:attribute-set name="table.cell.padding">
+ <xsl:attribute name="padding-left">2pt</xsl:attribute>
+ <xsl:attribute name="padding-right">2pt</xsl:attribute>
+ <xsl:attribute name="padding-top">2pt</xsl:attribute>
+ <xsl:attribute name="padding-bottom">2pt</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Specifies the padding of table cells.
+
+
+
+
+
+
+table.frame.border.thickness
+length
+
+
+table.frame.border.thickness
+Specifies the thickness of the frame border
+
+
+
+
+<xsl:param name="table.frame.border.thickness">0.5pt</xsl:param>
+
+
+
+Description
+
+Specifies the thickness of the border on the table's frame.
+
+
+
+
+
+
+table.frame.border.style
+list
+none
+solid
+dotted
+dashed
+double
+groove
+ridge
+inset
+outset
+solid
+
+
+table.frame.border.style
+Specifies the border style of table frames
+
+
+
+
+<xsl:param name="table.frame.border.style">solid</xsl:param>
+
+
+
+Description
+
+Specifies the border style of table frames.
+
+
+
+
+
+
+table.frame.border.color
+color
+
+
+table.frame.border.color
+Specifies the border color of table frames
+
+
+
+
+
+<xsl:param name="table.frame.border.color">black</xsl:param>
+
+
+
+Description
+
+Specifies the border color of table frames.
+
+
+
+
+
+
+table.cell.border.thickness
+length
+
+
+table.cell.border.thickness
+Specifies the thickness of table cell borders
+
+
+
+
+<xsl:param name="table.cell.border.thickness">0.5pt</xsl:param>
+
+
+
+Description
+
+If non-zero, specifies the thickness of borders on table
+cells. The units are points. See
+CSS
+
+
+ To control properties of cell borders in HTML output, you must also turn on the
+ table.borders.with.css parameter.
+
+
+
+
+
+
+
+table.cell.border.style
+list
+none
+solid
+dotted
+dashed
+double
+groove
+ridge
+inset
+outset
+solid
+
+
+table.cell.border.style
+Specifies the border style of table cells
+
+
+
+
+<xsl:param name="table.cell.border.style">solid</xsl:param>
+
+
+
+Description
+
+Specifies the border style of table cells.
+
+
+ To control properties of cell borders in HTML output, you must also turn on the
+ table.borders.with.css parameter.
+
+
+
+
+
+
+
+table.cell.border.color
+color
+
+
+table.cell.border.color
+Specifies the border color of table cells
+
+
+
+
+
+<xsl:param name="table.cell.border.color">black</xsl:param>
+
+
+
+Description
+
+Set the color of table cell borders. If non-zero, the value is used
+for the border coloration. See CSS. A
+color is either a keyword or a numerical RGB specification.
+Keywords are aqua, black, blue, fuchsia, gray, green, lime, maroon,
+navy, olive, orange, purple, red, silver, teal, white, and
+yellow.
+
+
+ To control properties of cell borders in HTML output, you must also turn on the
+ table.borders.with.css parameter.
+
+
+
+
+
+
+
+table.table.properties
+attribute set
+
+
+table.table.properties
+Properties associated with a table
+
+
+
+
+<xsl:attribute-set name="table.table.properties">
+ <xsl:attribute name="border-before-width.conditionality">retain</xsl:attribute>
+ <xsl:attribute name="border-collapse">collapse</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The styling for tables. This parameter should really
+have been called table.properties, but that parameter
+name was inadvertently established for the block-level properties
+of the table as a whole.
+
+
+See also table.properties.
+
+
+
+
+
+Linking
+
+
+current.docid
+string
+
+
+current.docid
+targetdoc identifier for the document being
+processed
+
+
+<xsl:param name="current.docid"></xsl:param>
+
+
+Description
+
+When olinks between documents are resolved for HTML output, the stylesheet can compute the relative path between the current document and the target document. The stylesheet needs to know the targetdoc identifiers for both documents, as they appear in the target.database.document database file. This parameter passes to the stylesheet
+the targetdoc identifier of the current document, since that
+identifier does not appear in the document itself.
+This parameter can also be used for print output. If an olink's targetdoc id differs from the current.docid, then the stylesheet can append the target document's title to the generated olink text. That identifies to the reader that the link is to a different document, not the current document. See also olink.doctitle to enable that feature.
+
+
+
+
+
+collect.xref.targets
+list
+no
+yes
+only
+
+
+collect.xref.targets
+Controls whether cross reference data is
+collected
+
+
+<xsl:param name="collect.xref.targets">no</xsl:param>
+
+
+Description
+
+
+In order to resolve olinks efficiently, the stylesheets can
+generate an external data file containing information about
+all potential cross reference endpoints in a document.
+This parameter determines whether the collection process is run when the document is processed by the stylesheet. The default value is no, which means the data file is not generated during processing. The other choices are yes, which means the data file is created and the document is processed for output, and only, which means the data file is created but the document is not processed for output.
+See also targets.filename.
+
+
+
+
+
+
+insert.olink.page.number
+list
+no
+yes
+maybe
+
+
+insert.olink.page.number
+Turns page numbers in olinks on and off
+
+
+
+
+<xsl:param name="insert.olink.page.number">no</xsl:param>
+
+
+
+Description
+
+The value of this parameter determines if
+cross references made between documents with
+olink will
+include page number citations.
+In most cases this is only applicable to references in printed output.
+
+The parameter has three possible values.
+
+
+
+no
+No page number references will be generated for olinks.
+
+
+
+yes
+Page number references will be generated
+for all olink references.
+The style of page reference may be changed
+if an xrefstyle
+attribute is used.
+
+
+
+maybe
+Page number references will not be generated
+for an olink element unless
+it has an
+xrefstyle
+attribute whose value specifies a page reference.
+
+
+
+Olinks that point to targets within the same document
+are treated as xrefs, and controlled by
+the insert.xref.page.number parameter.
+
+
+Page number references for olinks to
+external documents can only be inserted if the
+information exists in the olink database.
+This means each olink target element
+(div or obj)
+must have a page attribute
+whose value is its page number in the target document.
+The XSL stylesheets are not able to extract that information
+during processing because pages have not yet been created in
+XSLT transformation. Only the XSL-FO processor knows what
+page each element is placed on.
+Therefore some postprocessing must take place to populate
+page numbers in the olink database.
+
+
+
+
+
+
+
+
+
+insert.olink.pdf.frag
+boolean
+
+
+insert.olink.pdf.frag
+Add fragment identifiers for links into PDF files
+
+
+
+
+<xsl:param name="insert.olink.pdf.frag" select="0"></xsl:param>
+
+
+
+Description
+
+The value of this parameter determines whether
+the cross reference URIs to PDF documents made with
+olink will
+include fragment identifiers.
+
+
+When forming a URI to link to a PDF document,
+a fragment identifier (typically a '#' followed by an
+id value) appended to the PDF filename can be used by
+the PDF viewer to open
+the PDF file to a location within the document instead of
+the first page.
+However, not all PDF files have id
+values embedded in them, and not all PDF viewers can
+handle fragment identifiers.
+
+
+If insert.olink.pdf.frag is set
+to a non-zero value, then any olink targeting a
+PDF file will have the fragment identifier appended to the URI.
+The URI is formed by concatenating the value of the
+olink.base.uri parameter, the
+value of the baseuri
+attribute from the document
+element in the olink database with the matching
+targetdoc value,
+and the value of the href
+attribute for the targeted element in the olink database.
+The href attribute
+contains the fragment identifier.
+
+
+If insert.olink.pdf.frag is set
+to zero (the default value), then
+the href attribute
+from the olink database
+is not appended to PDF olinks, so the fragment identifier is left off.
+A PDF olink is any olink for which the
+baseuri attribute
+from the matching document
+element in the olink database ends with '.pdf'.
+Any other olinks will still have the fragment identifier added.
+
+
+
+
+
+
+olink.base.uri
+uri
+
+
+olink.base.uri
+Base URI used in olink hrefs
+
+
+<xsl:param name="olink.base.uri"></xsl:param>
+
+
+Description
+
+When cross reference data is collected for resolving olinks, it
+may be necessary to prepend a base URI to each target's href. This
+parameter lets you set that base URI when cross reference data is
+collected. This feature is needed when you want to link to a document
+that is processed without chunking. The output filename for such a
+document is not known to the XSL stylesheet; the only target
+information consists of fragment identifiers such as
+#idref. To enable the resolution of olinks between
+documents, you should pass the name of the HTML output file as the
+value of this parameter. Then the hrefs recorded in the cross
+reference data collection look like
+outfile.html#idref, which can be reached as links
+from other documents.
+
+
+
+
+
+olink.debug
+boolean
+
+
+olink.debug
+Turn on debugging messages for olinks
+
+
+
+
+<xsl:param name="olink.debug" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, then each olink will generate several
+messages about how it is being resolved during processing.
+This is useful when an olink does not resolve properly
+and the standard error messages are not sufficient to
+find the problem.
+
+
+You may need to read through the olink XSL templates
+to understand the context for some of the debug messages.
+
+
+
+
+
+
+
+olink.doctitle
+list
+no
+yes
+maybe
+
+
+olink.doctitle
+show the document title for external olinks?
+
+
+
+<xsl:param name="olink.doctitle">no</xsl:param>
+
+
+Description
+
+When olinks between documents are resolved, the generated text
+may not make it clear that the reference is to another document.
+It is possible for the stylesheets to append the other document's
+title to external olinks. For this to happen, two parameters must
+be set.
+
+
+This olink.doctitle parameter
+should be set to either yes or maybe
+to enable this feature.
+
+
+
+And you should also set the current.docid
+parameter to the document id for the document currently
+being processed for output.
+
+
+
+
+
+Then if an olink's targetdoc id differs from
+the current.docid value, the stylesheet knows
+that it is a reference to another document and can
+append the target document's
+title to the generated olink text.
+
+The text for the target document's title is copied from the
+olink database from the ttl element
+of the top-level div for that document.
+If that ttl element is missing or empty,
+no title is output.
+
+
+The supported values for olink.doctitle are:
+
+
+
+yes
+
+
+Always insert the title to the target document if it is not
+the current document.
+
+
+
+
+no
+
+
+Never insert the title to the target document, even if requested
+in an xrefstyle attribute.
+
+
+
+
+maybe
+
+
+Only insert the title to the target document, if requested
+in an xrefstyle attribute.
+
+
+
+
+An xrefstyle attribute
+may override the global setting for individual olinks.
+The following values are supported in an
+xrefstyle
+attribute using the select: syntax:
+
+
+
+
+docname
+
+
+Insert the target document name for this olink using the
+docname gentext template, but only
+if the value of olink.doctitle
+is not no.
+
+
+
+
+docnamelong
+
+
+Insert the target document name for this olink using the
+docnamelong gentext template, but only
+if the value of olink.doctitle
+is not no.
+
+
+
+
+nodocname
+
+
+Omit the target document name even if
+the value of olink.doctitle
+is yes.
+
+
+
+
+Another way of inserting the target document name
+for a single olink is to employ an
+xrefstyle
+attribute using the template: syntax.
+The %o placeholder (the letter o, not zero)
+in such a template
+will be filled in with the target document's title when it is processed.
+This will occur regardless of
+the value of olink.doctitle.
+
+Note that prior to version 1.66 of the XSL stylesheets,
+the allowed values for this parameter were 0 and 1. Those
+values are still supported and mapped to 'no' and 'yes', respectively.
+
+
+
+
+
+
+olink.lang.fallback.sequence
+string
+
+
+olink.lang.fallback.sequence
+look up translated documents if olink not found?
+
+
+
+<xsl:param name="olink.lang.fallback.sequence"></xsl:param>
+
+
+Description
+
+
+This parameter defines a list of lang values
+to search among to resolve olinks.
+
+
+Normally an olink tries to resolve to a document in the same
+language as the olink itself. The language of an olink
+is determined by its nearest ancestor element with a
+lang attribute, otherwise the
+value of the l10n.gentext.default.lang
+parameter.
+
+
+An olink database can contain target data for the same
+document in multiple languages. Each set of data has the
+same value for the targetdoc attribute in
+the document element in the database, but with a
+different lang attribute value.
+
+
+When an olink is being resolved, the target is first
+sought in the document with the same language as the olink.
+If no match is found there, then this parameter is consulted
+for additional languages to try.
+
+The olink.lang.fallback.sequence
+must be a whitespace separated list of lang values to
+try. The first one with a match in the olink database is used.
+The default value is empty.
+
+For example, a document might be written in German
+and contain an olink with
+targetdoc="adminguide".
+When the document is processed, the processor
+first looks for a target dataset in the
+olink database starting with:
+
+<document targetdoc="adminguide" lang="de">.
+
+
+If there is no such element, then the
+olink.lang.fallback.sequence
+parameter is consulted.
+If its value is, for example, fr en, then the processor next
+looks for targetdoc="adminguide" lang="fr", and
+then for targetdoc="adminguide" lang="en".
+If there is still no match, it looks for
+targetdoc="adminguide" with no
+lang attribute.
+
+
+This parameter is useful when a set of documents is only
+partially translated, or is in the process of being translated.
+If a target of an olink has not yet been translated, then this
+parameter permits the processor to look for the document in
+other languages. This assumes the reader would rather have
+a link to a document in a different language than to have
+a broken link.
+
+
+
+
+
+
+
+olink.properties
+attribute set
+
+
+olink.properties
+Properties associated with the cross-reference
+text of an olink.
+
+
+
+
+<xsl:attribute-set name="olink.properties">
+ <xsl:attribute name="show-destination">replace</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+This attribute set is applied to the
+fo:basic-link element of an olink. It is not applied to the
+optional page number or optional title of the external
+document.
+
+
+
+
+
+
+prefer.internal.olink
+boolean
+
+
+prefer.internal.olink
+Prefer a local olink reference to an external reference
+
+
+
+
+<xsl:param name="prefer.internal.olink" select="0"></xsl:param>
+
+
+
+Description
+
+If you are re-using XML content modules in multiple documents,
+you may want to redirect some of your olinks. This parameter
+permits you to redirect an olink to the current document.
+
+
+For example: you are writing documentation for a product,
+which includes 3 manuals: a little installation
+booklet (booklet.xml), a user
+guide (user.xml), and a reference manual (reference.xml).
+All 3 documents begin with the same introduction section (intro.xml) that
+contains a reference to the customization section (custom.xml) which is
+included in both user.xml and reference.xml documents.
+
+
+How do you write the link to custom.xml in intro.xml
+so that it is interpreted correctly in all 3 documents?
+
+If you use xref, it will fail in user.xml.
+
+If you use olink (pointing to reference.xml),
+the reference in user.xml
+will point to the customization section of the reference manual, while it is
+actually available in user.xml.
+
+
+
+If you set the prefer.internal.olink
+parameter to a non-zero value, then the processor will
+first look in the olink database
+for the olink's targetptr attribute value
+in document matching the current.docid
+parameter value. If it isn't found there, then
+it tries the document in the database
+with the targetdoc
+value that matches the olink's targetdoc
+attribute.
+
+
+This feature permits an olink reference to resolve to
+the current document if there is an element
+with an id matching the olink's targetptr
+value. The current document's olink data must be
+included in the target database for this to work.
+
+
+There is a potential for incorrect links if
+the same id attribute value is used for different
+content in different documents.
+Some of your olinks may be redirected to the current document
+when they shouldn't be. It is not possible to control
+individual olink instances.
+
+
+
+
+
+
+
+target.database.document
+uri
+
+
+target.database.document
+Name of master database file for resolving
+olinks
+
+
+
+ <xsl:param name="target.database.document">olinkdb.xml</xsl:param>
+
+
+Description
+
+
+To resolve olinks between documents, the stylesheets use a master
+database document that identifies the target datafiles for all the
+documents within the scope of the olinks. This parameter value is the
+URI of the master document to be read during processing to resolve
+olinks. The default value is olinkdb.xml.
+
+The data structure of the file is defined in the
+targetdatabase.dtd DTD. The database file
+provides the high level elements to record the identifiers, locations,
+and relationships of documents. The cross reference data for
+individual documents is generally pulled into the database using
+system entity references or XIncludes. See also
+targets.filename.
+
+
+
+
+targets.filename
+string
+
+
+targets.filename
+Name of cross reference targets data file
+
+
+<xsl:param name="targets.filename">target.db</xsl:param>
+
+
+Description
+
+
+In order to resolve olinks efficiently, the stylesheets can
+generate an external data file containing information about
+all potential cross reference endpoints in a document.
+This parameter lets you change the name of the generated
+file from the default name target.db.
+The name must agree with that used in the target database
+used to resolve olinks during processing.
+See also target.database.document.
+
+
+
+
+
+
+use.local.olink.style
+boolean
+
+
+use.local.olink.style
+Process olinks using xref style of current
+document
+
+
+<xsl:param name="use.local.olink.style" select="0"></xsl:param>
+
+Description
+
+When cross reference data is collected for use by olinks, the data for each potential target includes one field containing a completely assembled cross reference string, as if it were an xref generated in that document. Other fields record the separate title, number, and element name of each target. When an olink is formed to a target from another document, the olink resolves to that preassembled string by default. If the use.local.olink.style parameter is set to non-zero, then instead the cross
+reference string is formed again from the target title, number, and
+element name, using the stylesheet processing the targeting document.
+Then olinks will match the xref style in the targeting document
+rather than in the target document. If both documents are processed
+with the same stylesheet, then the results will be the same.
+
+
+
+
+Cross References
+
+
+insert.xref.page.number
+list
+no
+yes
+maybe
+
+
+insert.xref.page.number
+Turns page numbers in xrefs on and off
+
+
+
+
+<xsl:param name="insert.xref.page.number">no</xsl:param>
+
+
+
+Description
+
+The value of this parameter determines if
+cross references (xrefs) in
+printed output will
+include page number citations.
+It has three possible values.
+
+
+
+no
+No page number references will be generated.
+
+
+
+yes
+Page number references will be generated
+for all xref elements.
+The style of page reference may be changed
+if an xrefstyle
+attribute is used.
+
+
+
+maybe
+Page number references will not be generated
+for an xref element unless
+it has an
+xrefstyle
+attribute whose value specifies a page reference.
+
+
+
+
+
+
+
+
+
+xref.properties
+attribute set
+
+
+xref.properties
+Properties associated with cross-reference text
+
+
+
+
+<xsl:attribute-set name="xref.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+This attribute set is used to set properties
+on cross reference text.
+
+
+
+
+
+
+xref.label-title.separator
+string
+
+
+xref.label-title.separator
+Punctuation or space separating label from title in xref
+
+
+
+<xsl:param name="xref.label-title.separator">: </xsl:param>
+
+
+Description
+
+
+This parameter allows you to control the punctuation of certain
+types of generated cross reference text.
+When cross reference text is generated for an
+xref or
+olink element
+using an xrefstyle attribute
+that makes use of the select: feature,
+and the selected components include both label and title,
+then the value of this parameter is inserted between
+label and title in the output.
+
+
+
+
+
+
+
+xref.label-page.separator
+string
+
+
+xref.label-page.separator
+Punctuation or space separating label from page number in xref
+
+
+
+<xsl:param name="xref.label-page.separator"><xsl:text> </xsl:text></xsl:param>
+
+
+Description
+
+
+This parameter allows you to control the punctuation of certain
+types of generated cross reference text.
+When cross reference text is generated for an
+xref or
+olink element
+using an xrefstyle attribute
+that makes use of the select: feature,
+and the selected components include both label and page
+but no title,
+then the value of this parameter is inserted between
+label and page number in the output.
+If a title is included, then other separators are used.
+
+
+
+
+
+
+
+xref.title-page.separator
+string
+
+
+xref.title-page.separator
+Punctuation or space separating title from page number in xref
+
+
+
+<xsl:param name="xref.title-page.separator"><xsl:text> </xsl:text></xsl:param>
+
+
+Description
+
+
+This parameter allows you to control the punctuation of certain
+types of generated cross reference text.
+When cross reference text is generated for an
+xref or
+olink element
+using an xrefstyle attribute
+that makes use of the select: feature,
+and the selected components include both title and page number,
+then the value of this parameter is inserted between
+title and page number in the output.
+
+
+
+
+
+
+
+insert.link.page.number
+list
+no
+yes
+maybe
+
+
+insert.link.page.number
+Turns page numbers in link elements on and off
+
+
+
+
+<xsl:param name="insert.link.page.number">no</xsl:param>
+
+
+
+Description
+
+The value of this parameter determines if
+cross references using the link element in
+printed output will
+include standard page number citations.
+It has three possible values.
+
+
+
+no
+No page number references will be generated.
+
+
+
+yes
+Page number references will be generated
+for all link elements.
+The style of page reference may be changed
+if an xrefstyle
+attribute is used.
+
+
+
+maybe
+Page number references will not be generated
+for a link element unless
+it has an
+xrefstyle
+attribute whose value specifies a page reference.
+
+
+
+
+Although the xrefstyle attribute
+can be used to turn the page reference on or off, it cannot be
+used to control the formatting of the page number as it
+can in xref.
+In link it will always format with
+the style established by the
+gentext template with name="page.citation"
+in the l:context name="xref".
+
+
+
+
+
+Lists
+
+
+compact.list.item.spacing
+attribute set
+
+
+compact.list.item.spacing
+What space do you want between list items (when spacing="compact")?
+
+
+
+<xsl:attribute-set name="compact.list.item.spacing">
+ <xsl:attribute name="space-before.optimum">0em</xsl:attribute>
+ <xsl:attribute name="space-before.minimum">0em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">0.2em</xsl:attribute>
+</xsl:attribute-set>
+
+Description
+Specify what spacing you want between each list item when
+spacing is
+compact.
+
+
+
+
+
+itemizedlist.properties
+attribute set
+
+
+itemizedlist.properties
+Properties that apply to each list-block generated by itemizedlist.
+
+
+
+<xsl:attribute-set name="itemizedlist.properties" use-attribute-sets="list.block.properties">
+</xsl:attribute-set>
+
+Description
+Properties that apply to each fo:list-block generated by itemizedlist.
+
+
+
+
+
+itemizedlist.label.properties
+attribute set
+
+
+itemizedlist.label.properties
+Properties that apply to each label inside itemized list.
+
+
+
+<xsl:attribute-set name="itemizedlist.label.properties">
+</xsl:attribute-set>
+
+Description
+Properties that apply to each label inside itemized list. E.g.:
+<xsl:attribute-set name="itemizedlist.label.properties">
+ <xsl:attribute name="text-align">right</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+
+
+itemizedlist.label.width
+length
+
+
+ itemizedlist.label.width
+The default width of the label (bullet) in an itemized list.
+
+
+
+
+ <xsl:param name="itemizedlist.label.width">1.0em</xsl:param>
+
+
+
+Description
+Specifies the default width of the label (usually a bullet or other
+symbol) in an itemized list. You can override the default value on any
+particular list with the “dbfo” processing instruction using the
+“label-width” pseudoattribute.
+
+
+
+
+
+list.block.properties
+attribute set
+
+
+list.block.properties
+Properties that apply to each list-block generated by list.
+
+
+
+<xsl:attribute-set name="list.block.properties">
+ <xsl:attribute name="provisional-label-separation">0.2em</xsl:attribute>
+ <xsl:attribute name="provisional-distance-between-starts">1.5em</xsl:attribute>
+</xsl:attribute-set>
+
+Description
+Properties that apply to each fo:list-block generated by itemizedlist/orderedlist.
+
+
+
+
+
+list.block.spacing
+attribute set
+
+
+list.block.spacing
+What spacing do you want before and after lists?
+
+
+
+<xsl:attribute-set name="list.block.spacing">
+ <xsl:attribute name="space-before.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-before.minimum">0.8em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">1.2em</xsl:attribute>
+ <xsl:attribute name="space-after.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-after.minimum">0.8em</xsl:attribute>
+ <xsl:attribute name="space-after.maximum">1.2em</xsl:attribute>
+</xsl:attribute-set>
+
+Description
+Specify the spacing required before and after a list. It is necessary to specify the space after a list block because lists can come inside of paras.
+
+
+
+
+
+list.item.spacing
+attribute set
+
+
+list.item.spacing
+What space do you want between list items?
+
+
+
+<xsl:attribute-set name="list.item.spacing">
+ <xsl:attribute name="space-before.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-before.minimum">0.8em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">1.2em</xsl:attribute>
+</xsl:attribute-set>
+
+Description
+Specify what spacing you want between each list item.
+
+
+
+
+
+orderedlist.properties
+attribute set
+
+
+orderedlist.properties
+Properties that apply to each list-block generated by orderedlist.
+
+
+
+<xsl:attribute-set name="orderedlist.properties" use-attribute-sets="list.block.properties">
+ <xsl:attribute name="provisional-distance-between-starts">2em</xsl:attribute>
+</xsl:attribute-set>
+
+Description
+Properties that apply to each fo:list-block generated by orderedlist.
+
+
+
+
+
+orderedlist.label.properties
+attribute set
+
+
+orderedlist.label.properties
+Properties that apply to each label inside ordered list.
+
+
+
+<xsl:attribute-set name="orderedlist.label.properties">
+</xsl:attribute-set>
+
+Description
+Properties that apply to each label inside ordered list. E.g.:
+<xsl:attribute-set name="orderedlist.label.properties">
+ <xsl:attribute name="text-align">right</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+
+
+orderedlist.label.width
+length
+
+
+orderedlist.label.width
+The default width of the label (number) in an ordered list.
+
+
+
+
+<xsl:param name="orderedlist.label.width">1.2em</xsl:param>
+
+
+
+Description
+Specifies the default width of the label (usually a number or
+sequence of numbers) in an ordered list. You can override the default
+value on any particular list with the “dbfo” processing instruction
+using the “label-width” pseudoattribute.
+
+
+
+
+
+variablelist.max.termlength
+number
+
+
+variablelist.max.termlength
+Specifies the longest term in variablelists
+
+
+
+
+<xsl:param name="variablelist.max.termlength">24</xsl:param>
+
+
+
+Description
+
+In variablelists, the listitem
+is indented to leave room for the
+term elements. That indent may be computed
+if it is not specified with a termlength
+attribute on the variablelist element.
+
+
+The computation counts characters in the
+term elements in the list
+to find the longest term. However, some terms are very long
+and would produce extreme indents. This parameter lets you
+set a maximum character count. Any terms longer than the maximum
+would line wrap. The default value is 24.
+
+
+The character counts are converted to physical widths
+by multiplying by 0.50em. There will be some variability
+in how many actual characters fit in the space
+since some characters are wider than others.
+
+
+
+
+
+
+
+variablelist.term.separator
+string
+
+
+variablelist.term.separator
+Text to separate terms within a multi-term
+varlistentry
+
+
+
+
+<xsl:param name="variablelist.term.separator">, </xsl:param>
+
+
+Description
+
+When a varlistentry contains multiple term
+elements, the string specified in the value of the
+variablelist.term.separator parameter is placed
+after each term except the last.
+
+
+ To generate a line break between multiple terms in
+ a varlistentry, set a non-zero value for the
+ variablelist.term.break.after parameter. If
+ you do so, you may also want to set the value of the
+ variablelist.term.separator parameter to an
+ empty string (to suppress rendering of the default comma and space
+ after each term).
+
+
+
+
+
+
+
+variablelist.term.break.after
+boolean
+
+
+variablelist.term.break.after
+Generate line break after each term within a
+multi-term varlistentry?
+
+
+
+
+<xsl:param name="variablelist.term.break.after">0</xsl:param>
+
+
+Description
+
+Set a non-zero value for the
+variablelist.term.break.after parameter to
+generate a line break between terms in a
+multi-term varlistentry.
+
+
+If you set a non-zero value for
+variablelist.term.break.after, you may also
+want to set the value of the
+variablelist.term.separator parameter to an
+empty string (to suppress rendering of the default comma and space
+after each term).
+
+
+
+
+
+
+QAndASet
+
+
+qandadiv.autolabel
+boolean
+
+
+qandadiv.autolabel
+Are divisions in QAndASets enumerated?
+
+
+
+<xsl:param name="qandadiv.autolabel" select="1"></xsl:param>
+
+
+Description
+
+If non-zero, unlabeled qandadivs will be enumerated.
+
+
+
+
+
+
+
+qanda.inherit.numeration
+boolean
+
+
+qanda.inherit.numeration
+Does enumeration of QandASet components inherit the numeration of parent elements?
+
+
+
+
+<xsl:param name="qanda.inherit.numeration" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, numbered qandadiv elements and
+question and answer inherit the enumeration of
+the ancestors of the qandaset.
+
+
+
+
+
+
+
+qanda.defaultlabel
+list
+number
+qanda
+none
+
+
+qanda.defaultlabel
+Sets the default for defaultlabel on QandASet.
+
+
+
+
+<xsl:param name="qanda.defaultlabel">number</xsl:param>
+
+
+
+Description
+
+If no defaultlabel attribute is specified on
+a qandaset, this value is used. It must be one of the legal
+values for the defaultlabel attribute, one from none, number or
+qanda. The default value is 'number'.
+
+Meaning
+qanda - questions are labeled “Q:” and answers are labeled “A:”.
+number - The entries are enumerated.
+none - No distinguishing label precedes Questions or Answers.
+
+
+
+
+
+
+
+
+
+
+
+
+qanda.in.toc
+boolean
+
+
+qanda.in.toc
+Should qandaentry questions appear in
+the document table of contents?
+
+
+
+<xsl:param name="qanda.in.toc" select="0"></xsl:param>
+
+
+Description
+
+If true (non-zero), then the generated table of contents
+for a document will include qandaset titles,
+qandadiv titles,
+and question elements. The default value (zero) excludes
+them from the TOC.
+
+This parameter does not affect any tables of contents
+that may be generated inside a qandaset or qandadiv.
+
+
+
+
+
+
+
+qanda.nested.in.toc
+boolean
+
+
+qanda.nested.in.toc
+Should nested answer/qandaentry instances appear in TOC?
+
+
+
+
+<xsl:param name="qanda.nested.in.toc" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, instances of qandaentry
+that are children of answer elements are shown in
+the TOC.
+
+
+
+
+
+Bibliography
+
+
+bibliography.style
+list
+normal
+iso690
+
+
+bibliography.style
+Style used for formatting of biblioentries.
+
+
+
+
+<xsl:param name="bibliography.style">normal</xsl:param>
+
+
+
+Description
+
+Currently only normal and
+iso690 styles are supported.
+
+In order to use ISO690 style to the full extent you might need
+to use additional markup described on the
+following WiKi page.
+
+
+
+
+
+
+biblioentry.item.separator
+string
+
+
+biblioentry.item.separator
+Text to separate bibliography entries
+
+
+
+<xsl:param name="biblioentry.item.separator">. </xsl:param>
+
+
+Description
+
+Text to separate bibliography entries
+
+
+
+
+
+
+
+bibliography.collection
+string
+
+
+bibliography.collection
+Name of the bibliography collection file
+
+
+
+
+<xsl:param name="bibliography.collection">http://docbook.sourceforge.net/release/bibliography/bibliography.xml</xsl:param>
+
+
+
+
+Description
+
+Maintaining bibliography entries across a set of documents is tedious, time
+consuming, and error prone. It makes much more sense, usually, to store all of
+the bibliography entries in a single place and simply extract
+the ones you need in each document.
+
+That's the purpose of the
+bibliography.collection parameter. To setup a global
+bibliography database, follow these steps:
+
+First, create a stand-alone bibliography document that contains all of
+the documents that you wish to reference. Make sure that each bibliography
+entry (whether you use biblioentry or bibliomixed)
+has an ID.
+
+My global bibliography, ~/bibliography.xml begins
+like this:
+
+
+<!DOCTYPE bibliography
+ PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
+<bibliography><title>References</title>
+
+<bibliomixed id="xml-rec"><abbrev>XML 1.0</abbrev>Tim Bray,
+Jean Paoli, C. M. Sperberg-McQueen, and Eve Maler, editors.
+<citetitle><ulink url="http://www.w3.org/TR/REC-xml">Extensible Markup
+Language (XML) 1.0 Second Edition</ulink></citetitle>.
+World Wide Web Consortium, 2000.
+</bibliomixed>
+
+<bibliomixed id="xml-names"><abbrev>Namespaces</abbrev>Tim Bray,
+Dave Hollander,
+and Andrew Layman, editors.
+<citetitle><ulink url="http://www.w3.org/TR/REC-xml-names/">Namespaces in
+XML</ulink></citetitle>.
+World Wide Web Consortium, 1999.
+</bibliomixed>
+
+<!-- ... -->
+</bibliography>
+
+
+
+When you create a bibliography in your document, simply
+provide emptybibliomixed
+entries for each document that you wish to cite. Make sure that these
+elements have the same ID as the corresponding real
+entry in your global bibliography.
+
+For example:
+
+
+<bibliography><title>Bibliography</title>
+
+<bibliomixed id="xml-rec"/>
+<bibliomixed id="xml-names"/>
+<bibliomixed id="DKnuth86">Donald E. Knuth. <citetitle>Computers and
+Typesetting: Volume B, TeX: The Program</citetitle>. Addison-Wesley,
+1986. ISBN 0-201-13437-3.
+</bibliomixed>
+<bibliomixed id="relaxng"/>
+
+</bibliography>
+
+
+Note that it's perfectly acceptable to mix entries from your
+global bibliography with normal entries. You can use
+xref or other elements to cross-reference your
+bibliography entries in exactly the same way you do now.
+
+Finally, when you are ready to format your document, simply set the
+bibliography.collection parameter (in either a
+customization layer or directly through your processor's interface) to
+point to your global bibliography.
+
+The stylesheets will format the bibliography in your document as if
+all of the entries referenced appeared there literally.
+
+
+
+
+
+
+bibliography.numbered
+boolean
+
+
+bibliography.numbered
+Should bibliography entries be numbered?
+
+
+
+
+<xsl:param name="bibliography.numbered" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero bibliography entries will be numbered
+
+
+
+
+
+
+ biblioentry.properties
+ attribute set
+
+
+biblioentry.properties
+To set the style for biblioentry.
+
+
+
+<xsl:attribute-set name="biblioentry.properties" use-attribute-sets="normal.para.spacing">
+ <xsl:attribute name="start-indent">0.5in</xsl:attribute>
+ <xsl:attribute name="text-indent">-0.5in</xsl:attribute>
+</xsl:attribute-set>
+
+
+Description
+How do you want biblioentry styled?
+Set the font-size, weight, space-above and space-below, indents, etc. to the style required
+
+
+
+
+
+Glossary
+
+
+glossterm.auto.link
+boolean
+
+
+glossterm.auto.link
+Generate links from glossterm to glossentry automatically?
+
+
+
+
+<xsl:param name="glossterm.auto.link" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, links from inline glossterms to the corresponding
+glossentry elements in a glossary or glosslist
+will be automatically generated. This is useful when your glossterms are consistent
+and you don't want to add links manually.
+
+The automatic link generation feature is not used on glossterm elements
+that have a linkend attribute.
+
+
+
+
+
+
+firstterm.only.link
+boolean
+
+
+firstterm.only.link
+Does automatic glossterm linking only apply to firstterms?
+
+
+
+
+<xsl:param name="firstterm.only.link" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, only firstterms will be automatically linked
+to the glossary. If glossary linking is not enabled, this parameter
+has no effect.
+
+
+
+
+
+
+glossary.collection
+string
+
+
+glossary.collection
+Name of the glossary collection file
+
+
+
+
+<xsl:param name="glossary.collection"></xsl:param>
+
+
+
+Description
+
+Glossaries maintained independently across a set of documents
+are likely to become inconsistent unless considerable effort is
+expended to keep them in sync. It makes much more sense, usually, to
+store all of the glossary entries in a single place and simply
+extract the ones you need in each document.
+
+That's the purpose of the
+glossary.collection parameter. To setup a global
+glossary database, follow these steps:
+
+Setting Up the Glossary Database
+
+First, create a stand-alone glossary document that contains all of
+the entries that you wish to reference. Make sure that each glossary
+entry has an ID.
+
+Here's an example glossary:
+
+
+
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE glossary
+ PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
+<glossary>
+<glossaryinfo>
+<editor><firstname>Eric</firstname><surname>Raymond</surname></editor>
+<title>Jargon File 4.2.3 (abridged)</title>
+<releaseinfo>Just some test data</releaseinfo>
+</glossaryinfo>
+
+<glossdiv><title>0</title>
+
+<glossentry>
+<glossterm>0</glossterm>
+<glossdef>
+<para>Numeric zero, as opposed to the letter `O' (the 15th letter of
+the English alphabet). In their unmodified forms they look a lot
+alike, and various kluges invented to make them visually distinct have
+compounded the confusion. If your zero is center-dotted and letter-O
+is not, or if letter-O looks almost rectangular but zero looks more
+like an American football stood on end (or the reverse), you're
+probably looking at a modern character display (though the dotted zero
+seems to have originated as an option on IBM 3270 controllers). If
+your zero is slashed but letter-O is not, you're probably looking at
+an old-style ASCII graphic set descended from the default typewheel on
+the venerable ASR-33 Teletype (Scandinavians, for whom /O is a letter,
+curse this arrangement). (Interestingly, the slashed zero long
+predates computers; Florian Cajori's monumental "A History of
+Mathematical Notations" notes that it was used in the twelfth and
+thirteenth centuries.) If letter-O has a slash across it and the zero
+does not, your display is tuned for a very old convention used at IBM
+and a few other early mainframe makers (Scandinavians curse <emphasis>this</emphasis>
+arrangement even more, because it means two of their letters collide).
+Some Burroughs/Unisys equipment displays a zero with a <emphasis>reversed</emphasis>
+slash. Old CDC computers rendered letter O as an unbroken oval and 0
+as an oval broken at upper right and lower left. And yet another
+convention common on early line printers left zero unornamented but
+added a tail or hook to the letter-O so that it resembled an inverted
+Q or cursive capital letter-O (this was endorsed by a draft ANSI
+standard for how to draw ASCII characters, but the final standard
+changed the distinguisher to a tick-mark in the upper-left corner).
+Are we sufficiently confused yet?</para>
+</glossdef>
+</glossentry>
+
+<glossentry>
+<glossterm>1TBS</glossterm>
+<glossdef>
+<para role="accidence">
+<phrase role="pronounce"></phrase>
+<phrase role="partsofspeach">n</phrase>
+</para>
+<para>The "One True Brace Style"</para>
+<glossseealso>indent style</glossseealso>
+</glossdef>
+</glossentry>
+
+<!-- ... -->
+
+</glossdiv>
+
+<!-- ... -->
+
+</glossary>
+
+
+
+
+Marking Up Glossary Terms
+
+That takes care of the glossary database, now you have to get the entries
+into your document. Unlike bibliography entries, which can be empty, creating
+placeholder glossary entries would be very tedious. So instead,
+support for glossary.collection relies on implicit linking.
+
+In your source document, simply use firstterm and
+glossterm to identify the terms you wish to have included
+in the glossary. The stylesheets assume that you will either set the
+baseform attribute correctly, or that the
+content of the element exactly matches a term in your glossary.
+
+If you're using a glossary.collection, don't
+make explicit links on the terms in your document.
+
+So, in your document, you might write things like this:
+
+
+<para>This is dummy text, without any real meaning.
+The point is simply to reference glossary terms like <glossterm>0</glossterm>
+and the <firstterm baseform="1TBS">One True Brace Style (1TBS)</firstterm>.
+The <glossterm>1TBS</glossterm>, as you can probably imagine, is a nearly
+religious issue.</para>
+
+
+If you set the firstterm.only.link parameter,
+only the terms marked with firstterm will be links.
+Otherwise, all the terms will be linked.
+
+
+
+Marking Up the Glossary
+
+The glossary itself has to be identified for the stylesheets. For lack
+of a better choice, the role is used.
+To identify the glossary as the target for automatic processing, set
+the role to auto. The title of this
+glossary (and any other information from the glossaryinfo
+that's rendered by your stylesheet) will be displayed, but the entries will
+come from the database.
+
+
+Unfortunately, the glossary can't be empty, so you must put in
+at least one glossentry. The content of this entry
+is irrelevant, it will not be rendered:
+
+
+<glossary role="auto">
+<glossentry>
+<glossterm>Irrelevant</glossterm>
+<glossdef>
+<para>If you can see this, the document was processed incorrectly. Use
+the <parameter>glossary.collection</parameter> parameter.</para>
+</glossdef>
+</glossentry>
+</glossary>
+
+
+What about glossary divisions? If your glossary database has glossary
+divisions and your automatic glossary contains at least
+one glossdiv, the automic glossary will have divisions.
+If the glossdiv is missing from either location, no divisions
+will be rendered.
+
+Glossary entries (and divisions, if appropriate) in the glossary will
+occur in precisely the order they occur in your database.
+
+
+
+Formatting the Document
+
+Finally, when you are ready to format your document, simply set the
+glossary.collection parameter (in either a
+customization layer or directly through your processor's interface) to
+point to your global glossary.
+
+The stylesheets will format the glossary in your document as if
+all of the entries implicilty referenced appeared there literally.
+
+
+Limitations
+
+Glossary cross-references within the glossary are
+not supported. For example, this will not work:
+
+
+<glossentry>
+<glossterm>gloss-1</glossterm>
+<glossdef><para>A description that references <glossterm>gloss-2</glossterm>.</para>
+<glossseealso>gloss-2</glossseealso>
+</glossdef>
+</glossentry>
+
+
+If you put glossary cross-references in your glossary that way,
+you'll get the cryptic error: Warning:
+glossary.collection specified, but there are 0 automatic
+glossaries.
+
+Instead, you must do two things:
+
+
+
+Markup your glossary using glossseealso:
+
+
+<glossentry>
+<glossterm>gloss-1</glossterm>
+<glossdef><para>A description that references <glossterm>gloss-2</glossterm>.</para>
+<glossseealso>gloss-2</glossseealso>
+</glossdef>
+</glossentry>
+
+
+
+
+Make sure there is at least one glossterm reference to
+gloss-2in your document. The
+easiest way to do that is probably within a remark in your
+automatic glossary:
+
+
+<glossary role="auto">
+<remark>Make sure there's a reference to <glossterm>gloss-2</glossterm>.</remark>
+<glossentry>
+<glossterm>Irrelevant</glossterm>
+<glossdef>
+<para>If you can see this, the document was processed incorrectly. Use
+the <parameter>glossary.collection</parameter> parameter.</para>
+</glossdef>
+</glossentry>
+</glossary>
+
+
+
+
+
+
+
+
+
+
+glossterm.separation
+length
+
+
+glossterm.separation
+Separation between glossary terms and descriptions in list mode
+
+
+
+
+<xsl:param name="glossterm.separation">0.25in</xsl:param>
+
+
+
+Description
+
+Specifies the separation between glossary terms and descriptions when
+glossarys are presented using lists.
+
+
+
+
+
+
+glossterm.width
+length
+
+
+glossterm.width
+Width of glossterm in list presentation mode
+
+
+
+
+<xsl:param name="glossterm.width">2in</xsl:param>
+
+
+
+Description
+
+This parameter specifies the width reserved for glossary terms when
+a list presentation is used.
+
+
+
+
+
+
+glossary.as.blocks
+boolean
+
+
+glossary.as.blocks
+Present glossarys using blocks instead of lists?
+
+
+
+
+<xsl:param name="glossary.as.blocks" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, glossarys will be formatted as
+blocks.
+
+If you have long glossterms, proper list
+markup in the FO case may produce unattractive lists. By setting this
+parameter, you can force the stylesheets to produce block markup
+instead of proper lists.
+
+You can override this setting with a processing instruction as the
+child of glossary: dbfo
+glossary-presentation="blocks" or dbfo
+glossary-presentation="list"
+
+
+
+
+
+
+glosslist.as.blocks
+boolean
+
+
+glosslist.as.blocks
+Use blocks for glosslists?
+
+
+
+
+<xsl:param name="glosslist.as.blocks" select="0"></xsl:param>
+
+
+
+Description
+
+See glossary.as.blocks.
+
+
+
+
+
+
+glossentry.show.acronym
+list
+no
+yes
+primary
+
+
+glossentry.show.acronym
+Display glossentry acronyms?
+
+
+
+
+<xsl:param name="glossentry.show.acronym">no</xsl:param>
+
+
+
+Description
+
+A setting of yes means they should be displayed;
+no means they shouldn't. If primary is used,
+then they are shown as the primary text for the entry.
+
+
+This setting controls both acronym and
+abbrev elements in the glossentry.
+
+
+
+
+
+
+
+glossary.sort
+boolean
+
+
+glossary.sort
+Sort glossentry elements?
+
+
+
+
+<xsl:param name="glossary.sort" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, then the glossentry elements within a
+glossary, glossdiv, or glosslist are sorted on the glossterm, using
+the current lang setting. If zero (the default), then
+glossentry elements are not sorted and are presented
+in document order.
+
+
+
+
+
+
+Miscellaneous
+
+
+formal.procedures
+boolean
+
+
+formal.procedures
+Selects formal or informal procedures
+
+
+
+
+<xsl:param name="formal.procedures" select="1"></xsl:param>
+
+
+
+Description
+
+Formal procedures are numbered and always have a title.
+
+
+
+
+
+
+
+formal.title.placement
+table
+
+
+formal.title.placement
+Specifies where formal object titles should occur
+
+
+
+
+<xsl:param name="formal.title.placement">
+figure before
+example before
+equation before
+table before
+procedure before
+task before
+</xsl:param>
+
+
+
+Description
+
+Specifies where formal object titles should occur. For each formal object
+type (figure,
+example,
+equation,
+table, and procedure)
+you can specify either the keyword
+before or
+after.
+
+
+
+
+
+
+runinhead.default.title.end.punct
+string
+
+
+runinhead.default.title.end.punct
+Default punctuation character on a run-in-head
+
+
+
+<xsl:param name="runinhead.default.title.end.punct">.</xsl:param>
+
+
+
+Description
+
+If non-zero, For a formalpara, use the specified
+string as the separator between the title and following text. The period is the default value.
+
+
+
+
+
+
+runinhead.title.end.punct
+string
+
+
+runinhead.title.end.punct
+Characters that count as punctuation on a run-in-head
+
+
+
+
+<xsl:param name="runinhead.title.end.punct">.!?:</xsl:param>
+
+
+
+Description
+
+Specify which characters are to be counted as punctuation. These
+characters are checked for a match with the last character of the
+title. If no match is found, the
+runinhead.default.title.end.punct contents are
+inserted. This is to avoid duplicated punctuation in the output.
+
+
+
+
+
+
+
+show.comments
+boolean
+
+
+show.comments
+Display remark elements?
+
+
+
+
+<xsl:param name="show.comments" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, comments will be displayed, otherwise they
+are suppressed. Comments here refers to the remark element
+(which was called comment prior to DocBook
+4.0), not XML comments (<-- like this -->) which are
+unavailable.
+
+
+
+
+
+
+
+punct.honorific
+string
+
+
+punct.honorific
+Punctuation after an honorific in a personal name.
+
+
+
+
+<xsl:param name="punct.honorific">.</xsl:param>
+
+
+
+Description
+
+This parameter specifies the punctuation that should be added after an
+honorific in a personal name.
+
+
+
+
+
+
+segmentedlist.as.table
+boolean
+
+
+segmentedlist.as.table
+Format segmented lists as tables?
+
+
+
+
+<xsl:param name="segmentedlist.as.table" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, segmentedlists will be formatted as
+tables.
+
+
+
+
+
+
+variablelist.as.blocks
+boolean
+
+
+variablelist.as.blocks
+Format variablelists lists as blocks?
+
+
+
+
+<xsl:param name="variablelist.as.blocks" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, variablelists will be formatted as
+blocks.
+
+If you have long terms, proper list markup in the FO case may produce
+unattractive lists. By setting this parameter, you can force the stylesheets
+to produce block markup instead of proper lists.
+
+You can override this setting with a processing instruction as the
+child of variablelist: dbfo
+list-presentation="blocks" or dbfo
+list-presentation="list".
+
+When using list-presentation="list",
+you can also control the amount of space used for the terms with
+the dbfo term-width=".25in" processing instruction,
+the termlength attribute on variablelist,
+or allow the stylesheets to attempt to calculate the amount of space to leave based on the
+number of letters in the longest term.
+
+
+ <variablelist>
+ <?dbfo list-presentation="list"?>
+ <?dbfo term-width="1.5in"?>
+ <?dbhtml list-presentation="table"?>
+ <?dbhtml term-width="1.5in"?>
+ <varlistentry>
+ <term>list</term>
+ <listitem>
+ <para>
+ Formatted as a list even if variablelist.as.blocks is set to 1.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+
+
+
+
+
+
+
+ blockquote.properties
+ attribute set
+
+
+blockquote.properties
+To set the style for block quotations.
+
+
+
+
+<xsl:attribute-set name="blockquote.properties">
+<xsl:attribute name="margin-left">0.5in</xsl:attribute>
+<xsl:attribute name="margin-right">0.5in</xsl:attribute>
+<xsl:attribute name="space-after.minimum">0.5em</xsl:attribute>
+<xsl:attribute name="space-after.optimum">1em</xsl:attribute>
+<xsl:attribute name="space-after.maximum">2em</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The blockquote.properties attribute set specifies
+the formating properties of block quotations.
+
+
+
+
+
+
+ulink.show
+boolean
+
+
+ulink.show
+Display URLs after ulinks?
+
+
+
+
+<xsl:param name="ulink.show" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, the URL of each ulink will
+appear after the text of the link. If the text of the link and the URL
+are identical, the URL is suppressed.
+
+See also ulink.footnotes.
+
+DocBook 5 does not have an ulink element. When processing
+DocBoook 5 documents, ulink.show applies to all inline
+elements that are marked up with xlink:href attributes
+that point to external resources.
+
+
+
+
+
+
+
+ulink.footnotes
+boolean
+
+
+ulink.footnotes
+Generate footnotes for ulinks?
+
+
+
+
+<xsl:param name="ulink.footnotes" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, and if ulink.show also is non-zero,
+the URL of each ulink will appear as a footnote.
+
+DocBook 5 does not have an ulink element. When processing
+DocBoook 5 documents, ulink.footnotes applies to all inline
+elements that are marked up with xlink:href attributes
+that point to external resources.
+
+
+
+
+
+
+
+ulink.hyphenate
+string
+
+
+ulink.hyphenate
+Allow URLs to be automatically hyphenated
+
+
+
+
+<xsl:param name="ulink.hyphenate"></xsl:param>
+
+
+
+Description
+
+If not empty, the specified character (or more generally, content) is
+added to URLs after every character included in the string
+in the ulink.hyphenate.chars parameter (default
+is /). If the character in this parameter is a
+Unicode soft hyphen (0x00AD) or Unicode zero-width space (0x200B), some FO
+processors will be able to reasonably hyphenate long URLs.
+
+As of 28 Jan 2002, discretionary hyphens are more widely and correctly
+supported than zero-width spaces for this purpose.
+
+
+
+
+
+
+ulink.hyphenate.chars
+string
+
+
+ulink.hyphenate.chars
+List of characters to allow ulink URLs to be automatically hyphenated on
+
+
+
+
+<xsl:param name="ulink.hyphenate.chars">/</xsl:param>
+
+
+
+Description
+
+If the ulink.hyphenate is not empty, then
+hyphenation of ulinks is turned on, and any
+character contained in this parameter is treated as an allowable
+hyphenation point.
+
+The default value is /, but the parameter
+could be customized
+to contain other URL characters, as for example:
+
+<xsl:param name="ulink.hyphenate.chars">:/@&?.#</xsl:param>
+
+
+
+
+
+
+
+shade.verbatim
+boolean
+
+
+shade.verbatim
+Should verbatim environments be shaded?
+
+
+
+<xsl:param name="shade.verbatim" select="0"></xsl:param>
+
+
+Description
+
+In the FO stylesheet, if this parameter is non-zero then the
+shade.verbatim.style properties will be applied
+to verbatim environments.
+
+In the HTML stylesheet, this parameter is now deprecated. Use
+CSS instead.
+
+
+
+
+
+
+shade.verbatim.style
+attribute set
+
+
+shade.verbatim.style
+Properties that specify the style of shaded verbatim listings
+
+
+
+
+
+<xsl:attribute-set name="shade.verbatim.style">
+ <xsl:attribute name="background-color">#E0E0E0</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Properties that specify the style of shaded verbatim listings. The
+parameters specified (the border and background color) are added to
+the styling of the xsl-fo output. A border might be specified as "thin
+black solid" for example. See xsl-fo
+
+
+
+
+
+
+hyphenate.verbatim
+boolean
+
+
+hyphenate.verbatim
+Should verbatim environments be hyphenated on space characters?
+
+
+
+<xsl:param name="hyphenate.verbatim" select="0"></xsl:param>
+
+
+Description
+
+If the lines of program listing are too long to fit into one
+line it is quite common to split them at space and indicite by hook
+arrow that code continues on the next line. You can turn on this
+behaviour for programlisting,
+screen and synopsis elements by
+using this parameter.
+
+Note that you must also enable line wrapping for verbatim environments and
+select appropriate hyphenation character (e.g. hook arrow). This can
+be done using monospace.verbatim.properties
+attribute set:
+
+<xsl:attribute-set name="monospace.verbatim.properties"
+ use-attribute-sets="verbatim.properties monospace.properties">
+ <xsl:attribute name="wrap-option">wrap</xsl:attribute>
+ <xsl:attribute name="hyphenation-character">►</xsl:attribute>
+</xsl:attribute-set>
+
+For a list of arrows available in Unicode see http://www.unicode.org/charts/PDF/U2190.pdf and http://www.unicode.org/charts/PDF/U2900.pdf and make sure that
+selected character is available in the font you are using for verbatim
+environments.
+
+
+
+
+
+
+hyphenate.verbatim.characters
+string
+
+
+hyphenate.verbatim.characters
+List of characters after which line break can occur in listings
+
+
+
+
+<xsl:param name="hyphenate.verbatim.characters"></xsl:param>
+
+
+
+Description
+
+If you enable hyphenate.verbatim line
+breaks are allowed only on space characters. If this is not enough for
+your document, you can specify list of additional characters after
+which line break is allowed in this parameter.
+
+
+
+
+
+
+use.svg
+boolean
+
+
+use.svg
+Allow SVG in the result tree?
+
+
+
+
+<xsl:param name="use.svg" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, SVG will be considered an acceptable image format. SVG
+is passed through to the result tree, so correct rendering of the resulting
+diagram depends on the formatter (FO processor or web browser) that is used
+to process the output from the stylesheet.
+
+
+
+
+
+
+use.role.as.xrefstyle
+boolean
+
+
+use.role.as.xrefstyle
+Use role attribute for
+xrefstyle on xref?
+
+
+
+
+<xsl:param name="use.role.as.xrefstyle" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, the role attribute on
+xref will be used to select the cross reference style.
+The DocBook
+Technical Committee recently added an
+xrefstyle attribute for this purpose.
+If the xrefstyle attribute
+is present, role will be ignored, regardless
+of this setting.
+
+Until an official DocBook release that includes the new
+attribute, this flag allows role
+to serve that purpose.
+
+
+
+Example
+
+The following small stylesheet shows how to configure the
+stylesheets to make use of the cross reference style:
+
+<?xml version="1.0"?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ version="1.0">
+
+<xsl:import href="../xsl/html/docbook.xsl"/>
+
+<xsl:output method="html"/>
+
+<xsl:param name="local.l10n.xml" select="document('')"/>
+<l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
+ <l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="en">
+ <l:context name="xref">
+ <l:template name="chapter" style="title" text="Chapter %n, %t"/>
+ <l:template name="chapter" text="Chapter %n"/>
+ </l:context>
+ </l:l10n>
+</l:i18n>
+
+</xsl:stylesheet>
+
+With this stylesheet, the cross references in the following document:
+
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<book id="book"><title>Book</title>
+
+<preface>
+<title>Preface</title>
+
+<para>Normal: <xref linkend="ch1"/>.</para>
+<para>Title: <xref xrefstyle="title" linkend="ch1"/>.</para>
+
+</preface>
+
+<chapter id="ch1">
+<title>First Chapter</title>
+
+<para>Irrelevant.</para>
+
+</chapter>
+</book>
+
+will appear as:
+
+
+Normal: Chapter 1.
+Title: Chapter 1, First Chapter.
+
+
+
+
+
+
+
+menuchoice.separator
+string
+
+
+menuchoice.separator
+Separator between items of a menuchoice
+other than guimenuitem and
+guisubmenu
+
+
+
+
+<xsl:param name="menuchoice.separator">+</xsl:param>
+
+
+
+Description
+
+Separator used to connect items of a menuchoice other
+than guimenuitem and guisubmenu. The latter
+elements are linked with menuchoice.menu.separator.
+
+
+
+
+
+
+
+menuchoice.menu.separator
+string
+
+
+menuchoice.menu.separator
+Separator between items of a menuchoice
+with guimenuitem or
+guisubmenu
+
+
+
+
+<xsl:param name="menuchoice.menu.separator"> → </xsl:param>
+
+
+
+Description
+
+Separator used to connect items of a menuchoice with
+guimenuitem or guisubmenu. Other elements
+are linked with menuchoice.separator.
+
+The default value is →, which is the
+→ (right arrow) character entity.
+The current FOP (0.20.5) requires setting the font-family
+explicitly.
+
+The default value also includes spaces around the arrow,
+which will allow a line to break. Replace the spaces with
+  (nonbreaking space) if you don't want those
+spaces to break.
+
+
+
+
+
+
+
+default.float.class
+string
+
+
+default.float.class
+Specifies the default float class
+
+
+
+
+<xsl:param name="default.float.class">
+ <xsl:choose>
+ <xsl:when test="contains($stylesheet.result.type,'html')">left</xsl:when>
+ <xsl:otherwise>before</xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+
+Description
+
+Selects the direction in which a float should be placed. for
+xsl-fo this is before, for html it is left. For Western texts, the
+before direction is the top of the page.
+
+
+
+
+
+
+footnote.number.format
+list
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+footnote.number.format
+Identifies the format used for footnote numbers
+
+
+
+
+<xsl:param name="footnote.number.format">1</xsl:param>
+
+
+
+Description
+
+The footnote.number.format specifies the format
+to use for footnote numeration (1, i, I, a, or A).
+
+
+
+
+
+
+table.footnote.number.format
+list
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+table.footnote.number.format
+Identifies the format used for footnote numbers in tables
+
+
+
+
+<xsl:param name="table.footnote.number.format">a</xsl:param>
+
+
+
+Description
+
+The table.footnote.number.format specifies the format
+to use for footnote numeration (1, i, I, a, or A) in tables.
+
+
+
+
+
+
+footnote.number.symbols
+
+
+
+footnote.number.symbols
+Special characters to use as footnote markers
+
+
+
+
+<xsl:param name="footnote.number.symbols"></xsl:param>
+
+
+
+Description
+
+If footnote.number.symbols is not the empty string,
+footnotes will use the characters it contains as footnote symbols. For example,
+*†‡◊✠ will identify
+footnotes with *, †, ‡,
+◊, and ✠. If there are more footnotes
+than symbols, the stylesheets will fall back to numbered footnotes using
+footnote.number.format.
+
+The use of symbols for footnotes depends on the ability of your
+processor (or browser) to render the symbols you select. Not all systems are
+capable of displaying the full range of Unicode characters. If the quoted characters
+in the preceding paragraph are not displayed properly, that's a good indicator
+that you may have trouble using those symbols for footnotes.
+
+
+
+
+
+
+table.footnote.number.symbols
+string
+
+
+table.footnote.number.symbols
+Special characters to use a footnote markers in tables
+
+
+
+
+<xsl:param name="table.footnote.number.symbols"></xsl:param>
+
+
+
+Description
+
+If table.footnote.number.symbols is not the empty string,
+table footnotes will use the characters it contains as footnote symbols. For example,
+*†‡◊✠ will identify
+footnotes with *, †, ‡,
+◊, and ✠. If there are more footnotes
+than symbols, the stylesheets will fall back to numbered footnotes using
+table.footnote.number.format.
+
+The use of symbols for footnotes depends on the ability of your
+processor (or browser) to render the symbols you select. Not all systems are
+capable of displaying the full range of Unicode characters. If the quoted characters
+in the preceding paragraph are not displayed properly, that's a good indicator
+that you may have trouble using those symbols for footnotes.
+
+
+
+
+
+
+footnote.properties
+attribute set
+
+
+footnote.properties
+Properties applied to each footnote body
+
+
+
+
+
+<xsl:attribute-set name="footnote.properties">
+ <xsl:attribute name="font-family"><xsl:value-of select="$body.fontset"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="font-size"><xsl:value-of select="$footnote.font.size"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="font-weight">normal</xsl:attribute>
+ <xsl:attribute name="font-style">normal</xsl:attribute>
+ <xsl:attribute name="text-align"><xsl:value-of select="$alignment"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="start-indent">0pt</xsl:attribute>
+ <xsl:attribute name="text-indent">0pt</xsl:attribute>
+ <xsl:attribute name="hyphenate"><xsl:value-of select="$hyphenate"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="wrap-option">wrap</xsl:attribute>
+ <xsl:attribute name="linefeed-treatment">treat-as-space</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+This attribute set is applied to the footnote-block
+for each footnote.
+It can be used to set the
+font-size, font-family, and other inheritable properties that will be
+applied to all footnotes.
+
+
+
+
+
+
+table.footnote.properties
+attribute set
+
+
+table.footnote.properties
+Properties applied to each table footnote body
+
+
+
+
+
+<xsl:attribute-set name="table.footnote.properties">
+ <xsl:attribute name="font-family"><xsl:value-of select="$body.fontset"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="font-size"><xsl:value-of select="$footnote.font.size"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="font-weight">normal</xsl:attribute>
+ <xsl:attribute name="font-style">normal</xsl:attribute>
+ <xsl:attribute name="space-before">2pt</xsl:attribute>
+ <xsl:attribute name="text-align"><xsl:value-of select="$alignment"></xsl:value-of></xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+This attribute set is applied to the footnote-block
+for each table footnote.
+It can be used to set the
+font-size, font-family, and other inheritable properties that will be
+applied to all table footnotes.
+
+
+
+
+
+
+footnote.mark.properties
+attribute set
+
+
+footnote.mark.properties
+Properties applied to each footnote mark
+
+
+
+
+
+<xsl:attribute-set name="footnote.mark.properties">
+ <xsl:attribute name="font-size">75%</xsl:attribute>
+ <xsl:attribute name="font-weight">normal</xsl:attribute>
+ <xsl:attribute name="font-style">normal</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+This attribute set is applied to the footnote mark used
+for each footnote.
+It should contain only inline properties.
+
+
+The property to make the mark a superscript is contained in the
+footnote template itself, because the current version of FOP reports
+an error if baseline-shift is used.
+
+
+
+
+
+
+
+footnote.sep.leader.properties
+attribute set
+
+
+footnote.sep.leader.properties
+Properties associated with footnote separators
+
+
+
+
+<xsl:attribute-set name="footnote.sep.leader.properties">
+ <xsl:attribute name="color">black</xsl:attribute>
+ <xsl:attribute name="leader-pattern">rule</xsl:attribute>
+ <xsl:attribute name="leader-length">1in</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The styling for the rule line that separates the
+footnotes from the body text.
+These are properties applied to the fo:leader used as
+the separator.
+
+If you want to do more than just set properties on
+the leader element, then you can customize the template
+named footnote.separator in
+fo/pagesetup.xsl.
+
+
+
+
+
+
+xref.with.number.and.title
+boolean
+
+
+xref.with.number.and.title
+Use number and title in cross references
+
+
+
+
+<xsl:param name="xref.with.number.and.title" select="1"></xsl:param>
+
+
+
+Description
+
+A cross reference may include the number (for example, the number of
+an example or figure) and the title which is a required child of some
+targets. This parameter inserts both the relevant number as well as
+the title into the link.
+
+
+
+
+
+
+superscript.properties
+attribute set
+
+
+superscript.properties
+Properties associated with superscripts
+
+
+
+
+<xsl:attribute-set name="superscript.properties">
+ <xsl:attribute name="font-size">75%</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Specifies styling properties for superscripts.
+
+
+
+
+
+
+subscript.properties
+attribute set
+
+
+subscript.properties
+Properties associated with subscripts
+
+
+
+
+<xsl:attribute-set name="subscript.properties">
+ <xsl:attribute name="font-size">75%</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Specifies styling properties for subscripts.
+
+
+
+
+
+
+pgwide.properties
+attribute set
+
+
+pgwide.properties
+Properties to make a figure or table page wide.
+
+
+
+
+
+<xsl:attribute-set name="pgwide.properties">
+ <xsl:attribute name="start-indent">0pt</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+This attribute set is used to set the properties
+that make a figure or table "page wide" in fo output.
+It comes into effect when an attribute pgwide="1"
+is used.
+
+
+
+By default, it sets start-indent
+to 0pt.
+In a stylesheet that sets the parameter
+body.start.indent
+to a non-zero value in order to indent body text,
+this attribute set can be used to outdent pgwide
+figures to the left margin.
+
+
+If a document uses a multi-column page layout,
+then this attribute set could try setting span
+to a value of all. However, this may
+not work with some processors because a span property must be on an
+fo:block that is a direct child of fo:flow. It may work in
+some processors anyway.
+
+
+
+
+
+
+
+highlight.source
+boolean
+
+
+highlight.source
+Should the content of programlisting
+be syntactically highlighted?
+
+
+
+
+<xsl:param name="highlight.source" select="0"></xsl:param>
+
+
+
+Description
+
+When this parameter is non-zero, the stylesheets will try to do
+syntax highlighting of the content of the programlisting element. The highlighting is done by the
+XSLTHL extension module. This is an external Java library which is not part of the DocBook XSL distribution.
+
+In order to use this extension, you must add
+xslthl-2.0.0.jar to your Java classpath. You can
+download this software from the XSLT syntax highlighting project at SourceForge.
+
+The configuration of syntax highlighting is stored in
+highlighting/xslthl-config.xml. The Java
+property xslthl.config or parameter highlight.xslthl.config must point to this
+file (using URL syntax).
+
+This extension is known to work with Saxon 6.5.x, Saxon 8.5+ and Xalan-J. Here is an example of a modified Saxon command:
+
+java -cp c:\batch\;…;c:\path\to\xslthl-2.0.0.jar -Dxslthl.config=file:///c:/docbook-xsl/highlighting/xslthl-config.xml … com.icl.saxon.StyleSheet …
+
+You can specify the language for each programlisting by using the language attribute. The
+highlighting.default.language parameter can be used for specifying the
+language to be used for programlistings without a language attribute.
+
+
+
+
+
+
+highlight.xslthl.config
+uri
+
+
+highlight.xslthl.config
+Location of XSLTHL configuration file
+
+
+
+
+<xsl:param name="highlight.xslthl.config"></xsl:param>
+
+
+
+Description
+
+This location has precedence over the corresponding Java property.
+
+
+
+
+
+
+highlight.default.language
+string
+
+
+highlight.default.language
+Default language of programlisting
+
+
+
+
+<xsl:param name="highlight.default.language"></xsl:param>
+
+
+
+Description
+
+This language is used when there is no language attribute on programlisting.
+
+
+
+
+
+
+email.delimiters.enabled
+boolean
+
+
+email.delimiters.enabled
+Generate delimiters around email addresses?
+
+
+
+
+<xsl:param name="email.delimiters.enabled" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, delimiters
+
+For delimiters, the
+stylesheets are currently hard-coded to output angle
+brackets.
+
+are generated around e-mail addresses
+(the output of the email element).
+
+
+
+
+
+
+section.container.element
+list
+block
+wrapper
+
+
+section.container.element
+Select XSL-FO element name to contain sections
+
+
+
+
+<xsl:param name="section.container.element">block</xsl:param>
+
+
+
+Description
+
+Selects the element name for outer container of
+each section. The choices are block (default)
+or wrapper.
+The fo: namespace prefix is added
+by the stylesheet to form the full element name.
+
+
+This element receives the section id
+attribute and the appropriate section level attribute-set.
+
+
+Changing this parameter to wrapper
+is only necessary when producing multi-column output
+that contains page-wide spans. Using fo:wrapper
+avoids the nesting of fo:block
+elements that prevents spans from working (the standard says
+a span must be on a block that is a direct child of
+fo:flow).
+
+
+If set to wrapper, the
+section attribute-sets only support properties
+that are inheritable. That's because there is no
+block to apply them to. Properties such as
+font-family are inheritable, but properties such as
+border are not.
+
+
+Only some XSL-FO processors need to use this parameter.
+The Antenna House processor, for example, will handle
+spans in nested blocks without changing the element name.
+The RenderX XEP product and FOP follow the XSL-FO standard
+and need to use wrapper.
+
+
+
+
+
+
+Graphics
+
+
+graphic.default.extension
+string
+
+
+graphic.default.extension
+Default extension for graphic filenames
+
+
+
+<xsl:param name="graphic.default.extension"></xsl:param>
+
+
+Description
+
+If a graphic or mediaobject
+includes a reference to a filename that does not include an extension,
+and the format attribute is
+unspecified, the default extension will be used.
+
+
+
+
+
+
+
+default.image.width
+length
+
+
+default.image.width
+The default width of images
+
+
+
+
+<xsl:param name="default.image.width"></xsl:param>
+
+
+
+Description
+
+If specified, this value will be used for the
+width attribute on
+images that do not specify any
+viewport
+dimensions.
+
+
+
+
+
+
+preferred.mediaobject.role
+string
+
+
+preferred.mediaobject.role
+Select which mediaobject to use based on
+this value of an object's role attribute.
+
+
+
+
+
+<xsl:param name="preferred.mediaobject.role"></xsl:param>
+
+
+
+Description
+
+A mediaobject may contain several objects such as imageobjects.
+If the parameter use.role.for.mediaobject is
+non-zero, then the role attribute on
+imageobjects and other objects within a
+mediaobject container will be used to select which object
+will be used. If one of the objects has a role value that matches the
+preferred.mediaobject.role parameter, then it
+has first priority for selection. If more than one has such a role
+value, the first one is used.
+
+
+See the use.role.for.mediaobject parameter
+for the sequence of selection.
+
+
+
+
+
+use.role.for.mediaobject
+boolean
+
+
+use.role.for.mediaobject
+Use role attribute
+value for selecting which of several objects within a mediaobject to use.
+
+
+
+
+
+<xsl:param name="use.role.for.mediaobject" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, the role attribute on
+imageobjects or other objects within a mediaobject container will be used to select which object will be
+used.
+
+
+The order of selection when then parameter is non-zero is:
+
+
+
+ If the stylesheet parameter preferred.mediaobject.role has a value, then the object whose role equals that value is selected.
+
+
+Else if an object's role attribute has a value of
+html for HTML processing or
+fo for FO output, then the first
+of such objects is selected.
+
+
+
+Else the first suitable object is selected.
+
+
+
+If the value of
+use.role.for.mediaobject
+is zero, then role attributes are not considered
+and the first suitable object
+with or without a role value is used.
+
+
+
+
+
+
+ignore.image.scaling
+boolean
+
+
+ignore.image.scaling
+Tell the stylesheets to ignore the author's image scaling attributes
+
+
+
+
+<xsl:param name="ignore.image.scaling" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the scaling attributes on graphics and media objects are
+ignored.
+
+
+
+
+
+
+img.src.path
+string
+
+
+img.src.path
+Path to HTML/FO image files
+
+
+
+<xsl:param name="img.src.path"></xsl:param>
+
+
+Description
+
+Add a path prefix to the value of the fileref
+attribute of graphic, inlinegraphic, and imagedata elements. The resulting
+compound path is used in the output as the value of the src
+attribute of img (HTML) or external-graphic (FO).
+
+
+
+The path given by img.src.path could be relative to the directory where the HTML/FO
+files are created, or it could be an absolute URI.
+The default value is empty.
+Be sure to include a trailing slash if needed.
+
+
+This prefix is not applied to any filerefs that start
+with "/" or contain "//:".
+
+
+
+
+
+
+
+keep.relative.image.uris
+boolean
+
+
+keep.relative.image.uris
+Should image URIs be resolved against xml:base?
+
+
+
+
+
+<xsl:param name="keep.relative.image.uris" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, relative URIs (in, for example
+fileref attributes) will be used in the generated
+output. Otherwise, the URIs will be made absolute with respect to the
+base URI.
+
+Note that the stylesheets calculate (and use) the absolute form
+for some purposes, this only applies to the resulting output.
+
+
+
+
+
+Pagination and General Styles
+
+Understanding XSL FO Margins
+
+To make sense of the parameters in this section, it's useful to
+consider .
+
+
+ Page Model
+
+
+
+
+
+
+
+ Figure showing page margins
+
+ This figure shows the physical page with the various FO page regions
+ identified.
+
+
+
+
+First, let's consider the regions on the page.
+
+The white region is the physical page. Its dimensions are determined by
+the page.height and page.width
+parameters.
+
+The yellow region is the region-body. The size and placement of
+the region body is constrained by the dimensions labelled in the
+figure.
+
+The pink region at the top of the page is the region-before. The
+darker area inside the region-before is the header text. In XSL, the default
+display alignment for a region is before, but the
+DocBook stylesheets still explicitly make it before. That's
+why the darker area is at the top.
+
+The pink region at the bottom of the page is the region-after.
+The darker area is the footer text. In XSL, the default display
+alignment for a region is before,
+but the DocBook stylesheets explicitly make it
+after. That's why the darker area is at the bottom.
+
+The dimensions in the figure are:
+
+
+The page-master margin-top.
+
+The region-before extent.
+
+The region-body margin-top.
+
+The region-after extent.
+
+The page-master margin-bottom.
+
+The region-body margin-bottom.
+
+The sum of the page-master margin-left and the
+region-body margin-left. In DocBook, the region-body margin-left is
+zero by default, so this is simply the page-master region-left.
+
+The sum of the page-master margin-right and the
+region-body margin-right. In DocBook, the region-body margin-right is
+zero by default, so this is simply the page-master region-left.
+
+
+
+
+
+
+
+
+page.height
+length
+
+
+page.height
+The height of the physical page
+
+
+
+<xsl:param name="page.height">
+ <xsl:choose>
+ <xsl:when test="$page.orientation = 'portrait'">
+ <xsl:value-of select="$page.height.portrait"></xsl:value-of>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:value-of select="$page.width.portrait"></xsl:value-of>
+ </xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+Description
+
+The page height is generally calculated from the
+paper.type and
+page.orientation.
+
+
+
+
+
+
+
+page.height.portrait
+length
+
+
+page.height.portrait
+Specify the physical size of the long edge of the page
+
+
+
+<xsl:param name="page.height.portrait">
+ <xsl:choose>
+ <xsl:when test="$paper.type = 'A4landscape'">210mm</xsl:when>
+ <xsl:when test="$paper.type = 'USletter'">11in</xsl:when>
+ <xsl:when test="$paper.type = 'USlandscape'">8.5in</xsl:when>
+ <xsl:when test="$paper.type = '4A0'">2378mm</xsl:when>
+ <xsl:when test="$paper.type = '2A0'">1682mm</xsl:when>
+ <xsl:when test="$paper.type = 'A0'">1189mm</xsl:when>
+ <xsl:when test="$paper.type = 'A1'">841mm</xsl:when>
+ <xsl:when test="$paper.type = 'A2'">594mm</xsl:when>
+ <xsl:when test="$paper.type = 'A3'">420mm</xsl:when>
+ <xsl:when test="$paper.type = 'A4'">297mm</xsl:when>
+ <xsl:when test="$paper.type = 'A5'">210mm</xsl:when>
+ <xsl:when test="$paper.type = 'A6'">148mm</xsl:when>
+ <xsl:when test="$paper.type = 'A7'">105mm</xsl:when>
+ <xsl:when test="$paper.type = 'A8'">74mm</xsl:when>
+ <xsl:when test="$paper.type = 'A9'">52mm</xsl:when>
+ <xsl:when test="$paper.type = 'A10'">37mm</xsl:when>
+ <xsl:when test="$paper.type = 'B0'">1414mm</xsl:when>
+ <xsl:when test="$paper.type = 'B1'">1000mm</xsl:when>
+ <xsl:when test="$paper.type = 'B2'">707mm</xsl:when>
+ <xsl:when test="$paper.type = 'B3'">500mm</xsl:when>
+ <xsl:when test="$paper.type = 'B4'">353mm</xsl:when>
+ <xsl:when test="$paper.type = 'B5'">250mm</xsl:when>
+ <xsl:when test="$paper.type = 'B6'">176mm</xsl:when>
+ <xsl:when test="$paper.type = 'B7'">125mm</xsl:when>
+ <xsl:when test="$paper.type = 'B8'">88mm</xsl:when>
+ <xsl:when test="$paper.type = 'B9'">62mm</xsl:when>
+ <xsl:when test="$paper.type = 'B10'">44mm</xsl:when>
+ <xsl:when test="$paper.type = 'C0'">1297mm</xsl:when>
+ <xsl:when test="$paper.type = 'C1'">917mm</xsl:when>
+ <xsl:when test="$paper.type = 'C2'">648mm</xsl:when>
+ <xsl:when test="$paper.type = 'C3'">458mm</xsl:when>
+ <xsl:when test="$paper.type = 'C4'">324mm</xsl:when>
+ <xsl:when test="$paper.type = 'C5'">229mm</xsl:when>
+ <xsl:when test="$paper.type = 'C6'">162mm</xsl:when>
+ <xsl:when test="$paper.type = 'C7'">114mm</xsl:when>
+ <xsl:when test="$paper.type = 'C8'">81mm</xsl:when>
+ <xsl:when test="$paper.type = 'C9'">57mm</xsl:when>
+ <xsl:when test="$paper.type = 'C10'">40mm</xsl:when>
+ <xsl:otherwise>11in</xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+Description
+
+The portrait page height is the length of the long
+edge of the physical page.
+
+
+
+
+
+
+
+page.margin.bottom
+length
+
+
+page.margin.bottom
+The bottom margin of the page
+
+
+
+
+<xsl:param name="page.margin.bottom">0.5in</xsl:param>
+
+
+
+Description
+
+The bottom page margin is the distance from the bottom of the region-after
+to the physical bottom of the page.
+
+
+
+
+
+
+
+page.margin.inner
+length
+
+
+page.margin.inner
+The inner page margin
+
+
+
+<xsl:param name="page.margin.inner">
+ <xsl:choose>
+ <xsl:when test="$double.sided != 0">1.25in</xsl:when>
+ <xsl:otherwise>1in</xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+Description
+
+The inner page margin is the distance from binding edge of the
+page to the first column of text. In the left-to-right, top-to-bottom writing
+direction, this is the left margin of recto pages.
+The inner and outer margins are usually the same unless the output
+is double-sided.
+
+
+
+
+
+
+
+page.margin.outer
+length
+
+
+page.margin.outer
+The outer page margin
+
+
+
+<xsl:param name="page.margin.outer">
+ <xsl:choose>
+ <xsl:when test="$double.sided != 0">0.75in</xsl:when>
+ <xsl:otherwise>1in</xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+Description
+
+The outer page margin is the distance from non-binding edge of the
+page to the last column of text. In the left-to-right, top-to-bottom writing
+direction, this is the right margin of recto pages.
+The inner and outer margins are usually the same unless the output
+is double-sided.
+
+
+
+
+
+
+
+page.margin.top
+length
+
+
+page.margin.top
+The top margin of the page
+
+
+
+
+<xsl:param name="page.margin.top">0.5in</xsl:param>
+
+
+
+Description
+
+The top page margin is the distance from the physical top of the
+page to the top of the region-before.
+
+
+
+
+
+
+page.orientation
+list
+portrait
+landscape
+
+
+page.orientation
+Select the page orientation
+
+
+
+
+<xsl:param name="page.orientation">portrait</xsl:param>
+
+
+
+Description
+
+ Select one from portrait or landscape.
+In portrait orientation, the short edge is horizontal; in
+landscape orientation, it is vertical.
+
+
+
+
+
+
+
+page.width
+length
+
+
+page.width
+The width of the physical page
+
+
+
+<xsl:param name="page.width">
+ <xsl:choose>
+ <xsl:when test="$page.orientation = 'portrait'">
+ <xsl:value-of select="$page.width.portrait"></xsl:value-of>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:value-of select="$page.height.portrait"></xsl:value-of>
+ </xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+Description
+
+The page width is generally calculated from the
+paper.type and page.orientation.
+
+
+
+
+
+
+
+page.width.portrait
+length
+
+
+page.width.portrait
+Specify the physical size of the short edge of the page
+
+
+
+<xsl:param name="page.width.portrait">
+ <xsl:choose>
+ <xsl:when test="$paper.type = 'USletter'">8.5in</xsl:when>
+ <xsl:when test="$paper.type = '4A0'">1682mm</xsl:when>
+ <xsl:when test="$paper.type = '2A0'">1189mm</xsl:when>
+ <xsl:when test="$paper.type = 'A0'">841mm</xsl:when>
+ <xsl:when test="$paper.type = 'A1'">594mm</xsl:when>
+ <xsl:when test="$paper.type = 'A2'">420mm</xsl:when>
+ <xsl:when test="$paper.type = 'A3'">297mm</xsl:when>
+ <xsl:when test="$paper.type = 'A4'">210mm</xsl:when>
+ <xsl:when test="$paper.type = 'A5'">148mm</xsl:when>
+ <xsl:when test="$paper.type = 'A6'">105mm</xsl:when>
+ <xsl:when test="$paper.type = 'A7'">74mm</xsl:when>
+ <xsl:when test="$paper.type = 'A8'">52mm</xsl:when>
+ <xsl:when test="$paper.type = 'A9'">37mm</xsl:when>
+ <xsl:when test="$paper.type = 'A10'">26mm</xsl:when>
+ <xsl:when test="$paper.type = 'B0'">1000mm</xsl:when>
+ <xsl:when test="$paper.type = 'B1'">707mm</xsl:when>
+ <xsl:when test="$paper.type = 'B2'">500mm</xsl:when>
+ <xsl:when test="$paper.type = 'B3'">353mm</xsl:when>
+ <xsl:when test="$paper.type = 'B4'">250mm</xsl:when>
+ <xsl:when test="$paper.type = 'B5'">176mm</xsl:when>
+ <xsl:when test="$paper.type = 'B6'">125mm</xsl:when>
+ <xsl:when test="$paper.type = 'B7'">88mm</xsl:when>
+ <xsl:when test="$paper.type = 'B8'">62mm</xsl:when>
+ <xsl:when test="$paper.type = 'B9'">44mm</xsl:when>
+ <xsl:when test="$paper.type = 'B10'">31mm</xsl:when>
+ <xsl:when test="$paper.type = 'C0'">917mm</xsl:when>
+ <xsl:when test="$paper.type = 'C1'">648mm</xsl:when>
+ <xsl:when test="$paper.type = 'C2'">458mm</xsl:when>
+ <xsl:when test="$paper.type = 'C3'">324mm</xsl:when>
+ <xsl:when test="$paper.type = 'C4'">229mm</xsl:when>
+ <xsl:when test="$paper.type = 'C5'">162mm</xsl:when>
+ <xsl:when test="$paper.type = 'C6'">114mm</xsl:when>
+ <xsl:when test="$paper.type = 'C7'">81mm</xsl:when>
+ <xsl:when test="$paper.type = 'C8'">57mm</xsl:when>
+ <xsl:when test="$paper.type = 'C9'">40mm</xsl:when>
+ <xsl:when test="$paper.type = 'C10'">28mm</xsl:when>
+ <xsl:otherwise>8.5in</xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+Description
+
+The portrait page width is the length of the short
+edge of the physical page.
+
+
+
+
+
+
+
+paper.type
+list
+open
+open
+USletter8.5x11in
+USlandscape11x8.5in
+4A02378x1682mm
+2A01682x1189mm
+A01189x841mm
+A1841x594mm
+A2594x420mm
+A3420x297mm
+A4297x210mm
+A5210x148mm
+A6148x105mm
+A7105x74mm
+A874x52mm
+A952x37mm
+A1037x26mm
+B01414x1000mm
+B11000x707mm
+B2707x500mm
+B3500x353mm
+B4353x250mm
+B5250x176mm
+B6176x125mm
+B7125x88mm
+B888x62mm
+B962x44mm
+B1044x31mm
+C01297x917mm
+C1917x648mm
+C2648x458mm
+C3458x324mm
+C4324x229mm
+C5229x162mm
+C6162x114mm
+C7114x81mm
+C881x57mm
+C957x40mm
+C1040x28mm
+
+
+paper.type
+Select the paper type
+
+
+
+
+<xsl:param name="paper.type">USletter</xsl:param>
+
+
+
+Description
+
+The paper type is a convenient way to specify the paper size.
+The list of known paper sizes includes USletter and most of the A,
+B, and C sizes. See page.width.portrait, for example.
+
+
+
+
+
+
+
+
+
+double.sided
+boolean
+
+
+double.sided
+Is the document to be printed double sided?
+
+
+
+
+<xsl:param name="double.sided" select="0"></xsl:param>
+
+
+
+Description
+
+Double-sided documents are printed with a slightly wider margin
+on the binding edge of the page.
+
+FIXME: The current set of parameters does not take writing direction
+into account.
+
+
+
+
+
+
+body.margin.bottom
+length
+
+
+body.margin.bottom
+The bottom margin of the body text
+
+
+
+
+<xsl:param name="body.margin.bottom">0.5in</xsl:param>
+
+
+
+Description
+
+The body bottom margin is the distance from the last line of text
+in the page body to the bottom of the region-after.
+
+
+
+
+
+
+
+body.margin.top
+length
+
+
+body.margin.top
+To specify the size of the top margin of a page
+
+
+
+
+<xsl:param name="body.margin.top">0.5in</xsl:param>
+
+
+
+Description
+
+The body top margin is the distance from the top of the
+region-before to the first line of text in the page body.
+
+
+
+
+
+
+body.start.indent
+length
+
+
+body.start.indent
+The start-indent for the body text
+
+
+
+
+<xsl:param name="body.start.indent">
+ <xsl:choose>
+ <xsl:when test="$fop.extensions != 0">0pt</xsl:when>
+ <xsl:when test="$passivetex.extensions != 0">0pt</xsl:when>
+ <xsl:otherwise>4pc</xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+
+Description
+
+This parameter provides
+one means of indenting the body text relative to
+the left page margin.
+It is used in place of the
+title.margin.left for
+all XSL-FO processors except FOP.
+It enables support for side floats to appear
+in the indented margin area.
+
+This start-indent property is added to the fo:flow
+for certain page sequences. Which page-sequences it is
+applied to is determined by the template named
+set.flow.properties.
+By default, that template adds it to the flow
+for page-sequences using the body
+master-reference, as well as appendixes and prefaces.
+
+If this parameter is used, section titles should have
+a start-indent value of 0pt if they are to be
+outdented relative to the body text.
+
+
+If you are using FOP, then set this parameter to a zero
+width value and set the title.margin.left
+parameter to the negative value of the desired indent.
+
+
+See also body.end.indent and
+title.margin.left.
+
+
+
+
+
+
+
+body.end.indent
+length
+
+
+body.end.indent
+The end-indent for the body text
+
+
+
+
+<xsl:param name="body.end.indent">0pt</xsl:param>
+
+
+
+Description
+
+This end-indent property is added to the fo:flow
+for certain page sequences. Which page-sequences it is
+applied to is determined by the template named
+set.flow.properties.
+By default, that template adds it to the flow
+for page-sequences using the body
+master-reference, as well as appendixes and prefaces.
+
+
+See also body.start.indent.
+
+
+
+
+
+
+
+alignment
+ list
+ open
+ left
+ right
+ center
+ justify
+
+
+alignment
+Specify the default text alignment
+
+
+
+<xsl:param name="alignment">justify</xsl:param>
+
+
+Description
+
+The default text alignment is used for most body text.
+
+
+
+
+
+
+
+hyphenate
+list
+closed
+true
+false
+
+
+hyphenate
+Specify hyphenation behavior
+
+
+
+<xsl:param name="hyphenate">true</xsl:param>
+
+
+Description
+
+If true, words may be hyphenated. Otherwise, they may not.
+
+
+
+
+
+
+
+line-height
+string
+
+
+line-height
+Specify the line-height property
+
+
+
+
+<xsl:param name="line-height">normal</xsl:param>
+
+
+
+Description
+
+Sets the line-height property.
+
+
+
+
+
+
+column.count.back
+integer
+
+
+column.count.back
+Number of columns on back matter pages
+
+
+
+
+<xsl:param name="column.count.back" select="1"></xsl:param>
+
+
+
+Description
+
+Number of columns on back matter (appendix, glossary, etc.) pages.
+
+
+
+
+
+
+column.count.body
+integer
+
+
+column.count.body
+Number of columns on body pages
+
+
+
+
+<xsl:param name="column.count.body" select="1"></xsl:param>
+
+
+
+Description
+
+Number of columns on body pages.
+
+
+
+
+
+
+column.count.front
+integer
+
+
+column.count.front
+Number of columns on front matter pages
+
+
+
+
+<xsl:param name="column.count.front" select="1"></xsl:param>
+
+
+
+Description
+
+Number of columns on front matter (dedication, preface, etc.) pages.
+
+
+
+
+
+
+column.count.index
+integer
+
+
+column.count.index
+Number of columns on index pages
+
+
+
+
+<xsl:param name="column.count.index">2</xsl:param>
+
+
+
+Description
+
+Number of columns on index pages.
+
+
+
+
+
+
+column.count.lot
+integer
+
+
+column.count.lot
+Number of columns on a 'List-of-Titles' page
+
+
+
+
+<xsl:param name="column.count.lot" select="1"></xsl:param>
+
+
+
+Description
+
+Number of columns on a page sequence containing the Table of Contents,
+List of Figures, etc.
+
+
+
+
+
+
+column.count.titlepage
+integer
+
+
+column.count.titlepage
+Number of columns on a title page
+
+
+
+
+<xsl:param name="column.count.titlepage" select="1"></xsl:param>
+
+
+
+Description
+
+Number of columns on a title page
+
+
+
+
+
+
+column.gap.back
+length
+
+
+column.gap.back
+Gap between columns in back matter
+
+
+
+
+<xsl:param name="column.gap.back">12pt</xsl:param>
+
+
+
+Description
+
+Specifies the gap between columns in back matter (if
+column.count.back is greater than one).
+
+
+
+
+
+
+column.gap.body
+length
+
+
+column.gap.body
+Gap between columns in the body
+
+
+
+
+<xsl:param name="column.gap.body">12pt</xsl:param>
+
+
+
+Description
+
+Specifies the gap between columns in body matter (if
+column.count.body is greater than one).
+
+
+
+
+
+
+column.gap.front
+length
+
+
+column.gap.front
+Gap between columns in the front matter
+
+
+
+
+<xsl:param name="column.gap.front">12pt</xsl:param>
+
+
+
+Description
+
+Specifies the gap between columns in front matter (if
+column.count.front is greater than one).
+
+
+
+
+
+
+column.gap.index
+length
+
+
+column.gap.index
+Gap between columns in the index
+
+
+
+
+<xsl:param name="column.gap.index">12pt</xsl:param>
+
+
+
+Description
+
+Specifies the gap between columns in indexes (if
+column.count.index is greater than one).
+
+
+
+
+
+
+column.gap.lot
+length
+
+
+column.gap.lot
+Gap between columns on a 'List-of-Titles' page
+
+
+
+
+<xsl:param name="column.gap.lot">12pt</xsl:param>
+
+
+
+Description
+
+Specifies the gap between columns on 'List-of-Titles' pages (if
+column.count.lot is greater than one).
+
+
+
+
+
+
+column.gap.titlepage
+length
+
+
+column.gap.titlepage
+Gap between columns on title pages
+
+
+
+
+<xsl:param name="column.gap.titlepage">12pt</xsl:param>
+
+
+
+Description
+
+Specifies the gap between columns on title pages (if
+column.count.titlepage is greater than one).
+
+
+
+
+
+
+
+region.after.extent
+length
+
+
+region.after.extent
+Specifies the height of the footer.
+
+
+
+
+<xsl:param name="region.after.extent">0.4in</xsl:param>
+
+
+
+Description
+
+The region after extent is the height of the area where footers
+are printed.
+
+
+
+
+
+
+
+region.before.extent
+length
+
+
+region.before.extent
+Specifies the height of the header
+
+
+
+
+<xsl:param name="region.before.extent">0.4in</xsl:param>
+
+
+
+Description
+
+The region before extent is the height of the area where headers
+are printed.
+
+
+
+
+
+
+
+default.units
+list
+cm
+mm
+in
+pt
+pc
+px
+em
+
+
+default.units
+Default units for an unqualified dimension
+
+
+
+
+<xsl:param name="default.units">pt</xsl:param>
+
+
+
+Description
+
+If an unqualified dimension is encountered (for example, in a
+graphic width), the default-units will be used for the
+units. Unqualified dimensions are not allowed in XSL Formatting Objects.
+
+
+
+
+
+
+
+normal.para.spacing
+attribute set
+
+
+normal.para.spacing
+What space do you want between normal paragraphs
+
+
+
+<xsl:attribute-set name="normal.para.spacing">
+ <xsl:attribute name="space-before.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-before.minimum">0.8em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">1.2em</xsl:attribute>
+</xsl:attribute-set>
+
+Description
+Specify the spacing required between normal paragraphs
+
+
+
+
+
+body.font.master
+ number
+
+
+body.font.master
+Specifies the default point size for body text
+
+
+
+
+<xsl:param name="body.font.master">10</xsl:param>
+
+
+
+Description
+
+The body font size is specified in two parameters
+(body.font.master and body.font.size)
+so that math can be performed on the font size by XSLT.
+
+
+
+
+
+
+
+body.font.size
+length
+
+
+body.font.size
+Specifies the default font size for body text
+
+
+
+
+<xsl:param name="body.font.size">
+ <xsl:value-of select="$body.font.master"></xsl:value-of><xsl:text>pt</xsl:text>
+</xsl:param>
+
+
+Description
+
+The body font size is specified in two parameters
+(body.font.master and body.font.size)
+so that math can be performed on the font size by XSLT.
+
+
+
+
+
+
+
+footnote.font.size
+length
+
+
+footnote.font.size
+The font size for footnotes
+
+
+
+<xsl:param name="footnote.font.size">
+ <xsl:value-of select="$body.font.master * 0.8"></xsl:value-of><xsl:text>pt</xsl:text>
+</xsl:param>
+
+
+Description
+
+The footnote font size is used for...footnotes!
+
+
+
+
+
+
+
+title.margin.left
+length
+
+
+title.margin.left
+Adjust the left margin for titles
+
+
+
+
+<xsl:param name="title.margin.left">
+ <xsl:choose>
+ <xsl:when test="$fop.extensions != 0">-4pc</xsl:when>
+ <xsl:when test="$passivetex.extensions != 0">0pt</xsl:when>
+ <xsl:otherwise>0pt</xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+
+Description
+
+This parameter provides
+one means of adjusting the left margin for titles.
+The left margin of the body region
+is calculated to include this space,
+and titles are outdented to the left by this amount,
+effectively leaving titles at the left margin
+and the body text indented.
+Currently this method is only used for FOP because
+it cannot properly use the body.start.indent
+parameter.
+the relative
+
+
+The default value for FOP is -4pc, which means the
+body text is indented 4 picas relative to
+the titles.
+The default value for other processors is 0pt, and
+the body indent is provided by the body.start.indent
+parameter.
+
+
+If you set the value to zero, be sure to still include
+a unit indicator such as 0pt, or
+the FO processor will report errors.
+
+
+This parameter must be set to 0pt if the
+passivetex.extensions
+parameter is nonzero because PassiveTeX cannot handle
+the math expression with negative values
+used to calculate the indents.
+
+
+
+
+
+
+
+draft.mode
+list
+no
+yes
+maybe
+
+
+draft.mode
+Select draft mode
+
+
+
+
+<xsl:param name="draft.mode">maybe</xsl:param>
+
+
+
+Description
+
+Selects draft mode. If draft.mode is
+yes, the entire document will be treated
+as a draft. If it is no, the entire document
+will be treated as a final copy. If it is maybe,
+individual sections will be treated as draft or final independently, depending
+on how their status attribute is set.
+
+
+
+
+
+
+
+draft.watermark.image
+uri
+
+
+draft.watermark.image
+The URI of the image to be used for draft watermarks
+
+
+
+
+<xsl:param name="draft.watermark.image">http://docbook.sourceforge.net/release/images/draft.png</xsl:param>
+
+
+
+Description
+
+The image to be used for draft watermarks.
+
+
+
+
+
+
+headers.on.blank.pages
+boolean
+
+
+headers.on.blank.pages
+Put headers on blank pages?
+
+
+
+
+<xsl:param name="headers.on.blank.pages" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, headers will be placed on blank pages.
+
+
+
+
+
+
+footers.on.blank.pages
+boolean
+
+
+footers.on.blank.pages
+Put footers on blank pages?
+
+
+
+
+<xsl:param name="footers.on.blank.pages" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, footers will be placed on blank pages.
+
+
+
+
+
+
+header.rule
+boolean
+
+
+header.rule
+Rule under headers?
+
+
+
+
+<xsl:param name="header.rule" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, a rule will be drawn below the page headers.
+
+
+
+
+
+
+footer.rule
+boolean
+
+
+footer.rule
+Rule over footers?
+
+
+
+
+<xsl:param name="footer.rule" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, a rule will be drawn above the page footers.
+
+
+
+
+
+
+header.column.widths
+string
+
+
+header.column.widths
+Specify relative widths of header areas
+
+
+
+<xsl:param name="header.column.widths">1 1 1</xsl:param>
+
+
+Description
+
+Page headers in print output use a three column table
+to position text at the left, center, and right side of
+the header on the page.
+This parameter lets you specify the relative sizes of the
+three columns. The default value is
+"1 1 1".
+
+The parameter value must be three numbers, separated
+by white space. The first number represents the relative
+width of the left header for
+single-sided output, or the inside header for
+double-sided output. The second number is the relative
+width of the center header. The third number is the
+relative width of the right header for
+single-sided output, or the outside header for
+double-sided output.
+
+
+The numbers are used to specify the column widths
+for the table that makes up the header area.
+In the FO output, this looks like:
+
+
+
+<fo:table-column column-number="1"
+ column-width="proportional-column-width(1)"/>
+
+
+
+The proportional-column-width()
+function computes a column width by dividing its
+argument by the total of the arguments for all the columns, and
+then multiplying the result by the width of the whole table
+(assuming all the column specs use the function).
+Its argument can be any positive integer or floating point number.
+Zero is an acceptable value, although some FO processors
+may warn about it, in which case using a very small number might
+be more satisfactory.
+
+
+For example, the value "1 2 1" means the center
+header should have twice the width of the other areas.
+A value of "0 0 1" means the entire header area
+is reserved for the right (or outside) header text.
+Note that to keep the center area centered on
+the page, the left and right values must be
+the same. A specification like "1 2 3" means the
+center area is no longer centered on the page
+since the right area is three times the width of the left area.
+
+
+
+
+
+
+
+footer.column.widths
+string
+
+
+footer.column.widths
+Specify relative widths of footer areas
+
+
+
+<xsl:param name="footer.column.widths">1 1 1</xsl:param>
+
+
+Description
+
+Page footers in print output use a three column table
+to position text at the left, center, and right side of
+the footer on the page.
+This parameter lets you specify the relative sizes of the
+three columns. The default value is
+"1 1 1".
+
+The parameter value must be three numbers, separated
+by white space. The first number represents the relative
+width of the left footer for
+single-sided output, or the inside footer for
+double-sided output. The second number is the relative
+width of the center footer. The third number is the
+relative width of the right footer for
+single-sided output, or the outside footer for
+double-sided output.
+
+
+The numbers are used to specify the column widths
+for the table that makes up the footer area.
+In the FO output, this looks like:
+
+
+
+<fo:table-column column-number="1"
+ column-width="proportional-column-width(1)"/>
+
+
+
+The proportional-column-width()
+function computes a column width by dividing its
+argument by the total of the arguments for all the columns, and
+then multiplying the result by the width of the whole table
+(assuming all the column specs use the function).
+Its argument can be any positive integer or floating point number.
+Zero is an acceptable value, although some FO processors
+may warn about it, in which case using a very small number might
+be more satisfactory.
+
+
+For example, the value "1 2 1" means the center
+footer should have twice the width of the other areas.
+A value of "0 0 1" means the entire footer area
+is reserved for the right (or outside) footer text.
+Note that to keep the center area centered on
+the page, the left and right values must be
+the same. A specification like "1 2 3" means the
+center area is no longer centered on the page
+since the right area is three times the width of the left area.
+
+
+
+
+
+
+
+header.table.properties
+attribute set
+
+
+header.table.properties
+Apply properties to the header layout table
+
+
+
+
+<xsl:attribute-set name="header.table.properties">
+ <xsl:attribute name="table-layout">fixed</xsl:attribute>
+ <xsl:attribute name="width">100%</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Properties applied to the table that lays out the page header.
+
+
+
+
+
+
+header.table.height
+length
+
+
+header.table.height
+Specify the minimum height of the table containing the running page headers
+
+
+
+<xsl:param name="header.table.height">14pt</xsl:param>
+
+
+Description
+
+Page headers in print output use a three column table
+to position text at the left, center, and right side of
+the header on the page.
+This parameter lets you specify the minimum height
+of the single row in the table.
+Since this specifies only the minimum height,
+the table should automatically grow to fit taller content.
+The default value is "14pt".
+
+
+
+
+
+
+footer.table.properties
+attribute set
+
+
+footer.table.properties
+Apply properties to the footer layout table
+
+
+
+
+<xsl:attribute-set name="footer.table.properties">
+ <xsl:attribute name="table-layout">fixed</xsl:attribute>
+ <xsl:attribute name="width">100%</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Properties applied to the table that lays out the page footer.
+
+
+
+
+
+
+footer.table.height
+length
+
+
+footer.table.height
+Specify the minimum height of the table containing the running page footers
+
+
+
+<xsl:param name="footer.table.height">14pt</xsl:param>
+
+
+Description
+
+Page footers in print output use a three column table
+to position text at the left, center, and right side of
+the footer on the page.
+This parameter lets you specify the minimum height
+of the single row in the table.
+Since this specifies only the minimum height,
+the table should automatically grow to fit taller content.
+The default value is "14pt".
+
+
+
+
+
+
+header.content.properties
+attribute set
+
+
+header.content.properties
+Properties of page header content
+
+
+
+
+<xsl:attribute-set name="header.content.properties">
+ <xsl:attribute name="font-family">
+ <xsl:value-of select="$body.fontset"></xsl:value-of>
+ </xsl:attribute>
+ <xsl:attribute name="margin-left">
+ <xsl:value-of select="$title.margin.left"></xsl:value-of>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Properties of page header content.
+
+
+
+
+
+
+footer.content.properties
+attribute set
+
+
+footer.content.properties
+Properties of page footer content
+
+
+
+
+<xsl:attribute-set name="footer.content.properties">
+ <xsl:attribute name="font-family">
+ <xsl:value-of select="$body.fontset"></xsl:value-of>
+ </xsl:attribute>
+ <xsl:attribute name="margin-left">
+ <xsl:value-of select="$title.margin.left"></xsl:value-of>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Properties of page footer content.
+
+
+
+
+
+
+marker.section.level
+integer
+
+
+marker.section.level
+Control depth of sections shown in running headers or footers
+
+
+
+
+<xsl:param name="marker.section.level">2</xsl:param>
+
+
+
+Description
+
+The marker.section.level parameter
+controls the depth of section levels that may be displayed
+in running headers and footers. For example, if the value
+is 2 (the default), then titles from sect1 and
+sect2 or equivalent section
+elements are candidates for use in running headers and
+footers.
+
+Each candidate title is marked in the FO output with a
+<fo:marker marker-class-name="section.head.marker">
+element.
+
+In order for such titles to appear in headers
+or footers, the header.content
+or footer.content template
+must be customized to retrieve the marker using
+an output element such as:
+
+
+<fo:retrieve-marker retrieve-class-name="section.head.marker"
+ retrieve-position="first-including-carryover"
+ retrieve-boundary="page-sequence"/>
+
+
+
+
+
+
+
+Font Families
+
+
+body.font.family
+list
+open
+serif
+sans-serif
+monospace
+
+
+body.font.family
+The default font family for body text
+
+
+
+
+<xsl:param name="body.font.family">serif</xsl:param>
+
+
+
+Description
+
+The body font family is the default font used for text in the page body.
+
+
+
+
+
+
+
+dingbat.font.family
+list
+open
+serif
+sans-serif
+monospace
+
+
+dingbat.font.family
+The font family for copyright, quotes, and other symbols
+
+
+
+
+<xsl:param name="dingbat.font.family">serif</xsl:param>
+
+
+
+Description
+
+The dingbat font family is used for dingbats. If it is defined
+as the empty string, no font change is effected around dingbats.
+
+
+
+
+
+
+
+monospace.font.family
+string
+
+
+monospace.font.family
+The default font family for monospace environments
+
+
+
+
+<xsl:param name="monospace.font.family">monospace</xsl:param>
+
+
+
+Description
+
+The monospace font family is used for verbatim environments
+(program listings, screens, etc.).
+
+
+
+
+
+
+
+sans.font.family
+string
+
+
+sans.font.family
+The default sans-serif font family
+
+
+
+
+<xsl:param name="sans.font.family">sans-serif</xsl:param>
+
+
+
+Description
+
+The default sans-serif font family. At the present, this isn't
+actually used by the stylesheets.
+
+
+
+
+
+
+
+title.font.family
+list
+open
+serif
+sans-serif
+monospace
+
+
+title.font.family
+The default font family for titles
+
+
+
+
+<xsl:param name="title.font.family">sans-serif</xsl:param>
+
+
+
+Description
+
+The title font family is used for titles (chapter, section, figure,
+etc.)
+
+
+
+
+
+
+
+symbol.font.family
+list
+open
+serif
+sans-serif
+monospace
+
+
+symbol.font.family
+The font families to be searched for symbols outside
+ of the body font
+
+
+
+
+<xsl:param name="symbol.font.family">Symbol,ZapfDingbats</xsl:param>
+
+
+
+Description
+
+A typical body or title font does not contain all
+the character glyphs that DocBook supports. This parameter
+specifies additional fonts that should be searched for
+special characters not in the normal font.
+These symbol font names are automatically appended
+to the body or title font family name when fonts
+are specified in a
+font-family
+property in the FO output.
+
+The symbol font names should be entered as a
+comma-separated list. The default value is
+Symbol,ZapfDingbats.
+
+
+
+
+
+
+Property Sets
+
+
+formal.object.properties
+attribute set
+
+
+formal.object.properties
+Properties associated with a formal object such as a figure, or other component that has a title
+
+
+
+
+<xsl:attribute-set name="formal.object.properties">
+ <xsl:attribute name="space-before.minimum">0.5em</xsl:attribute>
+ <xsl:attribute name="space-before.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">2em</xsl:attribute>
+ <xsl:attribute name="space-after.minimum">0.5em</xsl:attribute>
+ <xsl:attribute name="space-after.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-after.maximum">2em</xsl:attribute>
+ <xsl:attribute name="keep-together.within-column">always</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The styling for formal objects in docbook. Specify the spacing
+before and after the object.
+
+
+
+
+
+
+formal.title.properties
+attribute set
+
+
+formal.title.properties
+Style the title element of formal object such as a figure.
+
+
+
+
+<xsl:attribute-set name="formal.title.properties" use-attribute-sets="normal.para.spacing">
+ <xsl:attribute name="font-weight">bold</xsl:attribute>
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master * 1.2"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+ <xsl:attribute name="hyphenate">false</xsl:attribute>
+ <xsl:attribute name="space-after.minimum">0.4em</xsl:attribute>
+ <xsl:attribute name="space-after.optimum">0.6em</xsl:attribute>
+ <xsl:attribute name="space-after.maximum">0.8em</xsl:attribute>
+</xsl:attribute-set>
+
+
+Description
+Specify how the title should be styled. Specify the font size and weight of the title of the formal object.
+
+
+
+
+
+informal.object.properties
+attribute set
+
+
+informal.object.properties
+Properties associated with an informal (untitled) object, such as an informalfigure
+
+
+
+<xsl:attribute-set name="informal.object.properties">
+ <xsl:attribute name="space-before.minimum">0.5em</xsl:attribute>
+ <xsl:attribute name="space-before.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">2em</xsl:attribute>
+ <xsl:attribute name="space-after.minimum">0.5em</xsl:attribute>
+ <xsl:attribute name="space-after.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-after.maximum">2em</xsl:attribute>
+</xsl:attribute-set>
+
+Description
+The styling for informal objects in docbook. Specify the spacing before and after the object.
+
+
+
+
+
+monospace.properties
+attribute set
+
+
+monospace.properties
+Properties of monospaced content
+
+
+
+
+<xsl:attribute-set name="monospace.properties">
+ <xsl:attribute name="font-family">
+ <xsl:value-of select="$monospace.font.family"></xsl:value-of>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Specifies the font name for monospaced output. This property set
+used to set the font-size as well, but that doesn't work very well
+when different fonts are used (as they are in titles and paragraphs,
+for example).
+
+If you want to set the font-size in a customization layer, it's
+probably going to be more appropriate to set font-size-adjust, if your
+formatter supports it.
+
+
+
+
+
+
+verbatim.properties
+attribute set
+
+
+verbatim.properties
+Properties associated with verbatim text
+
+
+
+
+<xsl:attribute-set name="verbatim.properties">
+ <xsl:attribute name="space-before.minimum">0.8em</xsl:attribute>
+ <xsl:attribute name="space-before.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">1.2em</xsl:attribute>
+ <xsl:attribute name="space-after.minimum">0.8em</xsl:attribute>
+ <xsl:attribute name="space-after.optimum">1em</xsl:attribute>
+ <xsl:attribute name="space-after.maximum">1.2em</xsl:attribute>
+ <xsl:attribute name="hyphenate">false</xsl:attribute>
+ <xsl:attribute name="wrap-option">no-wrap</xsl:attribute>
+ <xsl:attribute name="white-space-collapse">false</xsl:attribute>
+ <xsl:attribute name="white-space-treatment">preserve</xsl:attribute>
+ <xsl:attribute name="linefeed-treatment">preserve</xsl:attribute>
+ <xsl:attribute name="text-align">start</xsl:attribute>
+</xsl:attribute-set>
+
+
+Description
+This attribute set is used on all verbatim environments.
+
+
+
+
+
+
+monospace.verbatim.properties
+attribute set
+
+
+monospace.verbatim.properties
+What font and size do you want for monospaced content?
+
+
+
+
+<xsl:attribute-set name="monospace.verbatim.properties" use-attribute-sets="verbatim.properties monospace.properties">
+ <xsl:attribute name="text-align">start</xsl:attribute>
+ <xsl:attribute name="wrap-option">no-wrap</xsl:attribute>
+</xsl:attribute-set>
+
+
+Description
+Specify the font name and size you want for monospaced output
+
+
+
+
+
+sidebar.properties
+attribute set
+
+
+sidebar.properties
+Attribute set for sidebar properties
+
+
+
+
+<xsl:attribute-set name="sidebar.properties" use-attribute-sets="formal.object.properties">
+ <xsl:attribute name="border-style">solid</xsl:attribute>
+ <xsl:attribute name="border-width">1pt</xsl:attribute>
+ <xsl:attribute name="border-color">black</xsl:attribute>
+ <xsl:attribute name="background-color">#DDDDDD</xsl:attribute>
+ <xsl:attribute name="padding-left">12pt</xsl:attribute>
+ <xsl:attribute name="padding-right">12pt</xsl:attribute>
+ <xsl:attribute name="padding-top">6pt</xsl:attribute>
+ <xsl:attribute name="padding-bottom">6pt</xsl:attribute>
+ <xsl:attribute name="margin-left">0pt</xsl:attribute>
+ <xsl:attribute name="margin-right">0pt</xsl:attribute>
+<!--
+ <xsl:attribute name="margin-top">6pt</xsl:attribute>
+ <xsl:attribute name="margin-bottom">6pt</xsl:attribute>
+-->
+</xsl:attribute-set>
+
+
+
+Description
+
+The styling for sidebars.
+
+
+
+
+
+
+sidebar.title.properties
+attribute set
+
+
+sidebar.title.properties
+Attribute set for sidebar titles
+
+
+
+
+<xsl:attribute-set name="sidebar.title.properties">
+ <xsl:attribute name="font-weight">bold</xsl:attribute>
+ <xsl:attribute name="hyphenate">false</xsl:attribute>
+ <xsl:attribute name="text-align">start</xsl:attribute>
+ <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The styling for sidebars titles.
+
+
+
+
+
+
+sidebar.float.type
+list
+none
+before
+left
+start
+right
+end
+inside
+outside
+
+
+sidebar.float.type
+Select type of float for sidebar elements
+
+
+
+
+<xsl:param name="sidebar.float.type">none</xsl:param>
+
+
+
+Description
+
+Selects the type of float for sidebar elements.
+
+
+
+If sidebar.float.type is
+none, then
+no float is used.
+
+
+
+If sidebar.float.type is
+before, then
+the float appears at the top of the page. On some processors,
+that may be the next page rather than the current page.
+
+
+
+If sidebar.float.type is
+left or
+start, then
+a left side float is used.
+
+
+
+If sidebar.float.type is
+right or
+end, then
+a right side float is used.
+
+
+
+If your XSL-FO processor supports floats positioned on the
+inside or
+outside
+of double-sided pages, then you have those two
+options for side floats as well.
+
+
+
+
+
+
+
+
+
+sidebar.float.width
+length
+
+
+sidebar.float.width
+Set the default width for sidebars
+
+
+
+
+<xsl:param name="sidebar.float.width">1in</xsl:param>
+
+
+
+Description
+
+Sets the default width for sidebars when used as a side float.
+The width determines the degree to which the sidebar block intrudes into
+the text area.
+
+If sidebar.float.type is
+before or
+none, then
+this parameter is ignored.
+
+
+
+
+
+
+
+margin.note.properties
+attribute set
+
+
+margin.note.properties
+Attribute set for margin.note properties
+
+
+
+
+<xsl:attribute-set name="margin.note.properties">
+ <xsl:attribute name="font-size">90%</xsl:attribute>
+ <xsl:attribute name="text-align">start</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The styling for margin notes.
+By default, margin notes are not implemented for any
+element. A stylesheet customization is needed to make
+use of this attribute-set.
+
+You can use a template named floater
+to create the customization.
+That template can create side floats by specifying the
+content and characteristics as template parameters.
+
+
+For example:
+<xsl:template match="para[@role='marginnote']">
+ <xsl:call-template name="floater">
+ <xsl:with-param name="position">
+ <xsl:value-of select="$margin.note.float.type"/>
+ </xsl:with-param>
+ <xsl:with-param name="width">
+ <xsl:value-of select="$margin.note.width"/>
+ </xsl:with-param>
+ <xsl:with-param name="content">
+ <xsl:apply-imports/>
+ </xsl:with-param>
+ </xsl:call-template>
+</xsl:template>
+
+
+
+
+
+
+margin.note.title.properties
+attribute set
+
+
+margin.note.title.properties
+Attribute set for margin note titles
+
+
+
+
+<xsl:attribute-set name="margin.note.title.properties">
+ <xsl:attribute name="font-weight">bold</xsl:attribute>
+ <xsl:attribute name="hyphenate">false</xsl:attribute>
+ <xsl:attribute name="text-align">start</xsl:attribute>
+ <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The styling for margin note titles.
+
+
+
+
+
+
+margin.note.float.type
+list
+none
+before
+left
+start
+right
+end
+inside
+outside
+
+
+margin.note.float.type
+Select type of float for margin note customizations
+
+
+
+
+<xsl:param name="margin.note.float.type">none</xsl:param>
+
+
+
+Description
+
+Selects the type of float for margin notes.
+DocBook does not define a margin note element, so this
+feature must be implemented as a customization of the stylesheet.
+See margin.note.properties for
+an example.
+
+
+
+If margin.note.float.type is
+none, then
+no float is used.
+
+
+
+If margin.note.float.type is
+before, then
+the float appears at the top of the page. On some processors,
+that may be the next page rather than the current page.
+
+
+
+If margin.note.float.type is
+left or
+start, then
+a left side float is used.
+
+
+
+If margin.note.float.type is
+right or
+end, then
+a right side float is used.
+
+
+
+If your XSL-FO processor supports floats positioned on the
+inside or
+outside
+of double-sided pages, then you have those two
+options for side floats as well.
+
+
+
+
+
+
+
+
+
+margin.note.width
+length
+
+
+margin.note.width
+Set the default width for margin notes
+
+
+
+
+<xsl:param name="margin.note.width">1in</xsl:param>
+
+
+
+Description
+
+Sets the default width for margin notes when used as a side
+float. The width determines the degree to which the margin note block
+intrudes into the text area.
+
+If margin.note.float.type is
+before or
+none, then
+this parameter is ignored.
+
+
+
+
+
+
+
+component.title.properties
+attribute set
+
+
+component.title.properties
+Properties for component titles
+
+
+
+
+<xsl:attribute-set name="component.title.properties">
+ <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
+ <xsl:attribute name="space-before.optimum"><xsl:value-of select="concat($body.font.master, 'pt')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="space-before.minimum"><xsl:value-of select="concat($body.font.master, 'pt * 0.8')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="space-before.maximum"><xsl:value-of select="concat($body.font.master, 'pt * 1.2')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="hyphenate">false</xsl:attribute>
+ <xsl:attribute name="text-align">
+ <xsl:choose>
+ <xsl:when test="((parent::article | parent::articleinfo | parent::info/parent::article) and not(ancestor::book) and not(self::bibliography)) or (parent::slides | parent::slidesinfo)">center</xsl:when>
+ <xsl:otherwise>left</xsl:otherwise>
+ </xsl:choose>
+ </xsl:attribute>
+ <xsl:attribute name="start-indent"><xsl:value-of select="$title.margin.left"></xsl:value-of></xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties common to all component titles.
+
+
+
+
+
+
+component.titlepage.properties
+attribute set
+
+
+component.titlepage.properties
+Properties for component titlepages
+
+
+
+
+<xsl:attribute-set name="component.titlepage.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties that are applied to the outer block containing
+all the component title page information.
+Its main use is to set a span="all"
+property on the block that is a direct child of the flow.
+
+This attribute-set is empty by default.
+
+
+
+
+
+
+section.title.properties
+attribute set
+
+
+section.title.properties
+Properties for section titles
+
+
+
+
+<xsl:attribute-set name="section.title.properties">
+ <xsl:attribute name="font-family">
+ <xsl:value-of select="$title.font.family"></xsl:value-of>
+ </xsl:attribute>
+ <xsl:attribute name="font-weight">bold</xsl:attribute>
+ <!-- font size is calculated dynamically by section.heading template -->
+ <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
+ <xsl:attribute name="space-before.minimum">0.8em</xsl:attribute>
+ <xsl:attribute name="space-before.optimum">1.0em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">1.2em</xsl:attribute>
+ <xsl:attribute name="text-align">left</xsl:attribute>
+ <xsl:attribute name="start-indent"><xsl:value-of select="$title.margin.left"></xsl:value-of></xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties common to all section titles.
+
+
+
+
+
+
+section.title.level1.properties
+attribute set
+
+
+section.title.level1.properties
+Properties for level-1 section titles
+
+
+
+
+<xsl:attribute-set name="section.title.level1.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master * 2.0736"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-1 section titles.
+
+
+
+
+
+
+
+section.title.level2.properties
+attribute set
+
+
+section.title.level2.properties
+Properties for level-2 section titles
+
+
+
+
+<xsl:attribute-set name="section.title.level2.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master * 1.728"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-2 section titles.
+
+
+
+
+
+
+section.title.level3.properties
+attribute set
+
+
+section.title.level3.properties
+Properties for level-3 section titles
+
+
+
+
+<xsl:attribute-set name="section.title.level3.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master * 1.44"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-3 section titles.
+
+
+
+
+
+
+section.title.level4.properties
+attribute set
+
+
+section.title.level4.properties
+Properties for level-4 section titles
+
+
+
+
+<xsl:attribute-set name="section.title.level4.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master * 1.2"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-4 section titles.
+
+
+
+
+
+
+section.title.level5.properties
+attribute set
+
+
+section.title.level5.properties
+Properties for level-5 section titles
+
+
+
+
+<xsl:attribute-set name="section.title.level5.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-5 section titles.
+
+
+
+
+
+
+section.title.level6.properties
+attribute set
+
+
+section.title.level6.properties
+Properties for level-6 section titles
+
+
+
+
+<xsl:attribute-set name="section.title.level6.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-6 section titles. This property set is actually
+used for all titles below level 5.
+
+
+
+
+
+
+section.properties
+attribute set
+
+
+section.properties
+Properties for all section levels
+
+
+
+
+<xsl:attribute-set name="section.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties that apply to the containing
+block of all section levels, and therefore apply to
+the whole section.
+This attribute set is inherited by the
+more specific attribute sets such as
+section.level1.properties.
+The default is empty.
+
+
+
+
+
+
+
+section.level1.properties
+attribute set
+
+
+section.level1.properties
+Properties for level-1 sections
+
+
+
+
+<xsl:attribute-set name="section.level1.properties" use-attribute-sets="section.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties that apply to the containing
+block of a level-1 section, and therefore apply to
+the whole section. This includes sect1
+elements and section elements at level 1.
+
+
+For example, you could start each level-1 section on
+a new page by using:
+<xsl:attribute-set name="section.level1.properties">
+ <xsl:attribute name="break-before">page</xsl:attribute>
+</xsl:attribute-set>
+
+
+This attribute set inherits attributes from the
+general section.properties attribute set.
+
+
+
+
+
+
+
+section.level2.properties
+attribute set
+
+
+section.level2.properties
+Properties for level-2 sections
+
+
+
+
+<xsl:attribute-set name="section.level2.properties" use-attribute-sets="section.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties that apply to the containing
+block of a level-2 section, and therefore apply to
+the whole section. This includes sect2
+elements and section elements at level 2.
+
+
+For example, you could start each level-2 section on
+a new page by using:
+<xsl:attribute-set name="section.level2.properties">
+ <xsl:attribute name="break-before">page</xsl:attribute>
+</xsl:attribute-set>
+
+
+This attribute set inherits attributes from the
+general section.properties attribute set.
+
+
+
+
+
+
+
+section.level3.properties
+attribute set
+
+
+section.level3.properties
+Properties for level-3 sections
+
+
+
+
+<xsl:attribute-set name="section.level3.properties" use-attribute-sets="section.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties that apply to the containing
+block of a level-3 section, and therefore apply to
+the whole section. This includes sect3
+elements and section elements at level 3.
+
+
+For example, you could start each level-3 section on
+a new page by using:
+<xsl:attribute-set name="section.level3.properties">
+ <xsl:attribute name="break-before">page</xsl:attribute>
+</xsl:attribute-set>
+
+
+This attribute set inherits attributes from the
+general section.properties attribute set.
+
+
+
+
+
+
+
+section.level4.properties
+attribute set
+
+
+section.level4.properties
+Properties for level-4 sections
+
+
+
+
+<xsl:attribute-set name="section.level4.properties" use-attribute-sets="section.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties that apply to the containing
+block of a level-4 section, and therefore apply to
+the whole section. This includes sect4
+elements and section elements at level 4.
+
+
+For example, you could start each level-4 section on
+a new page by using:
+<xsl:attribute-set name="section.level4.properties">
+ <xsl:attribute name="break-before">page</xsl:attribute>
+</xsl:attribute-set>
+
+
+This attribute set inherits attributes from the
+general section.properties attribute set.
+
+
+
+
+
+
+
+section.level5.properties
+attribute set
+
+
+section.level5.properties
+Properties for level-5 sections
+
+
+
+
+<xsl:attribute-set name="section.level5.properties" use-attribute-sets="section.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties that apply to the containing
+block of a level-5 section, and therefore apply to
+the whole section. This includes sect5
+elements and section elements at level 5.
+
+
+For example, you could start each level-5 section on
+a new page by using:
+<xsl:attribute-set name="section.level5.properties">
+ <xsl:attribute name="break-before">page</xsl:attribute>
+</xsl:attribute-set>
+
+
+This attribute set inherits attributes from the
+general section.properties attribute set.
+
+
+
+
+
+
+
+section.level6.properties
+attribute set
+
+
+section.level6.properties
+Properties for level-6 sections
+
+
+
+
+<xsl:attribute-set name="section.level6.properties" use-attribute-sets="section.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties that apply to the containing
+block of a level 6 or lower section, and therefore apply to
+the whole section. This includes
+section elements at level 6 and lower.
+
+
+For example, you could start each level-6 section on
+a new page by using:
+<xsl:attribute-set name="section.level6.properties">
+ <xsl:attribute name="break-before">page</xsl:attribute>
+</xsl:attribute-set>
+
+
+This attribute set inherits attributes from the
+general section.properties attribute set.
+
+
+
+
+
+
+
+figure.properties
+attribute set
+
+
+figure.properties
+Properties associated with a figure
+
+
+
+
+<xsl:attribute-set name="figure.properties" use-attribute-sets="formal.object.properties"></xsl:attribute-set>
+
+
+
+Description
+
+The styling for figures.
+
+
+
+
+
+
+example.properties
+attribute set
+
+
+example.properties
+Properties associated with a example
+
+
+
+
+<xsl:attribute-set name="example.properties" use-attribute-sets="formal.object.properties"></xsl:attribute-set>
+
+
+
+Description
+
+The styling for examples.
+
+
+
+
+
+
+equation.properties
+attribute set
+
+
+equation.properties
+Properties associated with a equation
+
+
+
+
+<xsl:attribute-set name="equation.properties" use-attribute-sets="formal.object.properties"></xsl:attribute-set>
+
+
+
+Description
+
+The styling for equations.
+
+
+
+
+
+
+table.properties
+attribute set
+
+
+table.properties
+Properties associated with the block surrounding a table
+
+
+
+
+<xsl:attribute-set name="table.properties" use-attribute-sets="formal.object.properties">
+ <xsl:attribute name="keep-together.within-column">auto</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Block styling properties for tables. This parameter should really
+have been called table.block.properties or something
+like that, but we’re leaving it to avoid backwards-compatibility
+problems.
+
+See also table.table.properties.
+
+
+
+
+
+
+informalfigure.properties
+attribute set
+
+
+informalfigure.properties
+Properties associated with an informalfigure
+
+
+
+
+<xsl:attribute-set name="informalfigure.properties" use-attribute-sets="informal.object.properties"></xsl:attribute-set>
+
+
+
+Description
+
+The styling for informalfigures.
+
+
+
+
+
+
+informalexample.properties
+attribute set
+
+
+informalexample.properties
+Properties associated with an informalexample
+
+
+
+
+<xsl:attribute-set name="informalexample.properties" use-attribute-sets="informal.object.properties"></xsl:attribute-set>
+
+
+
+Description
+
+The styling for informalexamples.
+
+
+
+
+
+
+informalequation.properties
+attribute set
+
+
+informalequation.properties
+Properties associated with an informalequation
+
+
+
+
+<xsl:attribute-set name="informalequation.properties" use-attribute-sets="informal.object.properties"></xsl:attribute-set>
+
+
+
+Description
+
+The styling for informalequations.
+
+
+
+
+
+
+informaltable.properties
+attribute set
+
+
+informaltable.properties
+Properties associated with the block surrounding an informaltable
+
+
+
+
+<xsl:attribute-set name="informaltable.properties" use-attribute-sets="informal.object.properties"></xsl:attribute-set>
+
+
+
+Description
+
+Block styling properties for informaltables. This parameter should really
+have been called informaltable.block.properties or something
+like that, but we’re leaving it to avoid backwards-compatibility
+problems.
+
+See also table.table.properties.
+
+
+
+
+
+
+procedure.properties
+attribute set
+
+
+procedure.properties
+Properties associated with a procedure
+
+
+
+
+<xsl:attribute-set name="procedure.properties" use-attribute-sets="formal.object.properties">
+ <xsl:attribute name="keep-together.within-column">auto</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The styling for procedures.
+
+
+
+
+
+
+root.properties
+attribute set
+
+
+root.properties
+The properties of the fo:root element
+
+
+
+
+<xsl:attribute-set name="root.properties">
+ <xsl:attribute name="font-family">
+ <xsl:value-of select="$body.fontset"></xsl:value-of>
+ </xsl:attribute>
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.size"></xsl:value-of>
+ </xsl:attribute>
+ <xsl:attribute name="text-align">
+ <xsl:value-of select="$alignment"></xsl:value-of>
+ </xsl:attribute>
+ <xsl:attribute name="line-height">
+ <xsl:value-of select="$line-height"></xsl:value-of>
+ </xsl:attribute>
+ <xsl:attribute name="font-selection-strategy">character-by-character</xsl:attribute>
+ <xsl:attribute name="line-height-shift-adjustment">disregard-shifts</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+This property set is used on the fo:root element of
+an FO file. It defines a set of default, global parameters.
+
+
+
+
+
+
+qanda.title.properties
+attribute set
+
+
+qanda.title.properties
+Properties for qanda set titles
+
+
+
+
+<xsl:attribute-set name="qanda.title.properties">
+ <xsl:attribute name="font-family">
+ <xsl:value-of select="$title.font.family"></xsl:value-of>
+ </xsl:attribute>
+ <xsl:attribute name="font-weight">bold</xsl:attribute>
+ <!-- font size is calculated dynamically by qanda.heading template -->
+ <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
+ <xsl:attribute name="space-before.minimum">0.8em</xsl:attribute>
+ <xsl:attribute name="space-before.optimum">1.0em</xsl:attribute>
+ <xsl:attribute name="space-before.maximum">1.2em</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties common to all qanda set titles.
+
+
+
+
+
+
+qanda.title.level1.properties
+attribute set
+
+
+qanda.title.level1.properties
+Properties for level-1 qanda set titles
+
+
+
+
+<xsl:attribute-set name="qanda.title.level1.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master * 2.0736"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-1 qanda set titles.
+
+
+
+
+
+
+qanda.title.level2.properties
+attribute set
+
+
+qanda.title.level2.properties
+Properties for level-2 qanda set titles
+
+
+
+
+<xsl:attribute-set name="qanda.title.level2.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master * 1.728"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-2 qanda set titles.
+
+
+
+
+
+
+qanda.title.level3.properties
+attribute set
+
+
+qanda.title.level3.properties
+Properties for level-3 qanda set titles
+
+
+
+
+<xsl:attribute-set name="qanda.title.level3.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master * 1.44"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-3 qanda set titles.
+
+
+
+
+
+
+qanda.title.level4.properties
+attribute set
+
+
+qanda.title.level4.properties
+Properties for level-4 qanda set titles
+
+
+
+
+<xsl:attribute-set name="qanda.title.level4.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master * 1.2"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-4 qanda set titles.
+
+
+
+
+
+
+qanda.title.level5.properties
+attribute set
+
+
+qanda.title.level5.properties
+Properties for level-5 qanda set titles
+
+
+
+
+<xsl:attribute-set name="qanda.title.level5.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-5 qanda set titles.
+
+
+
+
+
+
+qanda.title.level6.properties
+attribute set
+
+
+qanda.title.level6.properties
+Properties for level-6 qanda set titles
+
+
+
+
+<xsl:attribute-set name="qanda.title.level6.properties">
+ <xsl:attribute name="font-size">
+ <xsl:value-of select="$body.font.master"></xsl:value-of>
+ <xsl:text>pt</xsl:text>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties of level-6 qanda set titles.
+This property set is actually
+used for all titles below level 5.
+
+
+
+
+
+
+article.appendix.title.properties
+attribute set
+
+
+article.appendix.title.properties
+Properties for appendix titles that appear in an article
+
+
+
+
+<xsl:attribute-set name="article.appendix.title.properties" use-attribute-sets="section.title.properties section.title.level1.properties">
+ <xsl:attribute name="margin-left">
+ <xsl:value-of select="$title.margin.left"></xsl:value-of>
+ </xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties for the title of an appendix that
+appears inside an article. The default is to use
+the properties of sect1 titles.
+
+
+
+
+
+
+abstract.properties
+attribute set
+
+
+abstract.properties
+Properties associated with the block surrounding an abstract
+
+
+
+
+<xsl:attribute-set name="abstract.properties">
+ <xsl:attribute name="start-indent">0.0in</xsl:attribute>
+ <xsl:attribute name="end-indent">0.0in</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+Block styling properties for abstract.
+
+See also abstract.title.properties.
+
+
+
+
+
+
+abstract.title.properties
+attribute set
+
+
+abstract.title.properties
+Properties for abstract titles
+
+
+
+
+<xsl:attribute-set name="abstract.title.properties">
+ <xsl:attribute name="font-family"><xsl:value-of select="$title.fontset"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="font-weight">bold</xsl:attribute>
+ <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
+ <xsl:attribute name="keep-with-next.within-column">always</xsl:attribute>
+ <xsl:attribute name="space-before.optimum"><xsl:value-of select="concat($body.font.master, 'pt')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="space-before.minimum"><xsl:value-of select="concat($body.font.master, 'pt * 0.8')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="space-before.maximum"><xsl:value-of select="concat($body.font.master, 'pt * 1.2')"></xsl:value-of></xsl:attribute>
+ <xsl:attribute name="hyphenate">false</xsl:attribute>
+ <xsl:attribute name="text-align">center</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+The properties for abstract titles.
+
+See also abstract.properties.
+
+
+
+
+
+
+index.page.number.properties
+attribute set
+
+
+index.page.number.properties
+Properties associated with index page numbers
+
+
+
+
+<xsl:attribute-set name="index.page.number.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+Properties associated with page numbers in indexes.
+Changing color to indicate the page number is a link is
+one possibility.
+
+
+
+
+
+
+
+revhistory.table.properties
+attribute set
+
+
+revhistory.table.properties
+The properties of table used for formatting revhistory
+
+
+
+
+<xsl:attribute-set name="revhistory.table.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+This property set defines appearance of revhistory table.
+
+
+
+
+
+
+revhistory.table.cell.properties
+attribute set
+
+
+revhistory.table.cell.properties
+The properties of table cells used for formatting revhistory
+
+
+
+
+<xsl:attribute-set name="revhistory.table.cell.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+This property set defines appearance of individual cells in revhistory table.
+
+
+
+
+
+
+revhistory.title.properties
+attribute set
+
+
+revhistory.title.properties
+The properties of revhistory title
+
+
+
+
+<xsl:attribute-set name="revhistory.title.properties">
+</xsl:attribute-set>
+
+
+
+Description
+
+This property set defines appearance of revhistory title.
+
+
+
+
+
+Profiling
+
+The following parameters can be used for attribute-based
+profiling of your document. For more information about profiling, see
+Profiling (conditional text).
+
+
+
+profile.arch
+string
+
+
+profile.arch
+Target profile for arch
+attribute
+
+
+
+
+<xsl:param name="profile.arch"></xsl:param>
+
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.audience
+string
+
+
+profile.audience
+Target profile for audience
+attribute
+
+
+
+
+<xsl:param name="profile.audience"></xsl:param>
+
+
+
+Description
+
+Value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.condition
+string
+
+
+profile.condition
+Target profile for condition
+attribute
+
+
+
+
+<xsl:param name="profile.condition"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.conformance
+string
+
+
+profile.conformance
+Target profile for conformance
+attribute
+
+
+
+
+<xsl:param name="profile.conformance"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.lang
+string
+
+
+profile.lang
+Target profile for lang
+attribute
+
+
+
+
+<xsl:param name="profile.lang"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.os
+string
+
+
+profile.os
+Target profile for os
+attribute
+
+
+
+
+<xsl:param name="profile.os"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.revision
+string
+
+
+profile.revision
+Target profile for revision
+attribute
+
+
+
+
+<xsl:param name="profile.revision"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.revisionflag
+string
+
+
+profile.revisionflag
+Target profile for revisionflag
+attribute
+
+
+
+
+<xsl:param name="profile.revisionflag"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.role
+string
+
+
+profile.role
+Target profile for role
+attribute
+
+
+
+
+<xsl:param name="profile.role"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+Note that role is often
+used for other purposes than profiling. For example it is commonly
+used to get emphasize in bold font:
+
+<emphasis role="bold">very important</emphasis>
+
+If you are using role for
+these purposes do not forget to add values like bold to
+value of this parameter. If you forgot you will get document with
+small pieces missing which are very hard to track.
+
+For this reason it is not recommended to use role attribute for profiling. You should
+rather use profiling specific attributes like userlevel, os, arch, condition, etc.
+
+
+
+
+
+
+
+profile.security
+string
+
+
+profile.security
+Target profile for security
+attribute
+
+
+
+
+<xsl:param name="profile.security"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.status
+string
+
+
+profile.status
+Target profile for status
+attribute
+
+
+
+
+<xsl:param name="profile.status"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.userlevel
+string
+
+
+profile.userlevel
+Target profile for userlevel
+attribute
+
+
+
+
+<xsl:param name="profile.userlevel"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.vendor
+string
+
+
+profile.vendor
+Target profile for vendor
+attribute
+
+
+
+
+<xsl:param name="profile.vendor"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.wordsize
+string
+
+
+profile.wordsize
+Target profile for wordsize
+attribute
+
+
+
+
+<xsl:param name="profile.wordsize"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.attribute
+string
+
+
+profile.attribute
+Name of user-specified profiling attribute
+
+
+
+
+<xsl:param name="profile.attribute"></xsl:param>
+
+
+
+Description
+
+This parameter is used in conjuction with
+profile.value.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.value
+string
+
+
+profile.value
+Target profile for user-specified attribute
+
+
+
+
+<xsl:param name="profile.value"></xsl:param>
+
+
+
+Description
+
+When you are using this parameter you must also specify name of
+profiling attribute with parameter
+profile.attribute.
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.separator
+string
+
+
+profile.separator
+Separator character for compound profile values
+
+
+
+
+<xsl:param name="profile.separator">;</xsl:param>
+
+
+
+Description
+
+Separator character used for compound profile values. See profile.arch
+
+
+
+
+
+Localization
+
+
+l10n.gentext.language
+string
+
+
+l10n.gentext.language
+Sets the gentext language
+
+
+
+
+<xsl:param name="l10n.gentext.language"></xsl:param>
+
+
+
+Description
+
+If this parameter is set to any value other than the empty string, its
+value will be used as the value for the language when generating text. Setting
+l10n.gentext.language overrides any settings within the
+document being formatted.
+
+It's much more likely that you might want to set the
+l10n.gentext.default.language parameter.
+
+
+
+
+
+
+ l10n.gentext.default.language
+ string
+
+
+ l10n.gentext.default.language
+ Sets the default language for generated text
+
+
+
+
+<xsl:param name="l10n.gentext.default.language">en</xsl:param>
+
+
+
+Description
+
+The value of the l10n.gentext.default.language
+parameter is used as the language for generated text if no setting is provided
+in the source document.
+
+
+
+
+
+
+l10n.gentext.use.xref.language
+boolean
+
+
+l10n.gentext.use.xref.language
+Use the language of target when generating cross-reference text?
+
+
+
+
+<xsl:param name="l10n.gentext.use.xref.language" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the language of the target will be used when
+generating cross reference text. Usually, the current
+language is used when generating text (that is, the language of the
+element that contains the cross-reference element). But setting this parameter
+allows the language of the element pointed to to control
+the generated text.
+
+Consider the following example:
+
+
+<para lang="en">See also <xref linkend="chap3"/>.</para>
+
+
+
+Suppose that Chapter 3 happens to be written in German.
+If l10n.gentext.use.xref.language is non-zero, the
+resulting text will be something like this:
+
+
+See also Kapital 3.
+
+
+Where the more traditional rendering would be:
+
+
+See also Chapter 3.
+
+
+
+
+
+
+
+l10n.lang.value.rfc.compliant
+boolean
+
+
+l10n.lang.value.rfc.compliant
+Make value of lang attribute RFC compliant?
+
+
+
+
+<xsl:param name="l10n.lang.value.rfc.compliant" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, ensure that the values for all lang attributes in HTML output are RFC
+compliantSection 8.1.1, Language Codes, in the HTML 4.0 Recommendation states that:
+
+
[RFC1766] defines and explains the language codes
+that must be used in HTML documents.
+Briefly, language codes consist of a primary code and a possibly
+empty series of subcodes:
+
+language-code = primary-code ( "-" subcode )*
+
+And in RFC 1766, Tags for the Identification
+of Languages, the EBNF for "language tag" is given as:
+
+Language-Tag = Primary-tag *( "-" Subtag )
+Primary-tag = 1*8ALPHA
+Subtag = 1*8ALPHA
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/autoidx-kimber.xsl b/doc/reference/lib/docbook-xsl-snapshot/html/autoidx-kimber.xsl
new file mode 100644
index 00000000..f8d9e3fd
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/autoidx-kimber.xsl
@@ -0,0 +1,168 @@
+
+
+
+
+
+
+
+
+
+
+]>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ERROR: the 'kimber' index method requires the
+ Saxon version 6 or 8 XSLT processor.
+
+
+
+
+
+ ERROR: the 'kimber' index method requires the
+ Innodata Isogen
Java extensions for
+ internationalized indexes.
Install those
+ extensions, or use a different index method.
+ For more information, see:
+ http://www.innodata-isogen.com/knowledge_center/tools_downloads/i18nsupport
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/autoidx-kosek.xsl b/doc/reference/lib/docbook-xsl-snapshot/html/autoidx-kosek.xsl
new file mode 100644
index 00000000..a1309190
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/autoidx-kosek.xsl
@@ -0,0 +1,125 @@
+
+
+
+
+
+
+]>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ERROR: the 'kosek' index method does not
+ work with the xsltproc XSLT processor.
+
+
+
+
+
+ ERROR: the 'kosek' index method does not
+ work with the Saxon 8 XSLT processor.
+
+
+
+
+
+ ERROR: the 'kosek' index method requires the
+ exslt:node-set() function. Use a processor that
+ has it, or use a different index method.
+
+
+
+
+
+ ERROR: the 'kosek' index method requires the
+ index extension functions be imported:
+ xsl:import href="common/autoidx-kosek.xsl"
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ERROR: the 'kosek' index method does not
+ work with the xsltproc XSLT processor.
+
+
+
+
+
+
+ ERROR: the 'kosek' index method requires the
+ exslt:node-set() function. Use a processor that
+ has it, or use a different index method.
+
+
+
+
+
+ ERROR: the 'kosek' index method requires the
+ kosek index extensions be imported:
+ xsl:import href="html/autoidx-kosek.xsl"
+
+
+
+
+
+
+
+
+
+
+
+
+ ERROR: the 'kimber' index method requires the
+ Saxon version 6 or 8 XSLT processor.
+
+
+
+
+
+ ERROR: the 'kimber' index method requires the
+ kimber index extensions be imported:
+ xsl:import href="html/autoidx-kimber.xsl"
+
+
+
+
+
+
+
+
+
+
+
+
+
+
The following annotations are from this essay. You are seeing
+ them here because your browser doesn’t support the user-interface
+ techniques used to make them appear as ‘popups’ on modern browsers.
The following annotations are from this essay. You are seeing
+ them here because your browser doesn’t support the user-interface
+ techniques used to make them appear as ‘popups’ on modern browsers.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Warning: footnote number may not be generated
+ correctly;
+
+ unexpected as first child of footnote.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ???
+
+
+
+
+ #
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ???
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/maketoc.xsl b/doc/reference/lib/docbook-xsl-snapshot/html/maketoc.xsl
new file mode 100644
index 00000000..1ba3931e
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/maketoc.xsl
@@ -0,0 +1,86 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ filename="
+
+ "
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/manifest.xsl b/doc/reference/lib/docbook-xsl-snapshot/html/manifest.xsl
new file mode 100644
index 00000000..01faaccf
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/manifest.xsl
@@ -0,0 +1,22 @@
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/math.xsl b/doc/reference/lib/docbook-xsl-snapshot/html/math.xsl
new file mode 100644
index 00000000..5bb4377c
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/math.xsl
@@ -0,0 +1,270 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Unsupported TeX math notation:
+
+
+
+
+
+
+
+
+
+
+
+
+ \nopagenumbers
+
+
+
+ \bye
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ \special{dvi2bitmap outputfile
+
+ }
+
+ $
+
+
+
+ $
+
+ \vfill\eject
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ \special{dvi2bitmap outputfile
+
+ }
+
+ $$
+
+
+
+ $$
+
+ \vfill\eject
+
+
+
+
+
+
+
+
+ \documentclass{article}
+ \pagestyle{empty}
+ \begin{document}
+
+
+
+ \end{document}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ \special{dvi2bitmap outputfile
+
+ }
+
+ $
+
+
+
+ $
+
+ \newpage
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ \special{dvi2bitmap outputfile
+
+ }
+
+ $$
+
+
+
+ $$
+
+ \newpage
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 0
+ 0
+ 1
+
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/oldchunker.xsl b/doc/reference/lib/docbook-xsl-snapshot/html/oldchunker.xsl
new file mode 100644
index 00000000..fe6b17c3
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/oldchunker.xsl
@@ -0,0 +1,202 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+Encoding used in generated HTML pages
+
+This encoding is used in files generated by chunking stylesheet. Currently
+only Saxon is able to change output encoding.
+
+
+
+
+
+
+
+
+
+Saxon character representation used in generated HTML pages
+
+This character representation is used in files generated by chunking stylesheet. If
+you want to suppress entity references for characters with direct representation
+in default.encoding, set this parameter to value native.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Chunking isn't supported with
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Writing
+
+
+ for
+
+
+ (
+
+ )
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Can't make chunks with
+
+ 's processor.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Writing
+
+
+ for
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Can't make chunks with
+
+ 's processor.
+
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/onechunk.xsl b/doc/reference/lib/docbook-xsl-snapshot/html/onechunk.xsl
new file mode 100644
index 00000000..527dccfd
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/onechunk.xsl
@@ -0,0 +1,37 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+1
+
+
+
+ #
+
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/param.xml b/doc/reference/lib/docbook-xsl-snapshot/html/param.xml
new file mode 100644
index 00000000..a12c79a8
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/param.xml
@@ -0,0 +1,10319 @@
+
+
+
+HTML Parameter Reference
+
+$Id: param.xweb 8092 2008-07-18 21:26:36Z kosek $
+
+
+
+ Walsh
+ Norman
+
+
+
+ 1999
+ 2000
+ 2001
+ 2002
+ 2003
+ 2004
+ 2005
+ 2006
+ 2007
+ Norman Walsh
+
+
+ This is reference documentation for all user-configurable
+ parameters in the DocBook XSL HTML stylesheets (for generating
+ HTML output).
+
+
+Admonitions
+
+
+admon.graphics.extension
+string
+
+
+admon.graphics.extension
+Filename extension for admonition graphics
+
+
+
+
+<xsl:param name="admon.graphics.extension">.png</xsl:param>
+
+
+
+Description
+
+Sets the filename extension to use on admonition graphics.
+
+
+
+
+
+
+admon.graphics.path
+string
+
+
+admon.graphics.path
+Path to admonition graphics
+
+
+
+<xsl:param name="admon.graphics.path">images/</xsl:param>
+
+
+Description
+
+Sets the path to the directory containing the admonition graphics
+(caution.png, important.png etc). This location is normally relative
+to the output html directory. See base.dir
+
+
+
+
+
+
+admon.graphics
+boolean
+
+
+admon.graphics
+Use graphics in admonitions?
+
+
+
+
+<xsl:param name="admon.graphics" select="0"></xsl:param>
+
+
+
+Description
+
+If true (non-zero), admonitions are presented in an alternate style that uses
+a graphic. Default graphics are provided in the distribution.
+
+
+
+
+
+
+
+admon.textlabel
+boolean
+
+
+admon.textlabel
+Use text label in admonitions?
+
+
+
+
+<xsl:param name="admon.textlabel" select="1"></xsl:param>
+
+
+
+Description
+
+If true (non-zero), admonitions are presented with a generated
+text label such as Note or Warning in the appropriate language.
+If zero, such labels are turned off, but any title child
+of the admonition element are still output.
+The default value is 1.
+
+
+
+
+
+
+
+admon.style
+string
+
+
+admon.style
+Specifies the CSS style attribute that should be added to
+admonitions.
+
+
+
+<xsl:param name="admon.style">
+ <xsl:text>margin-left: 0.5in; margin-right: 0.5in;</xsl:text>
+</xsl:param>
+
+
+Description
+
+Specifies the value of the CSS style
+attribute that should be added to admonitions.
+
+
+
+
+
+
+Callouts
+
+
+callout.defaultcolumn
+integer
+
+
+callout.defaultcolumn
+Indicates what column callouts appear in by default
+
+
+
+
+<xsl:param name="callout.defaultcolumn">60</xsl:param>
+
+
+
+Description
+
+If a callout does not identify a column (for example, if it uses
+the linerangeunit),
+it will appear in the default column.
+
+
+
+
+
+
+
+callout.graphics.extension
+string
+
+
+callout.graphics.extension
+Filename extension for callout graphics
+
+
+
+
+<xsl:param name="callout.graphics.extension">.png</xsl:param>
+
+
+
+
+Description
+Sets the filename extension to use on callout graphics.
+
+
+The Docbook XSL distribution provides callout graphics in the following formats:
+SVG (extension: .svg)
+PNG (extension: .png)
+GIF (extension: .gif)
+
+
+
+
+
+
+callout.graphics.number.limit
+integer
+
+
+callout.graphics.number.limit
+Number of the largest callout graphic
+
+
+
+
+<xsl:param name="callout.graphics.number.limit">15</xsl:param>
+
+
+
+
+Description
+
+If callout.graphics is non-zero, graphics
+are used to represent callout numbers instead of plain text. The value
+of callout.graphics.number.limit is the largest
+number for which a graphic exists. If the callout number exceeds this
+limit, the default presentation "(plain text instead of a graphic)"
+will be used.
+
+
+
+
+
+
+
+callout.graphics.path
+string
+
+
+callout.graphics.path
+Path to callout graphics
+
+
+
+
+<xsl:param name="callout.graphics.path">images/callouts/</xsl:param>
+
+
+
+Description
+
+Sets the path to the directory holding the callout graphics. his
+location is normally relative to the output html directory. see
+base.dir. Always terminate the directory with / since the graphic file
+is appended to this string, hence needs the separator.
+
+
+
+
+
+
+
+callout.graphics
+boolean
+
+
+callout.graphics
+Use graphics for callouts?
+
+
+
+
+<xsl:param name="callout.graphics" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, callouts are presented with graphics (e.g., reverse-video
+circled numbers instead of "(1)", "(2)", etc.).
+Default graphics are provided in the distribution.
+
+
+
+
+
+
+
+callout.list.table
+boolean
+
+
+callout.list.table
+Present callout lists using a table?
+
+
+
+
+<xsl:param name="callout.list.table" select="1"></xsl:param>
+
+
+
+Description
+
+The default presentation of CalloutLists uses
+an HTML DL. Some browsers don't align DLs very well
+if callout.graphics are used. With this option
+turned on, CalloutLists are presented in an HTML
+TABLE, which usually results in better alignment
+of the callout number with the callout description.
+
+
+
+
+
+
+callout.unicode.number.limit
+integer
+
+
+callout.unicode.number.limit
+Number of the largest unicode callout character
+
+
+
+
+<xsl:param name="callout.unicode.number.limit">10</xsl:param>
+
+
+
+Description
+
+If callout.unicode
+is non-zero, unicode characters are used to represent
+callout numbers. The value of
+callout.unicode.number.limit
+is
+the largest number for which a unicode character exists. If the callout number
+exceeds this limit, the default presentation "(nnn)" will always
+be used.
+
+
+
+
+
+
+
+callout.unicode.start.character
+integer
+
+
+callout.unicode.start.character
+First Unicode character to use, decimal value.
+
+
+
+
+<xsl:param name="callout.unicode.start.character">10102</xsl:param>
+
+
+
+Description
+
+If callout.graphics is zero and callout.unicode
+is non-zero, unicode characters are used to represent
+callout numbers. The value of
+callout.unicode.start.character
+is the decimal unicode value used for callout number one. Currently,
+only 10102 is supported in the stylesheets for this parameter.
+
+
+
+
+
+
+
+callout.unicode
+boolean
+
+
+callout.unicode
+Use Unicode characters rather than images for callouts.
+
+
+
+<xsl:param name="callout.unicode" select="0"></xsl:param>
+
+
+Description
+
+The stylesheets can use either an image of the numbers one to ten, or the single Unicode character which represents the numeral, in white on a black background. Use this to select the Unicode character option.
+
+
+
+
+
+
+
+callouts.extension
+boolean
+
+
+callouts.extension
+Enable the callout extension
+
+
+
+
+<xsl:param name="callouts.extension" select="1"></xsl:param>
+
+
+
+Description
+
+The callouts extension processes areaset
+elements in ProgramListingCO and other text-based
+callout elements.
+
+
+
+
+
+
+EBNF
+
+
+ebnf.table.bgcolor
+color
+
+
+ebnf.table.bgcolor
+Background color for EBNF tables
+
+
+
+
+<xsl:param name="ebnf.table.bgcolor">#F5DCB3</xsl:param>
+
+
+
+Description
+
+Sets the background color for EBNF tables (a pale brown). No
+bgcolor attribute is output if
+ebnf.table.bgcolor is set to the null string.
+
+
+
+
+
+
+
+ebnf.table.border
+boolean
+
+
+ebnf.table.border
+Selects border on EBNF tables
+
+
+
+<xsl:param name="ebnf.table.border" select="1"></xsl:param>
+
+
+Description
+
+Selects the border on EBNF tables. If non-zero, the tables have
+borders, otherwise they don't.
+
+
+
+
+
+
+ebnf.assignment
+rtf
+
+
+ebnf.assignment
+The EBNF production assignment operator
+
+
+
+
+<xsl:param name="ebnf.assignment">
+<code>::=</code>
+</xsl:param>
+
+
+
+
+Description
+
+The ebnf.assignment parameter determines what
+text is used to show assignment in productions
+in productionsets.
+
+While ::= is common, so are several
+other operators.
+
+
+
+
+
+
+ebnf.statement.terminator
+rtf
+
+
+ebnf.statement.terminator
+Punctuation that ends an EBNF statement.
+
+
+
+
+<xsl:param name="ebnf.statement.terminator"></xsl:param>
+
+
+
+
+Description
+
+The ebnf.statement.terminator parameter determines what
+text is used to terminate each production
+in productionset.
+
+Some notations end each statement with a period.
+
+
+
+
+
+ToC/LoT/Index Generation
+
+
+annotate.toc
+boolean
+
+
+annotate.toc
+Annotate the Table of Contents?
+
+
+
+<xsl:param name="annotate.toc" select="1"></xsl:param>
+
+
+Description
+
+If true, TOCs will be annotated. At present, this just means
+that the RefPurpose of RefEntry
+TOC entries will be displayed.
+
+
+
+
+
+
+
+autotoc.label.separator
+string
+
+
+autotoc.label.separator
+Separator between labels and titles in the ToC
+
+
+
+
+<xsl:param name="autotoc.label.separator">. </xsl:param>
+
+
+
+Description
+
+String used to separate labels and titles in a table of contents.
+
+
+
+
+
+
+autotoc.label.in.hyperlink
+boolean
+
+
+autotoc.label.in.hyperlink
+Include label in hyperlinked titles in TOC?
+
+
+
+<xsl:param name="autotoc.label.in.hyperlink" select="1"></xsl:param>
+
+
+Description
+
+If the value of
+autotoc.label.in.hyperlink is non-zero, labels
+are included in hyperlinked titles in the TOC. If it is instead zero,
+labels are still displayed prior to the hyperlinked titles, but
+are not hyperlinked along with the titles.
+
+
+
+
+
+
+process.source.toc
+boolean
+
+
+process.source.toc
+Process a non-empty toc element if it occurs in a source document?
+
+
+
+<xsl:param name="process.source.toc" select="0"></xsl:param>
+
+
+Description
+
+Specifies that the contents of a non-empty "hard-coded"
+toc element in a source document are processed to
+generate a TOC in output.
+
+ This parameter has no effect on automated generation of
+ TOCs. An automated TOC may still be generated along with the
+ "hard-coded" TOC. To suppress automated TOC generation, adjust the
+ value of the generate.toc paramameter.
+
+ The process.source.toc parameter also has
+ no effect if the toc element is empty; handling
+ for empty toc is controlled by the
+ process.empty.source.toc parameter.
+
+
+
+
+
+
+
+
+process.empty.source.toc
+boolean
+
+
+process.empty.source.toc
+Generate automated TOC if toc element occurs in a source document?
+
+
+
+<xsl:param name="process.empty.source.toc" select="0"></xsl:param>
+
+
+Description
+
+Specifies that if an empty toc element is found in a
+source document, an automated TOC is generated at this point in the
+document.
+
+ Depending on what the value of the
+ generate.toc parameter is, setting this
+ parameter to 1 could result in generation of
+ duplicate automated TOCs. So the
+ process.empty.source.toc is primarily useful
+ as an "override": by placing an empty toc in your
+ document and setting this parameter to 1, you can
+ force a TOC to be generated even if generate.toc
+ says not to.
+
+
+
+
+
+
+
+
+bridgehead.in.toc
+boolean
+
+
+bridgehead.in.toc
+Should bridgehead elements appear in the TOC?
+
+
+
+<xsl:param name="bridgehead.in.toc" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, bridgeheads appear in the TOC. Note that
+this option is not fully supported and may be removed in a future
+version of the stylesheets.
+
+
+
+
+
+
+
+simplesect.in.toc
+boolean
+
+
+simplesect.in.toc
+Should simplesect elements appear in the TOC?
+
+
+
+<xsl:param name="simplesect.in.toc" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, simplesects will be included in the TOC.
+
+
+
+
+
+
+
+manual.toc
+string
+
+
+manual.toc
+An explicit TOC to be used for the TOC
+
+
+
+
+<xsl:param name="manual.toc"></xsl:param>
+
+
+
+Description
+
+The manual.toc identifies an explicit TOC that
+will be used for building the printed TOC.
+
+
+
+
+
+
+
+toc.list.type
+list
+dl
+ul
+ol
+
+
+toc.list.type
+Type of HTML list element to use for Tables of Contents
+
+
+
+<xsl:param name="toc.list.type">dl</xsl:param>
+
+
+Description
+
+When an automatically generated Table of Contents (or List of Titles)
+is produced, this HTML element will be used to make the list.
+
+
+
+
+
+
+
+toc.section.depth
+integer
+
+
+toc.section.depth
+How deep should recursive sections appear
+in the TOC?
+
+
+
+<xsl:param name="toc.section.depth">2</xsl:param>
+
+
+Description
+
+Specifies the depth to which recursive sections should appear in the
+TOC.
+
+
+
+
+
+
+
+toc.max.depth
+integer
+
+
+toc.max.depth
+How many levels should be created for each TOC?
+
+
+
+<xsl:param name="toc.max.depth">8</xsl:param>
+
+
+Description
+
+Specifies the maximal depth of TOC on all levels.
+
+
+
+
+
+
+generate.toc
+table
+
+
+generate.toc
+Control generation of ToCs and LoTs
+
+
+
+
+<xsl:param name="generate.toc">
+appendix toc,title
+article/appendix nop
+article toc,title
+book toc,title,figure,table,example,equation
+chapter toc,title
+part toc,title
+preface toc,title
+qandadiv toc
+qandaset toc
+reference toc,title
+sect1 toc
+sect2 toc
+sect3 toc
+sect4 toc
+sect5 toc
+section toc
+set toc,title
+</xsl:param>
+
+
+
+
+Description
+
+This parameter has a structured value. It is a table of space-delimited
+path/value pairs. Each path identifies some element in the source document
+using a restricted subset of XPath (only the implicit child axis, no wildcards,
+no predicates). Paths can be either relative or absolute.
+
+When processing a particular element, the stylesheets consult this table to
+determine if a ToC (or LoT(s)) should be generated.
+
+For example, consider the entry:
+
+book toc,figure
+
+This indicates that whenever a book is formatted, a
+Table Of Contents and a List of Figures should be generated. Similarly,
+
+/chapter toc
+
+indicates that whenever a document that has a root
+ofchapter is formatted, a Table of
+Contents should be generated. The entry chapter would match
+all chapters, but /chapter matches only chapter
+document elements.
+
+Generally, the longest match wins. So, for example, if you want to distinguish
+articles in books from articles in parts, you could use these two entries:
+
+book/article toc,figure
+part/article toc
+
+Note that an article in a part can never match a book/article,
+so if you want nothing to be generated for articles in parts, you can simply leave
+that rule out.
+
+If you want to leave the rule in, to make it explicit that you're turning
+something off, use the value nop. For example, the following
+entry disables ToCs and LoTs for articles:
+
+article nop
+
+Do not simply leave the word article in the file
+without a matching value. That'd be just begging the silly little
+path/value parser to get confused.
+
+Section ToCs are further controlled by the
+generate.section.toc.level parameter.
+For a given section level to have a ToC, it must have both an entry in
+generate.toc and be within the range enabled by
+generate.section.toc.level.
+
+
+
+
+
+generate.section.toc.level
+integer
+
+
+generate.section.toc.level
+Control depth of TOC generation in sections
+
+
+
+
+<xsl:param name="generate.section.toc.level" select="0"></xsl:param>
+
+
+
+Description
+
+The generate.section.toc.level parameter
+controls the depth of section in which TOCs will be generated. Note
+that this is related to, but not the same as
+toc.section.depth, which controls the depth to
+which TOC entries will be generated in a given TOC.
+If, for example, generate.section.toc.level
+is 3, TOCs will be generated in first, second, and third
+level sections, but not in fourth level sections.
+
+
+
+
+
+
+
+generate.index
+boolean
+
+
+generate.index
+Do you want an index?
+
+
+
+<xsl:param name="generate.index" select="1"></xsl:param>
+
+
+Description
+
+Specify if an index should be generated.
+
+
+
+
+
+
+index.method
+list
+basic
+kosek
+kimber
+
+
+index.method
+Select method used to group index entries in an index
+
+
+
+
+<xsl:param name="index.method">basic</xsl:param>
+
+
+
+Description
+
+This parameter lets you select which method to use for sorting and grouping
+ index entries in an index.
+Indexes in Latin-based languages that have accented characters typically
+sort together accented words and unaccented words.
+Thus Á (U+00C1 LATIN CAPITAL LETTER A WITH ACUTE) would sort together
+with A (U+0041 LATIN CAPITAL LETTER A), so both would appear in the A
+section of the index.
+Languages using other alphabets (such as Russian, which is written in the Cyrillic alphabet)
+and languages using ideographic chararacters (such as Japanese)
+require grouping specific to the languages and alphabets.
+
+
+The default indexing method is limited.
+It can group accented characters in Latin-based languages only.
+It cannot handle non-Latin alphabets or ideographic languages.
+The other indexing methods require extensions of one type or
+another, and do not work with
+all XSLT processors, which is why they are not used by default.
+
+The three choices for indexing method are:
+
+
+basic
+
+
+(default) Sort and groups words based only on the Latin alphabet.
+Words with accented Latin letters will group and sort with
+their respective primary letter, but
+words in non-Latin alphabets will be
+put in the Symbols section of the index.
+
+
+
+
+kosek
+
+
+This method sorts and groups words based on letter groups configured in
+the DocBook locale file for the given language.
+See, for example, the French locale file common/fr.xml.
+This method requires that the XSLT processor
+supports the EXSLT extensions (most do).
+It also requires support for using
+user-defined functions in xsl:key (xsltproc does not).
+
+This method is suitable for any language for which you can
+list all the individual characters that should appear
+in each letter group in an index.
+It is probably not practical to use it for ideographic languages
+such as Chinese that have hundreds or thousands of characters.
+
+
+To use the kosek method, you must:
+
+
+
+Use a processor that supports its extensions, such as
+Saxon 6 or Xalan (xsltproc and Saxon 8 do not).
+
+
+
+Set the index.method parameter's value to kosek.
+
+
+
+Import the appropriate index extensions stylesheet module
+fo/autoidx-kosek.xsl or
+html/autoidx-kosek.xsl into your
+customization.
+
+
+
+
+
+
+
+kimber
+
+
+This method uses extensions to the Saxon processor to implement
+sophisticated indexing processes. It uses its own
+configuration file, which can include information for any number of
+languages. Each language's configuration can group
+words using one of two processes. In the
+enumerated process similar to that used in the kosek method,
+you indicate the groupings character-by-character.
+In the between-key process, you specify the
+break-points in the sort order that should start a new group.
+The latter configuration is useful for ideographic languages
+such as Chinese, Japanese, and Korean.
+You can also define your own collation algorithms and how you
+want mixed Latin-alphabet words sorted.
+
+
+For a whitepaper describing the extensions, see:
+http://www.innodata-isogen.com/knowledge_center/white_papers/back_of_book_for_xsl_fo.pdf.
+
+
+
+To download the extension library, see
+http://www.innodata-isogen.com/knowledge_center/tools_downloads/i18nsupport.
+
+
+
+
+To use the kimber method, you must:
+
+
+
+Use Saxon (version 6 or 8) as your XSLT processor.
+
+
+
+Install and configure the Innodata Isogen library, using
+the documentation that comes with it.
+
+
+
+Set the index.method parameter's value to kimber.
+
+
+
+Import the appropriate index extensions stylesheet module
+fo/autoidx-kimber.xsl or
+html/autoidx-kimber.xsl into your
+customization.
+
+
+
+
+
+
+
+
+
+
+
+
+
+index.on.type
+boolean
+
+
+index.on.type
+Select indexterms based on type
+attribute value
+
+
+
+
+<xsl:param name="index.on.type" select="0"></xsl:param>
+
+
+
+Description
+
+
+If non-zero,
+then an index element that has a
+type attribute
+value will contain only those indexterm
+elements with a matching type attribute value.
+If an index has no type
+attribute or it is blank, then the index will contain
+all indexterms in the current scope.
+
+
+
+If index.on.type is zero, then the
+type attribute has no effect
+on selecting indexterms for an index.
+
+
+For those using DocBook version 4.2 or earlier,
+the type attribute is not available
+for index terms. However, you can achieve the same
+effect by using the role attribute
+in the same manner on indexterm
+and index, and setting the stylesheet parameter
+index.on.role to a nonzero value.
+
+
+
+
+
+
+
+index.on.role
+boolean
+
+
+index.on.role
+Select indexterms based on role value
+
+
+
+
+<xsl:param name="index.on.role" select="0"></xsl:param>
+
+
+
+Description
+
+
+If non-zero,
+then an index element that has a
+role attribute
+value will contain only those indexterm
+elements with a matching role value.
+If an index has no role
+attribute or it is blank, then the index will contain
+all indexterms in the current scope.
+
+
+If index.on.role is zero, then the
+role attribute has no effect
+on selecting indexterms for an index.
+
+
+If you are using DocBook version 4.3 or later, you should
+use the type attribute instead of role
+on indexterm and index,
+and set the index.on.type to a nonzero
+value.
+
+
+
+
+
+
+
+index.prefer.titleabbrev
+boolean
+
+
+index.prefer.titleabbrev
+Should abbreviated titles be used as back references?
+
+
+
+
+<xsl:param name="index.prefer.titleabbrev" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, and if a titleabbrev is defined, the abbreviated title
+is used as the link text of a back reference in the index.
+
+
+
+
+
+
+
+index.term.separator
+string
+
+
+index.term.separator
+Override for punctuation separating an index term
+from its list of page references in an index
+
+
+
+
+<xsl:param name="index.term.separator"></xsl:param>
+
+
+
+Description
+
+This parameter permits you to override
+the text to insert between
+the end of an index term and its list of page references.
+Typically that might be a comma and a space.
+
+
+Because this text may be locale dependent,
+this parameter's value is normally taken from a gentext
+template named 'term-separator' in the
+context 'index' in the stylesheet
+locale file for the language
+of the current document.
+This parameter can be used to override the gentext string,
+and would typically be used on the command line.
+This parameter would apply to all languages.
+
+
+So this text string can be customized in two ways.
+You can reset the default gentext string using
+the local.l10n.xml parameter, or you can
+fill in the content for this normally empty
+override parameter.
+The content can be a simple string, or it can be
+something more complex such as a call-template.
+For fo output, it could be an fo:leader
+element to provide space of a specific length, or a dot leader.
+
+
+
+
+
+
+
+index.number.separator
+string
+
+
+index.number.separator
+Override for punctuation separating page numbers in index
+
+
+
+
+<xsl:param name="index.number.separator"></xsl:param>
+
+
+
+Description
+
+This parameter permits you to override the text to insert between
+page references in a formatted index entry. Typically
+that would be a comma and a space.
+
+
+Because this text may be locale dependent,
+this parameter's value is normally taken from a gentext
+template named 'number-separator' in the
+context 'index' in the stylesheet
+locale file for the language
+of the current document.
+This parameter can be used to override the gentext string,
+and would typically be used on the command line.
+This parameter would apply to all languages.
+
+
+So this text string can be customized in two ways.
+You can reset the default gentext string using
+the local.l10n.xml parameter, or you can
+override the gentext with the content of this parameter.
+The content can be a simple string, or it can be
+something more complex such as a call-template.
+
+
+In HTML index output, section title references are used instead of
+page number references. This punctuation appears between
+such section titles in an HTML index.
+
+
+
+
+
+
+
+index.range.separator
+string
+
+
+index.range.separator
+Override for punctuation separating the two numbers
+in a page range in index
+
+
+
+
+<xsl:param name="index.range.separator"></xsl:param>
+
+
+
+Description
+
+This parameter permits you
+to override the text to insert between
+the two numbers of a page range in an index.
+This parameter is only used by those XSL-FO processors
+that support an extension for generating such page ranges
+(such as XEP).
+
+Because this text may be locale dependent,
+this parameter's value is normally taken from a gentext
+template named 'range-separator' in the
+context 'index' in the stylesheet
+locale file for the language
+of the current document.
+This parameter can be used to override the gentext string,
+and would typically be used on the command line.
+This parameter would apply to all languages.
+
+
+So this text string can be customized in two ways.
+You can reset the default gentext string using
+the local.l10n.xml parameter, or you can
+override the gentext with the content of this parameter.
+The content can be a simple string, or it can be
+something more complex such as a call-template.
+
+
+In HTML index output, section title references are used instead of
+page number references. So there are no page ranges
+and this parameter has no effect.
+
+
+
+
+
+
+Stylesheet Extensions
+
+
+linenumbering.everyNth
+integer
+
+
+linenumbering.everyNth
+Indicate which lines should be numbered
+
+
+
+
+<xsl:param name="linenumbering.everyNth">5</xsl:param>
+
+
+
+Description
+
+If line numbering is enabled, everyNth line will be
+numbered. Note that numbering is one based, not zero based.
+
+
+
+
+
+
+
+linenumbering.extension
+boolean
+
+
+linenumbering.extension
+Enable the line numbering extension
+
+
+
+
+<xsl:param name="linenumbering.extension" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, verbatim environments (address, literallayout,
+programlisting, screen, synopsis) that specify line numbering will
+have line numbers.
+
+
+
+
+
+
+
+linenumbering.separator
+string
+
+
+linenumbering.separator
+Specify a separator between line numbers and lines
+
+
+
+
+<xsl:param name="linenumbering.separator"><xsl:text> </xsl:text></xsl:param>
+
+
+
+Description
+
+The separator is inserted between line numbers and lines in the
+verbatim environment. The default value is a single white space.
+ Note the interaction with linenumbering.width
+
+
+
+
+
+
+
+linenumbering.width
+integer
+
+
+linenumbering.width
+Indicates the width of line numbers
+
+
+
+
+<xsl:param name="linenumbering.width">3</xsl:param>
+
+
+
+Description
+
+If line numbering is enabled, line numbers will appear right
+justified in a field "width" characters wide.
+
+
+
+
+
+
+
+tablecolumns.extension
+boolean
+
+
+tablecolumns.extension
+Enable the table columns extension function
+
+
+
+
+<xsl:param name="tablecolumns.extension" select="1"></xsl:param>
+
+
+
+Description
+
+The table columns extension function adjusts the widths of table
+columns in the HTML result to more accurately reflect the specifications
+in the CALS table.
+
+
+
+
+
+
+
+ textinsert.extension
+ boolean
+
+
+ textinsert.extension
+ Enables the textinsert extension element
+
+
+
+ <xsl:param name="textinsert.extension" select="1"></xsl:param>
+
+
+ Description
+ The textinsert extension element inserts the contents of
+ a file into the result tree (as text).
+
+ To use the textinsert extension element, you must use
+ either Saxon or Xalan as your XSLT processor (it doesn’t
+ work with xsltproc), along with either the DocBook Saxon
+ extensions or DocBook Xalan extensions (for more
+ information about those extensions, see DocBook Saxon Extensions and DocBook Xalan Extensions), and you must set both
+ the use.extensions and
+ textinsert.extension parameters to
+ 1.
+ As an alternative to using the textinsert element,
+ consider using an Xinclude element with the
+ parse="text" attribute and value
+ specified, as detailed in Using XInclude for text inclusions.
+
+
+ See Also
+ You can also use the dbhtml-include href processing
+ instruction to insert external files — both files containing
+ plain text and files with markup content (including HTML
+ content).
+
+ More information
+ For how-to documentation on inserting contents of
+ external code files and other text files into output, see
+ External code files.
+ For guidelines on inserting contents of
+ HTML files into output, see Inserting external HTML code.
+
+
+
+
+
+textdata.default.encoding
+string
+
+
+textdata.default.encoding
+Default encoding of external text files which are included
+using textdata element
+
+
+
+
+<xsl:param name="textdata.default.encoding"></xsl:param>
+
+
+
+Description
+
+Specifies the encoding of any external text files included using
+textdata element. This value is used only when you do
+not specify encoding by the appropriate attribute
+directly on textdata. An empty string is interpreted as the system
+default encoding.
+
+
+
+
+
+
+graphicsize.extension
+boolean
+
+
+graphicsize.extension
+Enable the getWidth()/getDepth() extension functions
+
+
+
+
+<xsl:param name="graphicsize.extension" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero (and if use.extensions is non-zero
+and if you're using a processor that supports extension functions), the
+getWidth and getDepth functions
+will be used to extract image sizes from graphics.
+
+
+
+
+
+
+graphicsize.use.img.src.path
+boolean
+
+
+graphicsize.use.img.src.path
+Prepend img.src.path before
+filenames passed to extension functions
+
+
+
+
+<xsl:param name="graphicsize.use.img.src.path" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero img.src.path parameter will
+be appended before filenames passed to extension functions for
+measuring image dimensions.
+
+
+
+
+
+
+use.extensions
+boolean
+
+
+use.extensions
+Enable extensions
+
+
+
+
+<xsl:param name="use.extensions" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, extensions may be used. Each extension is
+further controlled by its own parameter. But if
+use.extensions is zero, no extensions will
+be used.
+
+
+
+
+
+
+Automatic labelling
+
+
+chapter.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+chapter.autolabel
+Specifies the labeling format for Chapter titles
+
+
+
+
+<xsl:param name="chapter.autolabel" select="1"></xsl:param>
+
+
+Description
+
+If non-zero, then chapters will be numbered using the parameter
+value as the number format if the value matches one of the following:
+
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+
+Any nonzero value other than the above will generate
+the default number format (arabic).
+
+
+
+
+
+
+
+appendix.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+appendix.autolabel
+Specifies the labeling format for Appendix titles
+
+
+
+
+<xsl:param name="appendix.autolabel">A</xsl:param>
+
+
+
+Description
+
+If non-zero, then appendices will be numbered using the
+parameter value as the number format if the value matches one of the
+following:
+
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+
+Any nonzero value other than the above will generate
+the default number format (upperalpha).
+
+
+
+
+
+
+
+part.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+part.autolabel
+Specifies the labeling format for Part titles
+
+
+
+
+<xsl:param name="part.autolabel">I</xsl:param>
+
+
+
+Description
+
+If non-zero, then parts will be numbered using the parameter
+value as the number format if the value matches one of the following:
+
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+
+Any nonzero value other than the above will generate
+the default number format (upperroman).
+
+
+
+
+
+
+
+
+reference.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+reference.autolabel
+Specifies the labeling format for Reference titles
+
+
+
+ <xsl:param name="reference.autolabel">I</xsl:param>
+
+
+Description
+If non-zero, references will be numbered using the parameter
+ value as the number format if the value matches one of the
+ following:
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+Any non-zero value other than the above will generate
+the default number format (upperroman).
+
+
+
+
+
+
+preface.autolabel
+list
+0none
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+preface.autolabel
+Specifices the labeling format for Preface titles
+
+
+
+<xsl:param name="preface.autolabel" select="0"></xsl:param>
+
+
+Description
+
+If non-zero then prefaces will be numbered using the parameter
+value as the number format if the value matches one of the following:
+
+
+
+
+ 1 or arabic
+
+ Arabic numeration (1, 2, 3 ...).
+
+
+
+ A or upperalpha
+
+ Uppercase letter numeration (A, B, C ...).
+
+
+
+ a or loweralpha
+
+ Lowercase letter numeration (a, b, c ...).
+
+
+
+ I or upperroman
+
+ Uppercase roman numeration (I, II, III ...).
+
+
+
+ i or lowerroman
+
+ Lowercase roman letter numeration (i, ii, iii ...).
+
+
+
+
+Any nonzero value other than the above will generate
+the default number format (arabic).
+
+
+
+
+
+
+
+
+qandadiv.autolabel
+boolean
+
+
+qandadiv.autolabel
+Are divisions in QAndASets enumerated?
+
+
+
+<xsl:param name="qandadiv.autolabel" select="1"></xsl:param>
+
+
+Description
+
+If non-zero, unlabeled qandadivs will be enumerated.
+
+
+
+
+
+
+
+section.autolabel
+boolean
+
+
+section.autolabel
+Are sections enumerated?
+
+
+
+<xsl:param name="section.autolabel" select="0"></xsl:param>
+
+
+Description
+
+If true (non-zero), unlabeled sections will be enumerated.
+
+
+
+
+
+
+
+section.autolabel.max.depth
+integer
+
+
+section.autolabel.max.depth
+The deepest level of sections that are numbered.
+
+
+
+
+<xsl:param name="section.autolabel.max.depth">8</xsl:param>
+
+
+
+Description
+
+When section numbering is turned on by the
+section.autolabel parameter, then this
+parameter controls the depth of section nesting that is
+numbered. Sections nested to a level deeper than this value will not
+be numbered.
+
+
+
+
+
+
+
+section.label.includes.component.label
+boolean
+
+
+section.label.includes.component.label
+Do section labels include the component label?
+
+
+
+<xsl:param name="section.label.includes.component.label" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, section labels are prefixed with the label of the
+component that contains them.
+
+
+
+
+
+
+
+label.from.part
+boolean
+
+
+label.from.part
+Renumber components in each part?
+
+
+
+
+<xsl:param name="label.from.part" select="0"></xsl:param>
+
+
+
+Description
+
+If label.from.part is non-zero, then
+ numbering of components — preface,
+ chapter, appendix, and
+ reference (when reference occurs at the
+ component level) — is re-started within each
+ part.
+If label.from.part is zero (the
+ default), numbering of components is not
+ re-started within each part; instead, components are
+ numbered sequentially throughout each book,
+ regardless of whether or not they occur within part
+ instances.
+
+
+
+
+
+
+component.label.includes.part.label
+boolean
+
+
+component.label.includes.part.label
+Do component labels include the part label?
+
+
+
+<xsl:param name="component.label.includes.part.label" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, number labels for chapter,
+appendix, and other component elements are prefixed with
+the label of the part element that contains them. So you might see
+Chapter II.3 instead of Chapter 3. Also, the labels for formal
+elements such as table and figure will include
+the part label. If there is no part element container, then no prefix
+is generated.
+
+
+This feature is most useful when the
+label.from.part parameter is turned on.
+In that case, there would be more than one chapter
+1, and the extra part label prefix will identify
+each chapter unambiguously.
+
+
+
+
+
+
+
+HTML
+
+
+html.base
+uri
+
+
+html.base
+An HTML base URI
+
+
+
+
+<xsl:param name="html.base"></xsl:param>
+
+
+Description
+
+If html.base is set, it is used for the base element
+in the head of the html documents. The parameter specifies
+the base URL for all relative URLs in the document. This is useful
+for dynamically served html where the base URI needs to be
+shifted.
+
+
+
+
+
+
+html.stylesheet.type
+string
+
+
+html.stylesheet.type
+The type of the stylesheet used in the generated HTML
+
+
+
+<xsl:param name="html.stylesheet.type">text/css</xsl:param>
+
+
+Description
+
+The type of the stylesheet to place in the HTML link tag.
+
+
+
+
+
+
+
+html.stylesheet
+string
+
+
+html.stylesheet
+Name of the stylesheet(s) to use in the generated HTML
+
+
+
+
+<xsl:param name="html.stylesheet"></xsl:param>
+
+
+
+Description
+
+The html.stylesheet parameter is either
+empty, indicating that no stylesheet link tag should be
+generated in the html output, or it is a list of one or more
+stylesheet files.
+
+Multiple stylesheets are space-delimited. If you need to
+reference a stylesheet URI that includes a space, encode it with
+%20. A separate html link element will
+be generated for each stylesheet in the order they are listed in the
+parameter.
+
+
+
+
+
+
+css.decoration
+boolean
+
+
+css.decoration
+Enable CSS decoration of elements
+
+
+
+
+<xsl:param name="css.decoration" select="1"></xsl:param>
+
+
+
+Description
+
+
+If non-zero, then html elements produced by the stylesheet may be
+decorated with style attributes. For example, the
+li tags produced for list items may include a
+fragment of CSS in the style attribute which sets
+the CSS property "list-style-type".
+
+
+
+
+
+
+
+spacing.paras
+boolean
+
+
+spacing.paras
+Insert additional <p> elements for spacing?
+
+
+
+
+<xsl:param name="spacing.paras" select="0"></xsl:param>
+
+
+
+Description
+
+When non-zero, additional, empty paragraphs are inserted in
+several contexts (for example, around informal figures), to create a
+more pleasing visual appearance in many browsers.
+
+
+
+
+
+
+
+emphasis.propagates.style
+boolean
+
+
+emphasis.propagates.style
+Pass emphasis role attribute through to HTML?
+
+
+
+<xsl:param name="emphasis.propagates.style" select="1"></xsl:param>
+
+
+Description
+If non-zero, the role attribute of
+emphasis elements will be passed through to the HTML as a
+class attribute on a span that surrounds the
+emphasis.
+
+
+
+
+
+para.propagates.style
+boolean
+
+
+para.propagates.style
+Pass para role attribute through to HTML?
+
+
+
+
+<xsl:param name="para.propagates.style" select="1"></xsl:param>
+
+
+
+Description
+
+If true, the role attribute of para elements
+will be passed through to the HTML as a class attribute on the
+p generated for the paragraph.
+
+
+
+
+
+
+phrase.propagates.style
+boolean
+
+
+phrase.propagates.style
+Pass phrase role attribute through to HTML?
+
+
+
+
+<xsl:param name="phrase.propagates.style" select="1"></xsl:param>
+
+
+Description
+
+If non-zero, the role attribute of phrase elements
+will be passed through to the HTML as a class
+attribute on a span that surrounds the
+phrase.
+
+
+
+
+
+
+entry.propagates.style
+boolean
+
+
+entry.propagates.style
+Pass entry role attribute through to HTML?
+
+
+
+
+<xsl:param name="entry.propagates.style" select="1"></xsl:param>
+
+
+
+Description
+
+If true, the role attribute of entry elements
+will be passed through to the HTML as a class attribute on the
+td or th generated for the table
+cell.
+
+
+
+
+
+
+html.longdesc
+boolean
+
+
+html.longdesc
+Should longdesc URIs be created?
+
+
+
+<xsl:param name="html.longdesc" select="1"></xsl:param>
+
+
+Description
+If non-zero, HTML files will be created for the
+longdesc attribute. These files
+are created from the textobjects in
+mediaobjects and
+inlinemediaobject.
+
+
+
+
+
+
+html.longdesc.link
+boolean
+
+
+html.longdesc.link
+Should a link to the longdesc be included in the HTML?
+
+
+
+
+<xsl:param name="html.longdesc.link" select="$html.longdesc"></xsl:param>
+
+
+
+Description
+
+If non-zero, links will be created to the
+HTML files created for the
+longdesc attribute. It makes no
+sense to enable this option without also enabling the
+html.longdesc parameter.
+
+
+
+
+
+
+
+
+make.valid.html
+boolean
+
+
+make.valid.html
+Attempt to make sure the HTML output is valid HTML
+
+
+
+
+<xsl:param name="make.valid.html" select="0"></xsl:param>
+
+
+
+Description
+
+If make.valid.html is true, the stylesheets take
+extra effort to ensure that the resulting HTML is valid. This may mean that some
+para tags are translated into HTML divs or
+that other substitutions occur.
+
+This parameter is different from html.cleanup
+because it changes the resulting markup; it does not use extension functions
+to manipulate result-tree-fragments and is therefore applicable to any
+XSLT processor.
+
+
+
+
+
+
+html.cleanup
+boolean
+
+
+html.cleanup
+Attempt to clean up the resulting HTML?
+
+
+
+
+<xsl:param name="html.cleanup" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, and if the EXSLT
+extensions are supported by your processor, the resulting HTML will be
+cleaned up. This improves the chances that the
+resulting HTML will be valid. It may also improve the formatting of
+some elements.
+
+This parameter is different from make.valid.html
+because it uses extension functions to manipulate result-tree-fragments.
+
+
+
+
+
+
+html.append
+string
+
+
+html.append
+Specifies content to append to HTML output
+
+
+
+<xsl:param name="html.append"></xsl:param>
+
+
+Description
+
+Specifies content to append to the end of HTML files output by
+the html/docbook.xsl stylesheet, after the
+closing <html> tag. You probably don’t want to set any
+value for this parameter; but if you do, the only value it should ever
+be set to is a newline character: 
 or
+
+
+
+
+
+
+
+draft.mode
+list
+no
+yes
+maybe
+
+
+draft.mode
+Select draft mode
+
+
+
+
+<xsl:param name="draft.mode">maybe</xsl:param>
+
+
+
+Description
+
+Selects draft mode. If draft.mode is
+yes, the entire document will be treated
+as a draft. If it is no, the entire document
+will be treated as a final copy. If it is maybe,
+individual sections will be treated as draft or final independently, depending
+on how their status attribute is set.
+
+
+
+
+
+
+
+draft.watermark.image
+uri
+
+
+draft.watermark.image
+The URI of the image to be used for draft watermarks
+
+
+
+
+<xsl:param name="draft.watermark.image">http://docbook.sourceforge.net/release/images/draft.png</xsl:param>
+
+
+
+Description
+
+The image to be used for draft watermarks.
+
+
+
+
+
+
+generate.id.attributes
+boolean
+
+
+generate.id.attributes
+Generate ID attributes on container elements?
+
+
+
+
+<xsl:param name="generate.id.attributes" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the HTML stylesheet will generate ID attributes on
+containers. For example, the markup:
+
+<section id="foo"><title>Some Title</title>
+<para>Some para.</para>
+</section>
+
+might produce:
+
+<div class="section" id="foo">
+<h2>Some Title</h2>
+<p>Some para.</p>
+</div>
+
+The alternative is to generate anchors:
+
+<div class="section">
+<h2><a name="foo"></a>Some Title</h2>
+<p>Some para.</p>
+</div>
+
+Because the name attribute of
+the a element and the id
+attribute of other tags are both of type ID, producing both
+generates invalid documents.
+
+As of version 1.50, you can use this switch to control which type of
+identifier is generated. For backwards-compatibility, generating
+a anchors is preferred.
+
+Note: at present, this switch is incompletely implemented.
+Disabling ID attributes will suppress them, but enabling ID attributes
+will not suppress the anchors.
+
+
+
+
+
+
+generate.meta.abstract
+boolean
+
+
+generate.meta.abstract
+Generate HTML META element from abstract?
+
+
+
+
+<xsl:param name="generate.meta.abstract" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, document abstracts will be reproduced in the HTML
+head, with >meta name="description" content="..."
+
+
+
+
+
+
+XSLT Processing
+
+
+rootid
+string
+
+
+rootid
+Specify the root element to format
+
+
+
+
+<xsl:param name="rootid"></xsl:param>
+
+
+Description
+
+If rootid is not empty, it must be the
+value of an ID that occurs in the document being formatted. The entire
+document will be loaded and parsed, but formatting will begin at the
+element identified, rather than at the root. For example, this allows
+you to process only chapter 4 of a book.
+Because the entire document is available to the processor, automatic
+numbering, cross references, and other dependencies are correctly
+resolved.
+
+
+
+
+
+
+suppress.navigation
+boolean
+
+
+suppress.navigation
+Disable header and footer navigation
+
+
+
+
+<xsl:param name="suppress.navigation" select="0"></xsl:param>
+
+
+
+Description
+
+
+If non-zero, header and footer navigation will be suppressed.
+
+
+
+
+
+
+suppress.header.navigation
+boolean
+
+
+suppress.header.navigation
+Disable header navigation
+
+
+
+
+<xsl:param name="suppress.header.navigation" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, header navigation will be suppressed.
+
+
+
+
+
+
+suppress.footer.navigation
+boolean
+
+
+suppress.footer.navigation
+Disable footer navigation
+
+
+
+<xsl:param name="suppress.footer.navigation">0</xsl:param>
+
+
+Description
+
+
+If non-zero, footer navigation will be suppressed.
+
+
+
+
+
+
+header.rule
+boolean
+
+
+header.rule
+Rule under headers?
+
+
+
+
+<xsl:param name="header.rule" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, a rule will be drawn below the page headers.
+
+
+
+
+
+
+footer.rule
+boolean
+
+
+footer.rule
+Rule over footers?
+
+
+
+
+<xsl:param name="footer.rule" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, a rule will be drawn above the page footers.
+
+
+
+
+
+
+id.warnings
+boolean
+
+
+id.warnings
+Should warnings be generated for titled elements without IDs?
+
+
+
+<xsl:param name="id.warnings" select="0"></xsl:param>
+
+
+Description
+If non-zero, the stylesheet will issue a warning for any element
+(other than the root element) which has a title but does not have an
+ID.
+
+
+
+
+Meta/*Info and Titlepages
+
+
+inherit.keywords
+boolean
+
+
+inherit.keywords
+Inherit keywords from ancestor elements?
+
+
+
+
+<xsl:param name="inherit.keywords" select="1"></xsl:param>
+
+
+Description
+
+If inherit.keywords
+is non-zero, the keyword meta for each HTML
+head element will include all of the keywords from
+ancestor elements. Otherwise, only the keywords from the current section
+will be used.
+
+
+
+
+
+
+
+make.single.year.ranges
+boolean
+
+
+make.single.year.ranges
+Print single-year ranges (e.g., 1998-1999)
+
+
+
+
+<xsl:param name="make.single.year.ranges" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, year ranges that span a single year will be printed
+in range notation (1998-1999) instead of discrete notation
+(1998, 1999).
+
+
+
+
+
+
+make.year.ranges
+boolean
+
+
+make.year.ranges
+Collate copyright years into ranges?
+
+
+
+<xsl:param name="make.year.ranges" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, multiple copyright year elements will be
+collated into ranges.
+This works only if each year number is put into a separate
+year element. The copyright element permits multiple
+year elements. The stylesheet will not successfully parse
+a complex year element such as <year>2001,2002,2003</year> into
+a range.
+
+
+
+
+
+
+author.othername.in.middle
+boolean
+
+
+author.othername.in.middle
+Is othername in author a
+middle name?
+
+
+
+
+<xsl:param name="author.othername.in.middle" select="1"></xsl:param>
+
+
+Description
+
+If non-zero, the othername of an author
+appears between the firstname and
+surname. Otherwise, othername
+is suppressed.
+
+
+
+
+
+
+
+blurb.on.titlepage.enabled
+boolean
+
+
+blurb.on.titlepage.enabled
+Display personblurb and authorblurb on title pages?
+
+
+
+
+<xsl:param name="blurb.on.titlepage.enabled" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, output from authorblurb and
+personblurb elements is displayed on title pages. If zero
+(the default), output from those elements is suppressed on title pages
+(unless you are using a titlepage customization
+that causes them to be included).
+
+
+
+
+
+
+contrib.inline.enabled
+boolean
+
+
+contrib.inline.enabled
+Display contrib output inline?
+
+
+
+<xsl:param name="contrib.inline.enabled">1</xsl:param>
+
+
+Description
+
+If non-zero (the default), output of the contrib element is
+displayed as inline content rather than as block content.
+
+
+
+
+
+
+editedby.enabled
+boolean
+
+
+editedby.enabled
+Display “Edited by” heading above editor name?
+
+
+
+<xsl:param name="editedby.enabled">1</xsl:param>
+
+
+Description
+
+If non-zero, a localized Edited
+by heading is displayed above editor names in output of the
+editor element.
+
+
+
+
+
+
+abstract.notitle.enabled
+boolean
+
+
+abstract.notitle.enabled
+Suppress display of abstract titles?
+
+
+ <xsl:param name="abstract.notitle.enabled" select="0"></xsl:param>
+
+Description
+If non-zero, in output of the abstract element on titlepages,
+display of the abstract title is suppressed.
+
+
+
+
+
+othercredit.like.author.enabled
+boolean
+
+
+othercredit.like.author.enabled
+Display othercredit in same style as author?
+
+
+
+<xsl:param name="othercredit.like.author.enabled">0</xsl:param>
+
+
+Description
+
+If non-zero, output of the
+othercredit element on titlepages is displayed in
+the same style as author and
+editor output. If zero then
+othercredit output is displayed using a style
+different than that of author and
+editor.
+
+
+
+
+
+
+generate.legalnotice.link
+boolean
+
+
+generate.legalnotice.link
+Write legalnotice to separate chunk and generate link?
+
+
+
+<xsl:param name="generate.legalnotice.link" select="0"></xsl:param>
+
+
+Description
+
+If the value of generate.legalnotice.link
+is non-zero, the stylesheet:
+
+
+
+ writes the contents of legalnotice to a separate
+ HTML file
+
+
+ inserts a hyperlink to the legalnotice file
+
+
+ adds (in the HTML head) either a single
+ link or element or multiple
+ link elements (depending on the value of the
+ html.head.legalnotice.link.multiple
+ parameter), with the value or values derived from the
+ html.head.legalnotice.link.types
+ parameter
+
+
+
+ Otherwise, if generate.legalnotice.link is
+ zero, legalnotice contents are rendered on the title
+ page.
+
+The name of the separate HTML file is computed as follows:
+
+
+
+ If a filename is given by the dbhtml filename
+processing instruction, that filename is used.
+
+
+ If the legalnotice has an id/xml:id
+attribute, and if use.id.as.filename != 0, the filename
+is the concatenation of the id value and the value of the html.ext
+parameter.
+
+
+ If the legalnotice does not have an id/xml:id
+ attribute, or if use.id.as.filename = 0, the filename is the concatenation of "ln-",
+auto-generated id value, and html.ext value.
+
+
+
+
+
+
+
+
+
+
+
+generate.revhistory.link
+boolean
+
+
+generate.revhistory.link
+Write revhistory to separate chunk and generate link?
+
+
+
+<xsl:param name="generate.revhistory.link" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, the contents of revhistory are written
+to a separate HTML file and a link to the file is
+generated. Otherwise, revhistory contents are rendered on
+the title page.
+
+The name of the separate HTML file is computed as follows:
+
+
+
+ If a filename is given by the dbhtml filename processing instruction,
+that filename is used.
+
+
+ If the revhistory has an id/xml:id
+attribute, and if use.id.as.filename != 0, the filename is the concatenation of
+the id value and the value of the html.ext parameter.
+
+
+ If the revhistory does not have an id/xml:id
+attribute, or if use.id.as.filename = 0, the filename is the concatenation of "rh-",
+auto-generated id value, and html.ext value.
+
+
+
+
+
+
+
+
+
+
+
+html.head.legalnotice.link.types
+string
+
+
+html.head.legalnotice.link.types
+Specifies link types for legalnotice link in html head
+
+
+
+
+<xsl:param name="html.head.legalnotice.link.types">copyright</xsl:param>
+
+
+
+Description
+
+The value of
+html.head.legalnotice.link.types is a
+space-separated list of link types, as described in Section 6.12
+of the HTML 4.01 specification. If the value of the
+generate.legalnotice.link parameter is
+non-zero, then the stylesheet generates (in the
+head section of the HTML source) either a single
+HTML link element or, if the value of the
+html.head.legalnotice.link.multiple is
+non-zero, one link element for each link type
+specified. Each link has the following attributes:
+
+
+
+ a rel attribute whose
+ value is derived from the value of
+ html.head.legalnotice.link.types
+
+
+ an href attribute whose
+ value is set to the URL of the file containing the
+ legalnotice
+
+
+ a title attribute whose
+ value is set to the title of the corresponding
+ legalnotice (or a title programatically
+ determined by the stylesheet)
+
+
+
+For example:
+
+ <link rel="license" href="ln-id2524073.html" title="Legal Notice">
+
+
+About the default value
+
+ In an ideal world, the default value of
+ html.head.legalnotice.link.types would
+ probably be “license”, since the content of the
+ DocBook legalnotice is typically license
+ information, not copyright information. However, the default value
+ is “copyright” for pragmatic reasons: because
+ that’s among the set of “recognized link types” listed in Section
+ 6.12 of the HTML 4.01 specification, and because certain
+ browsers and browser extensions are preconfigured to recognize that
+ value.
+
+
+
+
+
+
+
+html.head.legalnotice.link.multiple
+boolean
+
+
+html.head.legalnotice.link.multiple
+Generate multiple link instances in html head for legalnotice?
+
+
+
+
+<xsl:param name="html.head.legalnotice.link.multiple" select="1"></xsl:param>
+
+
+
+Description
+
+If html.head.legalnotice.link.multiple is
+non-zero and the value of
+html.head.legalnotice.link.types contains
+multiple link types, then the stylesheet generates (in the
+head section of the HTML source) one
+link element for each link type specified. For
+example, if the value of
+html.head.legalnotice.link.types is
+“copyright license”:
+
+ <link rel="copyright" href="ln-id2524073.html" title="Legal Notice">
+ <link rel="license" href="ln-id2524073.html" title="Legal Notice">
+
+ Otherwise, the stylesheet generates generates a single
+ link instance; for example:
+
+ <link rel="copyright license" href="ln-id2524073.html" title="Legal Notice">
+
+
+
+
+
+
+Reference Pages
+
+
+funcsynopsis.decoration
+boolean
+
+
+funcsynopsis.decoration
+Decorate elements of a funcsynopsis?
+
+
+
+
+<xsl:param name="funcsynopsis.decoration" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, elements of the funcsynopsis will be
+decorated (e.g. rendered as bold or italic text). The decoration is controlled by
+templates that can be redefined in a customization layer.
+
+
+
+
+
+
+
+funcsynopsis.style
+list
+ansi
+kr
+
+
+funcsynopsis.style
+What style of funcsynopsis should be generated?
+
+
+
+<xsl:param name="funcsynopsis.style">kr</xsl:param>
+
+
+Description
+
+If funcsynopsis.style is ansi,
+ANSI-style function synopses are generated for a
+funcsynopsis, otherwise K&R-style
+function synopses are generated.
+
+
+
+
+
+
+
+function.parens
+boolean
+
+
+function.parens
+Generate parens after a function?
+
+
+
+
+<xsl:param name="function.parens" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the formatting of a function element
+will include generated parentheses.
+
+
+
+
+
+
+
+refentry.generate.name
+boolean
+
+
+refentry.generate.name
+Output NAME header before 'RefName'(s)?
+
+
+
+
+<xsl:param name="refentry.generate.name" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, a "NAME" section title is output before the list
+of 'RefName's. This parameter and
+refentry.generate.title are mutually
+exclusive. This means that if you change this parameter to zero, you
+should set refentry.generate.title to non-zero unless
+you want get quite strange output.
+
+
+
+
+
+
+
+refentry.generate.title
+boolean
+
+
+refentry.generate.title
+Output title before 'RefName'(s)?
+
+
+
+
+<xsl:param name="refentry.generate.title" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the reference page title or first name is
+output before the list of 'RefName's. This parameter and
+refentry.generate.name are mutually exclusive.
+This means that if you change this parameter to non-zero, you
+should set refentry.generate.name to zero unless
+you want get quite strange output.
+
+
+
+
+
+
+
+refentry.xref.manvolnum
+boolean
+
+
+refentry.xref.manvolnum
+Output manvolnum as part of
+refentry cross-reference?
+
+
+
+
+<xsl:param name="refentry.xref.manvolnum" select="1"></xsl:param>
+
+
+
+Description
+
+if non-zero, the manvolnum is used when cross-referencing
+refentrys, either with xref
+or citerefentry.
+
+
+
+
+
+
+
+citerefentry.link
+boolean
+
+
+citerefentry.link
+Generate URL links when cross-referencing RefEntrys?
+
+
+
+
+<xsl:param name="citerefentry.link" select="0"></xsl:param>
+
+
+Description
+
+If non-zero, a web link will be generated, presumably
+to an online man->HTML gateway. The text of the link is
+generated by the generate.citerefentry.link template.
+
+
+
+
+
+
+
+refentry.separator
+boolean
+
+
+refentry.separator
+Generate a separator between consecutive RefEntry elements?
+
+
+
+
+<xsl:param name="refentry.separator" select="1"></xsl:param>
+
+
+
+Description
+
+If true, a separator will be generated between consecutive
+reference pages.
+
+
+
+
+
+
+
+refclass.suppress
+boolean
+
+
+refclass.suppress
+Suppress display of refclass contents?
+
+
+
+
+<xsl:param name="refclass.suppress" select="0"></xsl:param>
+
+
+Description
+
+If the value of refclass.suppress is
+non-zero, then display of refclass contents is
+suppressed in output.
+
+
+
+
+
+Tables
+
+
+default.table.width
+length
+
+
+default.table.width
+The default width of tables
+
+
+
+<xsl:param name="default.table.width"></xsl:param>
+
+
+Description
+If non-zero, this value will be used for the
+width attribute on tables that do not specify an
+alternate width (with the dbhtml table-width or
+dbfo table-width processing instruction).
+
+
+
+
+
+nominal.table.width
+length
+
+
+nominal.table.width
+The (absolute) nominal width of tables
+
+
+
+
+<xsl:param name="nominal.table.width">6in</xsl:param>
+
+
+
+Description
+
+In order to convert CALS column widths into HTML column widths, it
+is sometimes necessary to have an absolute table width to use for conversion
+of mixed absolute and relative widths. This value must be an absolute
+length (not a percentage).
+
+
+
+
+
+
+table.borders.with.css
+boolean
+
+
+table.borders.with.css
+Use CSS to specify table, row, and cell borders?
+
+
+
+
+<xsl:param name="table.borders.with.css" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, CSS will be used to draw table borders.
+
+
+
+
+
+
+
+table.cell.border.style
+list
+none
+solid
+dotted
+dashed
+double
+groove
+ridge
+inset
+outset
+solid
+
+
+table.cell.border.style
+Specifies the border style of table cells
+
+
+
+
+<xsl:param name="table.cell.border.style">solid</xsl:param>
+
+
+
+Description
+
+Specifies the border style of table cells.
+
+
+ To control properties of cell borders in HTML output, you must also turn on the
+ table.borders.with.css parameter.
+
+
+
+
+
+
+
+table.cell.border.thickness
+length
+
+
+table.cell.border.thickness
+Specifies the thickness of table cell borders
+
+
+
+
+<xsl:param name="table.cell.border.thickness">0.5pt</xsl:param>
+
+
+
+Description
+
+If non-zero, specifies the thickness of borders on table
+cells. The units are points. See
+CSS
+
+
+ To control properties of cell borders in HTML output, you must also turn on the
+ table.borders.with.css parameter.
+
+
+
+
+
+
+
+table.cell.border.color
+color
+
+
+table.cell.border.color
+Specifies the border color of table cells
+
+
+
+
+<xsl:param name="table.cell.border.color"></xsl:param>
+
+
+
+
+Description
+
+Set the color of table cell borders. If non-zero, the value is used
+for the border coloration. See CSS. A
+color is either a keyword or a numerical RGB specification.
+Keywords are aqua, black, blue, fuchsia, gray, green, lime, maroon,
+navy, olive, orange, purple, red, silver, teal, white, and
+yellow.
+
+
+ To control properties of cell borders in HTML output, you must also turn on the
+ table.borders.with.css parameter.
+
+
+
+
+
+
+
+table.frame.border.style
+list
+none
+solid
+dotted
+dashed
+double
+groove
+ridge
+inset
+outset
+solid
+
+
+table.frame.border.style
+Specifies the border style of table frames
+
+
+
+
+<xsl:param name="table.frame.border.style">solid</xsl:param>
+
+
+
+Description
+
+Specifies the border style of table frames.
+
+
+
+
+
+
+table.frame.border.thickness
+length
+
+
+table.frame.border.thickness
+Specifies the thickness of the frame border
+
+
+
+
+<xsl:param name="table.frame.border.thickness">0.5pt</xsl:param>
+
+
+
+Description
+
+Specifies the thickness of the border on the table's frame.
+
+
+
+
+
+
+table.frame.border.color
+color
+
+
+table.frame.border.color
+Specifies the border color of table frames
+
+
+
+
+<xsl:param name="table.frame.border.color"></xsl:param>
+
+
+
+
+Description
+
+Specifies the border color of table frames.
+
+
+
+
+
+
+default.table.frame
+string
+
+
+default.table.frame
+The default framing of tables
+
+
+
+
+<xsl:param name="default.table.frame">all</xsl:param>
+
+
+
+Description
+
+This value will be used when there is no frame attribute on the
+table.
+
+
+
+
+
+
+html.cellspacing
+integer
+
+
+html.cellspacing
+Default value for cellspacing in HTML tables
+
+
+
+
+<xsl:param name="html.cellspacing"></xsl:param>
+
+
+
+Description
+
+If non-zero, this value will be used as the default cellspacing
+value in HTML tables. nn for pixels or nn% for percentage
+length. E.g. 5 or 5%
+
+
+
+
+
+
+html.cellpadding
+integer
+
+
+html.cellpadding
+Default value for cellpadding in HTML tables
+
+
+
+
+<xsl:param name="html.cellpadding"></xsl:param>
+
+
+
+Description
+
+If non-zero, this value will be used as the default cellpadding value
+in HTML tables. nn for pixels or nn% for percentage length. E.g. 5 or
+5%
+
+
+
+
+
+QAndASet
+
+
+qanda.defaultlabel
+list
+number
+qanda
+none
+
+
+qanda.defaultlabel
+Sets the default for defaultlabel on QandASet.
+
+
+
+
+<xsl:param name="qanda.defaultlabel">number</xsl:param>
+
+
+
+Description
+
+If no defaultlabel attribute is specified on
+a qandaset, this value is used. It must be one of the legal
+values for the defaultlabel attribute, one from none, number or
+qanda. The default value is 'number'.
+
+Meaning
+qanda - questions are labeled “Q:” and answers are labeled “A:”.
+number - The entries are enumerated.
+none - No distinguishing label precedes Questions or Answers.
+
+
+
+
+
+
+
+
+
+
+
+
+qanda.inherit.numeration
+boolean
+
+
+qanda.inherit.numeration
+Does enumeration of QandASet components inherit the numeration of parent elements?
+
+
+
+
+<xsl:param name="qanda.inherit.numeration" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, numbered qandadiv elements and
+question and answer inherit the enumeration of
+the ancestors of the qandaset.
+
+
+
+
+
+
+
+qanda.in.toc
+boolean
+
+
+qanda.in.toc
+Should qandaentry questions appear in
+the document table of contents?
+
+
+
+<xsl:param name="qanda.in.toc" select="0"></xsl:param>
+
+
+Description
+
+If true (non-zero), then the generated table of contents
+for a document will include qandaset titles,
+qandadiv titles,
+and question elements. The default value (zero) excludes
+them from the TOC.
+
+This parameter does not affect any tables of contents
+that may be generated inside a qandaset or qandadiv.
+
+
+
+
+
+
+
+qanda.nested.in.toc
+boolean
+
+
+qanda.nested.in.toc
+Should nested answer/qandaentry instances appear in TOC?
+
+
+
+
+<xsl:param name="qanda.nested.in.toc" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, instances of qandaentry
+that are children of answer elements are shown in
+the TOC.
+
+
+
+
+
+Linking
+
+
+target.database.document
+uri
+
+
+target.database.document
+Name of master database file for resolving
+olinks
+
+
+
+ <xsl:param name="target.database.document">olinkdb.xml</xsl:param>
+
+
+Description
+
+
+To resolve olinks between documents, the stylesheets use a master
+database document that identifies the target datafiles for all the
+documents within the scope of the olinks. This parameter value is the
+URI of the master document to be read during processing to resolve
+olinks. The default value is olinkdb.xml.
+
+The data structure of the file is defined in the
+targetdatabase.dtd DTD. The database file
+provides the high level elements to record the identifiers, locations,
+and relationships of documents. The cross reference data for
+individual documents is generally pulled into the database using
+system entity references or XIncludes. See also
+targets.filename.
+
+
+
+
+targets.filename
+string
+
+
+targets.filename
+Name of cross reference targets data file
+
+
+<xsl:param name="targets.filename">target.db</xsl:param>
+
+
+Description
+
+
+In order to resolve olinks efficiently, the stylesheets can
+generate an external data file containing information about
+all potential cross reference endpoints in a document.
+This parameter lets you change the name of the generated
+file from the default name target.db.
+The name must agree with that used in the target database
+used to resolve olinks during processing.
+See also target.database.document.
+
+
+
+
+
+
+olink.base.uri
+uri
+
+
+olink.base.uri
+Base URI used in olink hrefs
+
+
+<xsl:param name="olink.base.uri"></xsl:param>
+
+
+Description
+
+When cross reference data is collected for resolving olinks, it
+may be necessary to prepend a base URI to each target's href. This
+parameter lets you set that base URI when cross reference data is
+collected. This feature is needed when you want to link to a document
+that is processed without chunking. The output filename for such a
+document is not known to the XSL stylesheet; the only target
+information consists of fragment identifiers such as
+#idref. To enable the resolution of olinks between
+documents, you should pass the name of the HTML output file as the
+value of this parameter. Then the hrefs recorded in the cross
+reference data collection look like
+outfile.html#idref, which can be reached as links
+from other documents.
+
+
+
+
+
+use.local.olink.style
+boolean
+
+
+use.local.olink.style
+Process olinks using xref style of current
+document
+
+
+<xsl:param name="use.local.olink.style" select="0"></xsl:param>
+
+Description
+
+When cross reference data is collected for use by olinks, the data for each potential target includes one field containing a completely assembled cross reference string, as if it were an xref generated in that document. Other fields record the separate title, number, and element name of each target. When an olink is formed to a target from another document, the olink resolves to that preassembled string by default. If the use.local.olink.style parameter is set to non-zero, then instead the cross
+reference string is formed again from the target title, number, and
+element name, using the stylesheet processing the targeting document.
+Then olinks will match the xref style in the targeting document
+rather than in the target document. If both documents are processed
+with the same stylesheet, then the results will be the same.
+
+
+
+
+
+current.docid
+string
+
+
+current.docid
+targetdoc identifier for the document being
+processed
+
+
+<xsl:param name="current.docid"></xsl:param>
+
+
+Description
+
+When olinks between documents are resolved for HTML output, the stylesheet can compute the relative path between the current document and the target document. The stylesheet needs to know the targetdoc identifiers for both documents, as they appear in the target.database.document database file. This parameter passes to the stylesheet
+the targetdoc identifier of the current document, since that
+identifier does not appear in the document itself.
+This parameter can also be used for print output. If an olink's targetdoc id differs from the current.docid, then the stylesheet can append the target document's title to the generated olink text. That identifies to the reader that the link is to a different document, not the current document. See also olink.doctitle to enable that feature.
+
+
+
+
+
+olink.doctitle
+list
+no
+yes
+maybe
+
+
+olink.doctitle
+show the document title for external olinks?
+
+
+
+<xsl:param name="olink.doctitle">no</xsl:param>
+
+
+Description
+
+When olinks between documents are resolved, the generated text
+may not make it clear that the reference is to another document.
+It is possible for the stylesheets to append the other document's
+title to external olinks. For this to happen, two parameters must
+be set.
+
+
+This olink.doctitle parameter
+should be set to either yes or maybe
+to enable this feature.
+
+
+
+And you should also set the current.docid
+parameter to the document id for the document currently
+being processed for output.
+
+
+
+
+
+Then if an olink's targetdoc id differs from
+the current.docid value, the stylesheet knows
+that it is a reference to another document and can
+append the target document's
+title to the generated olink text.
+
+The text for the target document's title is copied from the
+olink database from the ttl element
+of the top-level div for that document.
+If that ttl element is missing or empty,
+no title is output.
+
+
+The supported values for olink.doctitle are:
+
+
+
+yes
+
+
+Always insert the title to the target document if it is not
+the current document.
+
+
+
+
+no
+
+
+Never insert the title to the target document, even if requested
+in an xrefstyle attribute.
+
+
+
+
+maybe
+
+
+Only insert the title to the target document, if requested
+in an xrefstyle attribute.
+
+
+
+
+An xrefstyle attribute
+may override the global setting for individual olinks.
+The following values are supported in an
+xrefstyle
+attribute using the select: syntax:
+
+
+
+
+docname
+
+
+Insert the target document name for this olink using the
+docname gentext template, but only
+if the value of olink.doctitle
+is not no.
+
+
+
+
+docnamelong
+
+
+Insert the target document name for this olink using the
+docnamelong gentext template, but only
+if the value of olink.doctitle
+is not no.
+
+
+
+
+nodocname
+
+
+Omit the target document name even if
+the value of olink.doctitle
+is yes.
+
+
+
+
+Another way of inserting the target document name
+for a single olink is to employ an
+xrefstyle
+attribute using the template: syntax.
+The %o placeholder (the letter o, not zero)
+in such a template
+will be filled in with the target document's title when it is processed.
+This will occur regardless of
+the value of olink.doctitle.
+
+Note that prior to version 1.66 of the XSL stylesheets,
+the allowed values for this parameter were 0 and 1. Those
+values are still supported and mapped to 'no' and 'yes', respectively.
+
+
+
+
+
+
+olink.debug
+boolean
+
+
+olink.debug
+Turn on debugging messages for olinks
+
+
+
+
+<xsl:param name="olink.debug" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, then each olink will generate several
+messages about how it is being resolved during processing.
+This is useful when an olink does not resolve properly
+and the standard error messages are not sufficient to
+find the problem.
+
+
+You may need to read through the olink XSL templates
+to understand the context for some of the debug messages.
+
+
+
+
+
+
+
+olink.properties
+attribute set
+
+
+olink.properties
+Properties associated with the cross-reference
+text of an olink.
+
+
+
+
+<xsl:attribute-set name="olink.properties">
+ <xsl:attribute name="show-destination">replace</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+Description
+
+This attribute set is applied to the
+fo:basic-link element of an olink. It is not applied to the
+optional page number or optional title of the external
+document.
+
+
+
+
+
+
+olink.lang.fallback.sequence
+string
+
+
+olink.lang.fallback.sequence
+look up translated documents if olink not found?
+
+
+
+<xsl:param name="olink.lang.fallback.sequence"></xsl:param>
+
+
+Description
+
+
+This parameter defines a list of lang values
+to search among to resolve olinks.
+
+
+Normally an olink tries to resolve to a document in the same
+language as the olink itself. The language of an olink
+is determined by its nearest ancestor element with a
+lang attribute, otherwise the
+value of the l10n.gentext.default.lang
+parameter.
+
+
+An olink database can contain target data for the same
+document in multiple languages. Each set of data has the
+same value for the targetdoc attribute in
+the document element in the database, but with a
+different lang attribute value.
+
+
+When an olink is being resolved, the target is first
+sought in the document with the same language as the olink.
+If no match is found there, then this parameter is consulted
+for additional languages to try.
+
+The olink.lang.fallback.sequence
+must be a whitespace separated list of lang values to
+try. The first one with a match in the olink database is used.
+The default value is empty.
+
+For example, a document might be written in German
+and contain an olink with
+targetdoc="adminguide".
+When the document is processed, the processor
+first looks for a target dataset in the
+olink database starting with:
+
+<document targetdoc="adminguide" lang="de">.
+
+
+If there is no such element, then the
+olink.lang.fallback.sequence
+parameter is consulted.
+If its value is, for example, fr en, then the processor next
+looks for targetdoc="adminguide" lang="fr", and
+then for targetdoc="adminguide" lang="en".
+If there is still no match, it looks for
+targetdoc="adminguide" with no
+lang attribute.
+
+
+This parameter is useful when a set of documents is only
+partially translated, or is in the process of being translated.
+If a target of an olink has not yet been translated, then this
+parameter permits the processor to look for the document in
+other languages. This assumes the reader would rather have
+a link to a document in a different language than to have
+a broken link.
+
+
+
+
+
+
+
+insert.olink.page.number
+list
+no
+yes
+maybe
+
+
+insert.olink.page.number
+Turns page numbers in olinks on and off
+
+
+
+
+<xsl:param name="insert.olink.page.number">no</xsl:param>
+
+
+
+Description
+
+The value of this parameter determines if
+cross references made between documents with
+olink will
+include page number citations.
+In most cases this is only applicable to references in printed output.
+
+The parameter has three possible values.
+
+
+
+no
+No page number references will be generated for olinks.
+
+
+
+yes
+Page number references will be generated
+for all olink references.
+The style of page reference may be changed
+if an xrefstyle
+attribute is used.
+
+
+
+maybe
+Page number references will not be generated
+for an olink element unless
+it has an
+xrefstyle
+attribute whose value specifies a page reference.
+
+
+
+Olinks that point to targets within the same document
+are treated as xrefs, and controlled by
+the insert.xref.page.number parameter.
+
+
+Page number references for olinks to
+external documents can only be inserted if the
+information exists in the olink database.
+This means each olink target element
+(div or obj)
+must have a page attribute
+whose value is its page number in the target document.
+The XSL stylesheets are not able to extract that information
+during processing because pages have not yet been created in
+XSLT transformation. Only the XSL-FO processor knows what
+page each element is placed on.
+Therefore some postprocessing must take place to populate
+page numbers in the olink database.
+
+
+
+
+
+
+
+
+
+insert.olink.pdf.frag
+boolean
+
+
+insert.olink.pdf.frag
+Add fragment identifiers for links into PDF files
+
+
+
+
+<xsl:param name="insert.olink.pdf.frag" select="0"></xsl:param>
+
+
+
+Description
+
+The value of this parameter determines whether
+the cross reference URIs to PDF documents made with
+olink will
+include fragment identifiers.
+
+
+When forming a URI to link to a PDF document,
+a fragment identifier (typically a '#' followed by an
+id value) appended to the PDF filename can be used by
+the PDF viewer to open
+the PDF file to a location within the document instead of
+the first page.
+However, not all PDF files have id
+values embedded in them, and not all PDF viewers can
+handle fragment identifiers.
+
+
+If insert.olink.pdf.frag is set
+to a non-zero value, then any olink targeting a
+PDF file will have the fragment identifier appended to the URI.
+The URI is formed by concatenating the value of the
+olink.base.uri parameter, the
+value of the baseuri
+attribute from the document
+element in the olink database with the matching
+targetdoc value,
+and the value of the href
+attribute for the targeted element in the olink database.
+The href attribute
+contains the fragment identifier.
+
+
+If insert.olink.pdf.frag is set
+to zero (the default value), then
+the href attribute
+from the olink database
+is not appended to PDF olinks, so the fragment identifier is left off.
+A PDF olink is any olink for which the
+baseuri attribute
+from the matching document
+element in the olink database ends with '.pdf'.
+Any other olinks will still have the fragment identifier added.
+
+
+
+
+
+
+prefer.internal.olink
+boolean
+
+
+prefer.internal.olink
+Prefer a local olink reference to an external reference
+
+
+
+
+<xsl:param name="prefer.internal.olink" select="0"></xsl:param>
+
+
+
+Description
+
+If you are re-using XML content modules in multiple documents,
+you may want to redirect some of your olinks. This parameter
+permits you to redirect an olink to the current document.
+
+
+For example: you are writing documentation for a product,
+which includes 3 manuals: a little installation
+booklet (booklet.xml), a user
+guide (user.xml), and a reference manual (reference.xml).
+All 3 documents begin with the same introduction section (intro.xml) that
+contains a reference to the customization section (custom.xml) which is
+included in both user.xml and reference.xml documents.
+
+
+How do you write the link to custom.xml in intro.xml
+so that it is interpreted correctly in all 3 documents?
+
+If you use xref, it will fail in user.xml.
+
+If you use olink (pointing to reference.xml),
+the reference in user.xml
+will point to the customization section of the reference manual, while it is
+actually available in user.xml.
+
+
+
+If you set the prefer.internal.olink
+parameter to a non-zero value, then the processor will
+first look in the olink database
+for the olink's targetptr attribute value
+in document matching the current.docid
+parameter value. If it isn't found there, then
+it tries the document in the database
+with the targetdoc
+value that matches the olink's targetdoc
+attribute.
+
+
+This feature permits an olink reference to resolve to
+the current document if there is an element
+with an id matching the olink's targetptr
+value. The current document's olink data must be
+included in the target database for this to work.
+
+
+There is a potential for incorrect links if
+the same id attribute value is used for different
+content in different documents.
+Some of your olinks may be redirected to the current document
+when they shouldn't be. It is not possible to control
+individual olink instances.
+
+
+
+
+
+
+
+link.mailto.url
+string
+
+
+link.mailto.url
+Mailto URL for the LINK REL=made HTML HEAD element
+
+
+
+
+<xsl:param name="link.mailto.url"></xsl:param>
+
+
+
+Description
+
+If not the empty string, this address will be used for the
+rel=made link element in the html head
+
+
+
+
+
+
+
+ulink.target
+string
+
+
+ulink.target
+The HTML anchor target for ULinks
+
+
+
+
+<xsl:param name="ulink.target">_top</xsl:param>
+
+
+
+Description
+
+If ulink.target is non-zero, its value will
+be used for the target attribute
+on anchors generated for ulinks.
+
+
+
+
+
+
+olink.fragid
+string
+
+
+olink.fragid
+Names the fragment identifier portion of an OLink resolver query
+
+
+
+<xsl:param name="olink.fragid">fragid=</xsl:param>
+
+
+Description
+The fragment identifier portion of an olink target.
+
+
+
+
+
+olink.outline.ext
+string
+
+
+olink.outline.ext
+The extension of OLink outline files
+
+
+
+
+<xsl:param name="olink.outline.ext">.olink</xsl:param>
+
+
+
+Description
+
+The extension to be expected for OLink outline files
+Bob has this parameter as dead. Please don't use
+
+
+
+
+
+
+olink.pubid
+string
+
+
+olink.pubid
+Names the public identifier portion of an OLink resolver query
+
+
+
+
+<xsl:param name="olink.pubid">pubid</xsl:param>
+
+
+
+Description
+
+
+
+
+
+
+
+
+olink.sysid
+string
+
+
+olink.sysid
+Names the system identifier portion of an OLink resolver query
+
+
+
+
+<xsl:param name="olink.sysid">sysid</xsl:param>
+
+
+
+Description
+
+FIXME
+
+
+
+
+
+
+olink.resolver
+string
+
+
+olink.resolver
+The root name of the OLink resolver (usually a script)
+
+
+
+ <xsl:param name="olink.resolver">/cgi-bin/olink</xsl:param>
+
+
+Description
+FIXME:
+
+
+
+
+Cross References
+
+
+collect.xref.targets
+list
+no
+yes
+only
+
+
+collect.xref.targets
+Controls whether cross reference data is
+collected
+
+
+<xsl:param name="collect.xref.targets">no</xsl:param>
+
+
+Description
+
+
+In order to resolve olinks efficiently, the stylesheets can
+generate an external data file containing information about
+all potential cross reference endpoints in a document.
+This parameter determines whether the collection process is run when the document is processed by the stylesheet. The default value is no, which means the data file is not generated during processing. The other choices are yes, which means the data file is created and the document is processed for output, and only, which means the data file is created but the document is not processed for output.
+See also targets.filename.
+
+
+
+
+
+
+insert.xref.page.number
+list
+no
+yes
+maybe
+
+
+insert.xref.page.number
+Turns page numbers in xrefs on and off
+
+
+
+
+<xsl:param name="insert.xref.page.number">no</xsl:param>
+
+
+
+Description
+
+The value of this parameter determines if
+cross references (xrefs) in
+printed output will
+include page number citations.
+It has three possible values.
+
+
+
+no
+No page number references will be generated.
+
+
+
+yes
+Page number references will be generated
+for all xref elements.
+The style of page reference may be changed
+if an xrefstyle
+attribute is used.
+
+
+
+maybe
+Page number references will not be generated
+for an xref element unless
+it has an
+xrefstyle
+attribute whose value specifies a page reference.
+
+
+
+
+
+
+
+
+
+use.role.as.xrefstyle
+boolean
+
+
+use.role.as.xrefstyle
+Use role attribute for
+xrefstyle on xref?
+
+
+
+
+<xsl:param name="use.role.as.xrefstyle" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, the role attribute on
+xref will be used to select the cross reference style.
+The DocBook
+Technical Committee recently added an
+xrefstyle attribute for this purpose.
+If the xrefstyle attribute
+is present, role will be ignored, regardless
+of this setting.
+
+Until an official DocBook release that includes the new
+attribute, this flag allows role
+to serve that purpose.
+
+
+
+Example
+
+The following small stylesheet shows how to configure the
+stylesheets to make use of the cross reference style:
+
+<?xml version="1.0"?>
+<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ version="1.0">
+
+<xsl:import href="../xsl/html/docbook.xsl"/>
+
+<xsl:output method="html"/>
+
+<xsl:param name="local.l10n.xml" select="document('')"/>
+<l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
+ <l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="en">
+ <l:context name="xref">
+ <l:template name="chapter" style="title" text="Chapter %n, %t"/>
+ <l:template name="chapter" text="Chapter %n"/>
+ </l:context>
+ </l:l10n>
+</l:i18n>
+
+</xsl:stylesheet>
+
+With this stylesheet, the cross references in the following document:
+
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<book id="book"><title>Book</title>
+
+<preface>
+<title>Preface</title>
+
+<para>Normal: <xref linkend="ch1"/>.</para>
+<para>Title: <xref xrefstyle="title" linkend="ch1"/>.</para>
+
+</preface>
+
+<chapter id="ch1">
+<title>First Chapter</title>
+
+<para>Irrelevant.</para>
+
+</chapter>
+</book>
+
+will appear as:
+
+
+Normal: Chapter 1.
+Title: Chapter 1, First Chapter.
+
+
+
+
+
+
+
+xref.with.number.and.title
+boolean
+
+
+xref.with.number.and.title
+Use number and title in cross references
+
+
+
+
+<xsl:param name="xref.with.number.and.title" select="1"></xsl:param>
+
+
+
+Description
+
+A cross reference may include the number (for example, the number of
+an example or figure) and the title which is a required child of some
+targets. This parameter inserts both the relevant number as well as
+the title into the link.
+
+
+
+
+
+
+xref.label-page.separator
+string
+
+
+xref.label-page.separator
+Punctuation or space separating label from page number in xref
+
+
+
+<xsl:param name="xref.label-page.separator"><xsl:text> </xsl:text></xsl:param>
+
+
+Description
+
+
+This parameter allows you to control the punctuation of certain
+types of generated cross reference text.
+When cross reference text is generated for an
+xref or
+olink element
+using an xrefstyle attribute
+that makes use of the select: feature,
+and the selected components include both label and page
+but no title,
+then the value of this parameter is inserted between
+label and page number in the output.
+If a title is included, then other separators are used.
+
+
+
+
+
+
+
+xref.label-title.separator
+string
+
+
+xref.label-title.separator
+Punctuation or space separating label from title in xref
+
+
+
+<xsl:param name="xref.label-title.separator">: </xsl:param>
+
+
+Description
+
+
+This parameter allows you to control the punctuation of certain
+types of generated cross reference text.
+When cross reference text is generated for an
+xref or
+olink element
+using an xrefstyle attribute
+that makes use of the select: feature,
+and the selected components include both label and title,
+then the value of this parameter is inserted between
+label and title in the output.
+
+
+
+
+
+
+
+xref.title-page.separator
+string
+
+
+xref.title-page.separator
+Punctuation or space separating title from page number in xref
+
+
+
+<xsl:param name="xref.title-page.separator"><xsl:text> </xsl:text></xsl:param>
+
+
+Description
+
+
+This parameter allows you to control the punctuation of certain
+types of generated cross reference text.
+When cross reference text is generated for an
+xref or
+olink element
+using an xrefstyle attribute
+that makes use of the select: feature,
+and the selected components include both title and page number,
+then the value of this parameter is inserted between
+title and page number in the output.
+
+
+
+
+
+
+Lists
+
+
+segmentedlist.as.table
+boolean
+
+
+segmentedlist.as.table
+Format segmented lists as tables?
+
+
+
+
+<xsl:param name="segmentedlist.as.table" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, segmentedlists will be formatted as
+tables.
+
+
+
+
+
+
+variablelist.as.table
+boolean
+
+
+variablelist.as.table
+Format variablelists as tables?
+
+
+
+
+<xsl:param name="variablelist.as.table" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, variablelists will be formatted as
+tables. A processing instruction exists to specify a particular width for the
+column containing the terms:
+dbhtml term-width=".25in"
+
+You can override this setting with a processing instruction as the
+child of variablelist: dbhtml
+list-presentation="table" or dbhtml
+list-presentation="list".
+
+This parameter only applies to the HTML transformations. In the
+FO case, proper list markup is robust enough to handle the formatting.
+But see also variablelist.as.blocks.
+
+ <variablelist>
+ <?dbhtml list-presentation="table"?>
+ <?dbhtml term-width="1.5in"?>
+ <?dbfo list-presentation="list"?>
+ <?dbfo term-width="1in"?>
+ <varlistentry>
+ <term>list</term>
+ <listitem>
+ <para>
+ Formatted as a table even if variablelist.as.table is set to 0.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+
+
+
+
+
+variablelist.term.separator
+string
+
+
+variablelist.term.separator
+Text to separate terms within a multi-term
+varlistentry
+
+
+
+
+<xsl:param name="variablelist.term.separator">, </xsl:param>
+
+
+Description
+
+When a varlistentry contains multiple term
+elements, the string specified in the value of the
+variablelist.term.separator parameter is placed
+after each term except the last.
+
+
+ To generate a line break between multiple terms in
+ a varlistentry, set a non-zero value for the
+ variablelist.term.break.after parameter. If
+ you do so, you may also want to set the value of the
+ variablelist.term.separator parameter to an
+ empty string (to suppress rendering of the default comma and space
+ after each term).
+
+
+
+
+
+
+
+variablelist.term.break.after
+boolean
+
+
+variablelist.term.break.after
+Generate line break after each term within a
+multi-term varlistentry?
+
+
+
+
+<xsl:param name="variablelist.term.break.after">0</xsl:param>
+
+
+Description
+
+Set a non-zero value for the
+variablelist.term.break.after parameter to
+generate a line break between terms in a
+multi-term varlistentry.
+
+
+If you set a non-zero value for
+variablelist.term.break.after, you may also
+want to set the value of the
+variablelist.term.separator parameter to an
+empty string (to suppress rendering of the default comma and space
+after each term).
+
+
+
+
+
+
+Bibliography
+
+
+bibliography.style
+list
+normal
+iso690
+
+
+bibliography.style
+Style used for formatting of biblioentries.
+
+
+
+
+<xsl:param name="bibliography.style">normal</xsl:param>
+
+
+
+Description
+
+Currently only normal and
+iso690 styles are supported.
+
+In order to use ISO690 style to the full extent you might need
+to use additional markup described on the
+following WiKi page.
+
+
+
+
+
+
+biblioentry.item.separator
+string
+
+
+biblioentry.item.separator
+Text to separate bibliography entries
+
+
+
+<xsl:param name="biblioentry.item.separator">. </xsl:param>
+
+
+Description
+
+Text to separate bibliography entries
+
+
+
+
+
+
+
+bibliography.collection
+string
+
+
+bibliography.collection
+Name of the bibliography collection file
+
+
+
+
+<xsl:param name="bibliography.collection">http://docbook.sourceforge.net/release/bibliography/bibliography.xml</xsl:param>
+
+
+
+
+Description
+
+Maintaining bibliography entries across a set of documents is tedious, time
+consuming, and error prone. It makes much more sense, usually, to store all of
+the bibliography entries in a single place and simply extract
+the ones you need in each document.
+
+That's the purpose of the
+bibliography.collection parameter. To setup a global
+bibliography database, follow these steps:
+
+First, create a stand-alone bibliography document that contains all of
+the documents that you wish to reference. Make sure that each bibliography
+entry (whether you use biblioentry or bibliomixed)
+has an ID.
+
+My global bibliography, ~/bibliography.xml begins
+like this:
+
+
+<!DOCTYPE bibliography
+ PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
+<bibliography><title>References</title>
+
+<bibliomixed id="xml-rec"><abbrev>XML 1.0</abbrev>Tim Bray,
+Jean Paoli, C. M. Sperberg-McQueen, and Eve Maler, editors.
+<citetitle><ulink url="http://www.w3.org/TR/REC-xml">Extensible Markup
+Language (XML) 1.0 Second Edition</ulink></citetitle>.
+World Wide Web Consortium, 2000.
+</bibliomixed>
+
+<bibliomixed id="xml-names"><abbrev>Namespaces</abbrev>Tim Bray,
+Dave Hollander,
+and Andrew Layman, editors.
+<citetitle><ulink url="http://www.w3.org/TR/REC-xml-names/">Namespaces in
+XML</ulink></citetitle>.
+World Wide Web Consortium, 1999.
+</bibliomixed>
+
+<!-- ... -->
+</bibliography>
+
+
+
+When you create a bibliography in your document, simply
+provide emptybibliomixed
+entries for each document that you wish to cite. Make sure that these
+elements have the same ID as the corresponding real
+entry in your global bibliography.
+
+For example:
+
+
+<bibliography><title>Bibliography</title>
+
+<bibliomixed id="xml-rec"/>
+<bibliomixed id="xml-names"/>
+<bibliomixed id="DKnuth86">Donald E. Knuth. <citetitle>Computers and
+Typesetting: Volume B, TeX: The Program</citetitle>. Addison-Wesley,
+1986. ISBN 0-201-13437-3.
+</bibliomixed>
+<bibliomixed id="relaxng"/>
+
+</bibliography>
+
+
+Note that it's perfectly acceptable to mix entries from your
+global bibliography with normal entries. You can use
+xref or other elements to cross-reference your
+bibliography entries in exactly the same way you do now.
+
+Finally, when you are ready to format your document, simply set the
+bibliography.collection parameter (in either a
+customization layer or directly through your processor's interface) to
+point to your global bibliography.
+
+The stylesheets will format the bibliography in your document as if
+all of the entries referenced appeared there literally.
+
+
+
+
+
+
+bibliography.numbered
+boolean
+
+
+bibliography.numbered
+Should bibliography entries be numbered?
+
+
+
+
+<xsl:param name="bibliography.numbered" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero bibliography entries will be numbered
+
+
+
+
+
+Glossary
+
+
+glossterm.auto.link
+boolean
+
+
+glossterm.auto.link
+Generate links from glossterm to glossentry automatically?
+
+
+
+
+<xsl:param name="glossterm.auto.link" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, links from inline glossterms to the corresponding
+glossentry elements in a glossary or glosslist
+will be automatically generated. This is useful when your glossterms are consistent
+and you don't want to add links manually.
+
+The automatic link generation feature is not used on glossterm elements
+that have a linkend attribute.
+
+
+
+
+
+
+firstterm.only.link
+boolean
+
+
+firstterm.only.link
+Does automatic glossterm linking only apply to firstterms?
+
+
+
+
+<xsl:param name="firstterm.only.link" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, only firstterms will be automatically linked
+to the glossary. If glossary linking is not enabled, this parameter
+has no effect.
+
+
+
+
+
+
+glossary.collection
+string
+
+
+glossary.collection
+Name of the glossary collection file
+
+
+
+
+<xsl:param name="glossary.collection"></xsl:param>
+
+
+
+Description
+
+Glossaries maintained independently across a set of documents
+are likely to become inconsistent unless considerable effort is
+expended to keep them in sync. It makes much more sense, usually, to
+store all of the glossary entries in a single place and simply
+extract the ones you need in each document.
+
+That's the purpose of the
+glossary.collection parameter. To setup a global
+glossary database, follow these steps:
+
+Setting Up the Glossary Database
+
+First, create a stand-alone glossary document that contains all of
+the entries that you wish to reference. Make sure that each glossary
+entry has an ID.
+
+Here's an example glossary:
+
+
+
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE glossary
+ PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
+<glossary>
+<glossaryinfo>
+<editor><firstname>Eric</firstname><surname>Raymond</surname></editor>
+<title>Jargon File 4.2.3 (abridged)</title>
+<releaseinfo>Just some test data</releaseinfo>
+</glossaryinfo>
+
+<glossdiv><title>0</title>
+
+<glossentry>
+<glossterm>0</glossterm>
+<glossdef>
+<para>Numeric zero, as opposed to the letter `O' (the 15th letter of
+the English alphabet). In their unmodified forms they look a lot
+alike, and various kluges invented to make them visually distinct have
+compounded the confusion. If your zero is center-dotted and letter-O
+is not, or if letter-O looks almost rectangular but zero looks more
+like an American football stood on end (or the reverse), you're
+probably looking at a modern character display (though the dotted zero
+seems to have originated as an option on IBM 3270 controllers). If
+your zero is slashed but letter-O is not, you're probably looking at
+an old-style ASCII graphic set descended from the default typewheel on
+the venerable ASR-33 Teletype (Scandinavians, for whom /O is a letter,
+curse this arrangement). (Interestingly, the slashed zero long
+predates computers; Florian Cajori's monumental "A History of
+Mathematical Notations" notes that it was used in the twelfth and
+thirteenth centuries.) If letter-O has a slash across it and the zero
+does not, your display is tuned for a very old convention used at IBM
+and a few other early mainframe makers (Scandinavians curse <emphasis>this</emphasis>
+arrangement even more, because it means two of their letters collide).
+Some Burroughs/Unisys equipment displays a zero with a <emphasis>reversed</emphasis>
+slash. Old CDC computers rendered letter O as an unbroken oval and 0
+as an oval broken at upper right and lower left. And yet another
+convention common on early line printers left zero unornamented but
+added a tail or hook to the letter-O so that it resembled an inverted
+Q or cursive capital letter-O (this was endorsed by a draft ANSI
+standard for how to draw ASCII characters, but the final standard
+changed the distinguisher to a tick-mark in the upper-left corner).
+Are we sufficiently confused yet?</para>
+</glossdef>
+</glossentry>
+
+<glossentry>
+<glossterm>1TBS</glossterm>
+<glossdef>
+<para role="accidence">
+<phrase role="pronounce"></phrase>
+<phrase role="partsofspeach">n</phrase>
+</para>
+<para>The "One True Brace Style"</para>
+<glossseealso>indent style</glossseealso>
+</glossdef>
+</glossentry>
+
+<!-- ... -->
+
+</glossdiv>
+
+<!-- ... -->
+
+</glossary>
+
+
+
+
+Marking Up Glossary Terms
+
+That takes care of the glossary database, now you have to get the entries
+into your document. Unlike bibliography entries, which can be empty, creating
+placeholder glossary entries would be very tedious. So instead,
+support for glossary.collection relies on implicit linking.
+
+In your source document, simply use firstterm and
+glossterm to identify the terms you wish to have included
+in the glossary. The stylesheets assume that you will either set the
+baseform attribute correctly, or that the
+content of the element exactly matches a term in your glossary.
+
+If you're using a glossary.collection, don't
+make explicit links on the terms in your document.
+
+So, in your document, you might write things like this:
+
+
+<para>This is dummy text, without any real meaning.
+The point is simply to reference glossary terms like <glossterm>0</glossterm>
+and the <firstterm baseform="1TBS">One True Brace Style (1TBS)</firstterm>.
+The <glossterm>1TBS</glossterm>, as you can probably imagine, is a nearly
+religious issue.</para>
+
+
+If you set the firstterm.only.link parameter,
+only the terms marked with firstterm will be links.
+Otherwise, all the terms will be linked.
+
+
+
+Marking Up the Glossary
+
+The glossary itself has to be identified for the stylesheets. For lack
+of a better choice, the role is used.
+To identify the glossary as the target for automatic processing, set
+the role to auto. The title of this
+glossary (and any other information from the glossaryinfo
+that's rendered by your stylesheet) will be displayed, but the entries will
+come from the database.
+
+
+Unfortunately, the glossary can't be empty, so you must put in
+at least one glossentry. The content of this entry
+is irrelevant, it will not be rendered:
+
+
+<glossary role="auto">
+<glossentry>
+<glossterm>Irrelevant</glossterm>
+<glossdef>
+<para>If you can see this, the document was processed incorrectly. Use
+the <parameter>glossary.collection</parameter> parameter.</para>
+</glossdef>
+</glossentry>
+</glossary>
+
+
+What about glossary divisions? If your glossary database has glossary
+divisions and your automatic glossary contains at least
+one glossdiv, the automic glossary will have divisions.
+If the glossdiv is missing from either location, no divisions
+will be rendered.
+
+Glossary entries (and divisions, if appropriate) in the glossary will
+occur in precisely the order they occur in your database.
+
+
+
+Formatting the Document
+
+Finally, when you are ready to format your document, simply set the
+glossary.collection parameter (in either a
+customization layer or directly through your processor's interface) to
+point to your global glossary.
+
+The stylesheets will format the glossary in your document as if
+all of the entries implicilty referenced appeared there literally.
+
+
+Limitations
+
+Glossary cross-references within the glossary are
+not supported. For example, this will not work:
+
+
+<glossentry>
+<glossterm>gloss-1</glossterm>
+<glossdef><para>A description that references <glossterm>gloss-2</glossterm>.</para>
+<glossseealso>gloss-2</glossseealso>
+</glossdef>
+</glossentry>
+
+
+If you put glossary cross-references in your glossary that way,
+you'll get the cryptic error: Warning:
+glossary.collection specified, but there are 0 automatic
+glossaries.
+
+Instead, you must do two things:
+
+
+
+Markup your glossary using glossseealso:
+
+
+<glossentry>
+<glossterm>gloss-1</glossterm>
+<glossdef><para>A description that references <glossterm>gloss-2</glossterm>.</para>
+<glossseealso>gloss-2</glossseealso>
+</glossdef>
+</glossentry>
+
+
+
+
+Make sure there is at least one glossterm reference to
+gloss-2in your document. The
+easiest way to do that is probably within a remark in your
+automatic glossary:
+
+
+<glossary role="auto">
+<remark>Make sure there's a reference to <glossterm>gloss-2</glossterm>.</remark>
+<glossentry>
+<glossterm>Irrelevant</glossterm>
+<glossdef>
+<para>If you can see this, the document was processed incorrectly. Use
+the <parameter>glossary.collection</parameter> parameter.</para>
+</glossdef>
+</glossentry>
+</glossary>
+
+
+
+
+
+
+
+
+
+
+glossary.sort
+boolean
+
+
+glossary.sort
+Sort glossentry elements?
+
+
+
+
+<xsl:param name="glossary.sort" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, then the glossentry elements within a
+glossary, glossdiv, or glosslist are sorted on the glossterm, using
+the current lang setting. If zero (the default), then
+glossentry elements are not sorted and are presented
+in document order.
+
+
+
+
+
+
+
+glossentry.show.acronym
+list
+no
+yes
+primary
+
+
+glossentry.show.acronym
+Display glossentry acronyms?
+
+
+
+
+<xsl:param name="glossentry.show.acronym">no</xsl:param>
+
+
+
+Description
+
+A setting of yes means they should be displayed;
+no means they shouldn't. If primary is used,
+then they are shown as the primary text for the entry.
+
+
+This setting controls both acronym and
+abbrev elements in the glossentry.
+
+
+
+
+
+
+Miscellaneous
+
+
+formal.procedures
+boolean
+
+
+formal.procedures
+Selects formal or informal procedures
+
+
+
+
+<xsl:param name="formal.procedures" select="1"></xsl:param>
+
+
+
+Description
+
+Formal procedures are numbered and always have a title.
+
+
+
+
+
+
+
+formal.title.placement
+table
+
+
+formal.title.placement
+Specifies where formal object titles should occur
+
+
+
+
+<xsl:param name="formal.title.placement">
+figure before
+example before
+equation before
+table before
+procedure before
+task before
+</xsl:param>
+
+
+
+Description
+
+Specifies where formal object titles should occur. For each formal object
+type (figure,
+example,
+equation,
+table, and procedure)
+you can specify either the keyword
+before or
+after.
+
+
+
+
+
+
+runinhead.default.title.end.punct
+string
+
+
+runinhead.default.title.end.punct
+Default punctuation character on a run-in-head
+
+
+
+<xsl:param name="runinhead.default.title.end.punct">.</xsl:param>
+
+
+
+Description
+
+If non-zero, For a formalpara, use the specified
+string as the separator between the title and following text. The period is the default value.
+
+
+
+
+
+
+runinhead.title.end.punct
+string
+
+
+runinhead.title.end.punct
+Characters that count as punctuation on a run-in-head
+
+
+
+
+<xsl:param name="runinhead.title.end.punct">.!?:</xsl:param>
+
+
+
+Description
+
+Specify which characters are to be counted as punctuation. These
+characters are checked for a match with the last character of the
+title. If no match is found, the
+runinhead.default.title.end.punct contents are
+inserted. This is to avoid duplicated punctuation in the output.
+
+
+
+
+
+
+
+show.comments
+boolean
+
+
+show.comments
+Display remark elements?
+
+
+
+
+<xsl:param name="show.comments" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, comments will be displayed, otherwise they
+are suppressed. Comments here refers to the remark element
+(which was called comment prior to DocBook
+4.0), not XML comments (<-- like this -->) which are
+unavailable.
+
+
+
+
+
+
+
+show.revisionflag
+boolean
+
+
+show.revisionflag
+Enable decoration of elements that have a revisionflag
+
+
+
+
+<xsl:param name="show.revisionflag" select="0"></xsl:param>
+
+
+
+Description
+
+
+If show.revisionflag is turned on, then the stylesheets
+may produce additional markup designed to allow a CSS stylesheet to
+highlight elements that have specific revisionflag settings.
+
+The markup inserted will be usually be either a <span> or
+<div> with an appropriate class
+attribute. (The value of the class attribute will be the same as the
+value of the revisionflag attribute). In some contexts, for example
+tables, where extra markup would be structurally illegal, the class
+attribute will be added to the appropriate container element.
+
+In general, the stylesheets only test for revisionflag in contexts
+where an importing stylesheet would have to redefine whole templates.
+Most of the revisionflag processing is expected to be done by another
+stylesheet, for example changebars.xsl.
+
+
+
+
+
+
+shade.verbatim
+boolean
+
+
+shade.verbatim
+Should verbatim environments be shaded?
+
+
+
+<xsl:param name="shade.verbatim" select="0"></xsl:param>
+
+
+Description
+
+In the FO stylesheet, if this parameter is non-zero then the
+shade.verbatim.style properties will be applied
+to verbatim environments.
+
+In the HTML stylesheet, this parameter is now deprecated. Use
+CSS instead.
+
+
+
+
+
+
+shade.verbatim.style
+attribute set
+
+
+shade.verbatim.style
+Properties that specify the style of shaded verbatim listings
+
+
+
+
+<xsl:attribute-set name="shade.verbatim.style">
+ <xsl:attribute name="border">0</xsl:attribute>
+ <xsl:attribute name="bgcolor">#E0E0E0</xsl:attribute>
+</xsl:attribute-set>
+
+
+
+
+Description
+
+Properties that specify the style of shaded verbatim listings. The
+parameters specified (the border and background color) are added to
+the styling of the xsl-fo output. A border might be specified as "thin
+black solid" for example. See xsl-fo
+
+
+
+
+
+
+punct.honorific
+string
+
+
+punct.honorific
+Punctuation after an honorific in a personal name.
+
+
+
+
+<xsl:param name="punct.honorific">.</xsl:param>
+
+
+
+Description
+
+This parameter specifies the punctuation that should be added after an
+honorific in a personal name.
+
+
+
+
+
+
+tex.math.in.alt
+list
+plain
+latex
+
+
+tex.math.in.alt
+TeX notation used for equations
+
+
+
+
+<xsl:param name="tex.math.in.alt"></xsl:param>
+
+
+
+Description
+
+If you want type math directly in TeX notation in equations,
+this parameter specifies notation used. Currently are supported two
+values -- plain and latex. Empty
+value means that you are not using TeX math at all.
+
+Preferred way for including TeX alternative of math is inside of
+textobject element. Eg.:
+
+<inlineequation>
+<inlinemediaobject>
+<imageobject>
+<imagedata fileref="eq1.gif"/>
+</imageobject>
+<textobject><phrase>E=mc squared</phrase></textobject>
+<textobject role="tex"><phrase>E=mc^2</phrase></textobject>
+</inlinemediaobject>
+</inlineequation>
+
+If you are using graphic element, you can
+store TeX inside alt element:
+
+<inlineequation>
+<alt role="tex">a^2+b^2=c^2</alt>
+<graphic fileref="a2b2c2.gif"/>
+</inlineequation>
+
+If you want use this feature, you should process your FO with
+PassiveTeX, which only supports TeX math notation. When calling
+stylsheet, don't forget to specify also
+passivetex.extensions=1.
+
+If you want equations in HTML, just process generated file
+tex-math-equations.tex by TeX or LaTeX. Then run
+dvi2bitmap program on result DVI file. You will get images for
+equations in your document.
+
+
+ This feature is useful for print/PDF output only if you
+ use the obsolete and now unsupported PassiveTeX XSL-FO
+ engine.
+
+
+
+
+Related Parameters
+ tex.math.delims,
+ passivetex.extensions,
+ tex.math.file
+
+More information
+ For how-to documentation on embedding TeX equations and
+ generating output from them, see
+ DBTeXMath.
+
+
+
+
+
+tex.math.file
+string
+
+
+tex.math.file
+Name of temporary file for generating images from equations
+
+
+
+
+<xsl:param name="tex.math.file">tex-math-equations.tex</xsl:param>
+
+
+
+Description
+
+Name of auxiliary file for TeX equations. This file can be
+processed by dvi2bitmap to get bitmap versions of equations for HTML
+output.
+
+
+Related Parameters
+ tex.math.in.alt,
+ tex.math.delims,
+
+
+More information
+ For how-to documentation on embedding TeX equations and
+ generating output from them, see
+ DBTeXMath.
+
+
+
+
+
+tex.math.delims
+boolean
+
+
+tex.math.delims
+Should equations output for processing by TeX be
+surrounded by math mode delimiters?
+
+
+
+
+<xsl:param name="tex.math.delims" select="1"></xsl:param>
+
+
+
+Description
+
+For compatibility with DSSSL based DBTeXMath from Allin Cottrell
+you should set this parameter to 0.
+
+
+Related Parameters
+ tex.math.in.alt,
+ passivetex.extensions
+
+
+See Also
+ You can also use the dbtex delims processing
+ instruction to control whether delimiters are output.
+
+More information
+ For how-to documentation on embedding TeX equations and
+ generating output from them, see
+ DBTeXMath.
+
+
+
+
+
+pixels.per.inch
+integer
+
+
+pixels.per.inch
+How many pixels are there per inch?
+
+
+
+
+<xsl:param name="pixels.per.inch">90</xsl:param>
+
+
+
+Description
+
+When lengths are converted to pixels, this value is used to
+determine the size of a pixel. The default value is taken from the
+XSL
+Recommendation.
+
+
+
+
+
+
+
+points.per.em
+number
+
+
+points.per.em
+Specify the nominal size of an em-space in points
+
+
+
+
+<xsl:param name="points.per.em">10</xsl:param>
+
+
+
+Description
+
+The fixed value used for calculations based upon the size of a
+character. The assumption made is that ten point font is in use. This
+assumption may not be valid.
+
+
+
+
+
+
+use.svg
+boolean
+
+
+use.svg
+Allow SVG in the result tree?
+
+
+
+
+<xsl:param name="use.svg" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, SVG will be considered an acceptable image format. SVG
+is passed through to the result tree, so correct rendering of the resulting
+diagram depends on the formatter (FO processor or web browser) that is used
+to process the output from the stylesheet.
+
+
+
+
+
+
+menuchoice.separator
+string
+
+
+menuchoice.separator
+Separator between items of a menuchoice
+other than guimenuitem and
+guisubmenu
+
+
+
+
+<xsl:param name="menuchoice.separator">+</xsl:param>
+
+
+
+Description
+
+Separator used to connect items of a menuchoice other
+than guimenuitem and guisubmenu. The latter
+elements are linked with menuchoice.menu.separator.
+
+
+
+
+
+
+
+menuchoice.menu.separator
+string
+
+
+menuchoice.menu.separator
+Separator between items of a menuchoice
+with guimenuitem or
+guisubmenu
+
+
+
+
+<xsl:param name="menuchoice.menu.separator"> → </xsl:param>
+
+
+
+Description
+
+Separator used to connect items of a menuchoice with
+guimenuitem or guisubmenu. Other elements
+are linked with menuchoice.separator.
+
+The default value is →, which is the
+→ (right arrow) character entity.
+The current FOP (0.20.5) requires setting the font-family
+explicitly.
+
+The default value also includes spaces around the arrow,
+which will allow a line to break. Replace the spaces with
+  (nonbreaking space) if you don't want those
+spaces to break.
+
+
+
+
+
+
+
+default.float.class
+string
+
+
+default.float.class
+Specifies the default float class
+
+
+
+
+<xsl:param name="default.float.class">
+ <xsl:choose>
+ <xsl:when test="contains($stylesheet.result.type,'html')">left</xsl:when>
+ <xsl:otherwise>before</xsl:otherwise>
+ </xsl:choose>
+</xsl:param>
+
+
+
+Description
+
+Selects the direction in which a float should be placed. for
+xsl-fo this is before, for html it is left. For Western texts, the
+before direction is the top of the page.
+
+
+
+
+
+
+footnote.number.format
+list
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+footnote.number.format
+Identifies the format used for footnote numbers
+
+
+
+
+<xsl:param name="footnote.number.format">1</xsl:param>
+
+
+
+Description
+
+The footnote.number.format specifies the format
+to use for footnote numeration (1, i, I, a, or A).
+
+
+
+
+
+
+table.footnote.number.format
+list
+11,2,3...
+AA,B,C...
+aa,b,c...
+ii,ii,iii...
+II,II,III...
+
+
+table.footnote.number.format
+Identifies the format used for footnote numbers in tables
+
+
+
+
+<xsl:param name="table.footnote.number.format">a</xsl:param>
+
+
+
+Description
+
+The table.footnote.number.format specifies the format
+to use for footnote numeration (1, i, I, a, or A) in tables.
+
+
+
+
+
+
+footnote.number.symbols
+
+
+
+footnote.number.symbols
+Special characters to use as footnote markers
+
+
+
+
+<xsl:param name="footnote.number.symbols"></xsl:param>
+
+
+
+Description
+
+If footnote.number.symbols is not the empty string,
+footnotes will use the characters it contains as footnote symbols. For example,
+*†‡◊✠ will identify
+footnotes with *, †, ‡,
+◊, and ✠. If there are more footnotes
+than symbols, the stylesheets will fall back to numbered footnotes using
+footnote.number.format.
+
+The use of symbols for footnotes depends on the ability of your
+processor (or browser) to render the symbols you select. Not all systems are
+capable of displaying the full range of Unicode characters. If the quoted characters
+in the preceding paragraph are not displayed properly, that's a good indicator
+that you may have trouble using those symbols for footnotes.
+
+
+
+
+
+
+table.footnote.number.symbols
+string
+
+
+table.footnote.number.symbols
+Special characters to use a footnote markers in tables
+
+
+
+
+<xsl:param name="table.footnote.number.symbols"></xsl:param>
+
+
+
+Description
+
+If table.footnote.number.symbols is not the empty string,
+table footnotes will use the characters it contains as footnote symbols. For example,
+*†‡◊✠ will identify
+footnotes with *, †, ‡,
+◊, and ✠. If there are more footnotes
+than symbols, the stylesheets will fall back to numbered footnotes using
+table.footnote.number.format.
+
+The use of symbols for footnotes depends on the ability of your
+processor (or browser) to render the symbols you select. Not all systems are
+capable of displaying the full range of Unicode characters. If the quoted characters
+in the preceding paragraph are not displayed properly, that's a good indicator
+that you may have trouble using those symbols for footnotes.
+
+
+
+
+
+
+highlight.source
+boolean
+
+
+highlight.source
+Should the content of programlisting
+be syntactically highlighted?
+
+
+
+
+<xsl:param name="highlight.source" select="0"></xsl:param>
+
+
+
+Description
+
+When this parameter is non-zero, the stylesheets will try to do
+syntax highlighting of the content of the programlisting element. The highlighting is done by the
+XSLTHL extension module. This is an external Java library which is not part of the DocBook XSL distribution.
+
+In order to use this extension, you must add
+xslthl-2.0.0.jar to your Java classpath. You can
+download this software from the XSLT syntax highlighting project at SourceForge.
+
+The configuration of syntax highlighting is stored in
+highlighting/xslthl-config.xml. The Java
+property xslthl.config or parameter highlight.xslthl.config must point to this
+file (using URL syntax).
+
+This extension is known to work with Saxon 6.5.x, Saxon 8.5+ and Xalan-J. Here is an example of a modified Saxon command:
+
+java -cp c:\batch\;…;c:\path\to\xslthl-2.0.0.jar -Dxslthl.config=file:///c:/docbook-xsl/highlighting/xslthl-config.xml … com.icl.saxon.StyleSheet …
+
+You can specify the language for each programlisting by using the language attribute. The
+highlighting.default.language parameter can be used for specifying the
+language to be used for programlistings without a language attribute.
+
+
+
+
+
+
+highlight.xslthl.config
+uri
+
+
+highlight.xslthl.config
+Location of XSLTHL configuration file
+
+
+
+
+<xsl:param name="highlight.xslthl.config"></xsl:param>
+
+
+
+Description
+
+This location has precedence over the corresponding Java property.
+
+
+
+
+
+
+highlight.default.language
+string
+
+
+highlight.default.language
+Default language of programlisting
+
+
+
+
+<xsl:param name="highlight.default.language"></xsl:param>
+
+
+
+Description
+
+This language is used when there is no language attribute on programlisting.
+
+
+
+
+
+
+email.delimiters.enabled
+boolean
+
+
+email.delimiters.enabled
+Generate delimiters around email addresses?
+
+
+
+
+<xsl:param name="email.delimiters.enabled" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, delimiters
+
+For delimiters, the
+stylesheets are currently hard-coded to output angle
+brackets.
+
+are generated around e-mail addresses
+(the output of the email element).
+
+
+
+
+
+Annotations
+
+
+annotation.support
+boolean
+
+
+annotation.support
+Enable annotations?
+
+
+
+
+<xsl:param name="annotation.support" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the stylesheets will attempt to support annotation
+elements in HTML by including some JavaScript (see
+annotation.js).
+
+
+
+
+
+
+annotation.js
+string
+
+
+annotation.js
+URIs identifying JavaScript files with support for annotation popups
+
+
+
+
+
+<xsl:param name="annotation.js">
+<xsl:text>http://docbook.sourceforge.net/release/script/AnchorPosition.js http://docbook.sourceforge.net/release/script/PopupWindow.js</xsl:text></xsl:param>
+
+
+
+
+Description
+
+If annotation.support is enabled and the
+document contains annotations, then the URIs listed
+in this parameter will be included. These JavaScript files are required
+for popup annotation support.
+
+
+
+
+
+
+annotation.css
+string
+
+
+annotation.css
+CSS rules for annotations
+
+
+
+
+<xsl:param name="annotation.css">
+/* ======================================================================
+ Annotations
+*/
+
+div.annotation-list { visibility: hidden;
+ }
+
+div.annotation-nocss { position: absolute;
+ visibility: hidden;
+ }
+
+div.annotation-popup { position: absolute;
+ z-index: 4;
+ visibility: hidden;
+ padding: 0px;
+ margin: 2px;
+ border-style: solid;
+ border-width: 1px;
+ width: 200px;
+ background-color: white;
+ }
+
+div.annotation-title { padding: 1px;
+ font-weight: bold;
+ border-bottom-style: solid;
+ border-bottom-width: 1px;
+ color: white;
+ background-color: black;
+ }
+
+div.annotation-body { padding: 2px;
+ }
+
+div.annotation-body p { margin-top: 0px;
+ padding-top: 0px;
+ }
+
+div.annotation-close { position: absolute;
+ top: 2px;
+ right: 2px;
+ }
+</xsl:param>
+
+
+
+Description
+
+If annotation.support is enabled and the
+document contains annotations, then the CSS in this
+parameter will be included in the document.
+
+
+
+
+
+
+annotation.graphic.open
+uri
+
+
+annotation.graphic.open
+Image for identifying a link that opens an annotation popup
+
+
+
+
+<xsl:param name="annotation.graphic.open">http://docbook.sourceforge.net/release/images/annot-open.png</xsl:param>
+
+
+
+Description
+
+This image is used inline to identify the location of
+annotations. It may be replaced by a user provided graphic. The size should be approximately 10x10 pixels.
+
+
+
+
+
+
+annotation.graphic.close
+uri
+
+
+annotation.graphic.close
+Image for identifying a link that closes an annotation popup
+
+
+
+
+<xsl:param name="annotation.graphic.close">
+http://docbook.sourceforge.net/release/images/annot-close.png</xsl:param>
+
+
+
+Description
+
+This image is used on popup annotations as the “x” that the
+user can click to dismiss the popup.
+This image is used on popup annotations as the “x” that the user can
+click to dismiss the popup. It may be replaced by a user provided graphic. The size should be approximately 10x10 pixels.
+
+
+
+
+
+Graphics
+
+
+img.src.path
+string
+
+
+img.src.path
+Path to HTML/FO image files
+
+
+
+<xsl:param name="img.src.path"></xsl:param>
+
+
+Description
+
+Add a path prefix to the value of the fileref
+attribute of graphic, inlinegraphic, and imagedata elements. The resulting
+compound path is used in the output as the value of the src
+attribute of img (HTML) or external-graphic (FO).
+
+
+
+The path given by img.src.path could be relative to the directory where the HTML/FO
+files are created, or it could be an absolute URI.
+The default value is empty.
+Be sure to include a trailing slash if needed.
+
+
+This prefix is not applied to any filerefs that start
+with "/" or contain "//:".
+
+
+
+
+
+
+
+keep.relative.image.uris
+boolean
+
+
+keep.relative.image.uris
+Should image URIs be resolved against xml:base?
+
+
+
+
+<xsl:param name="keep.relative.image.uris" select="1"></xsl:param>
+
+
+
+
+Description
+
+If non-zero, relative URIs (in, for example
+fileref attributes) will be used in the generated
+output. Otherwise, the URIs will be made absolute with respect to the
+base URI.
+
+Note that the stylesheets calculate (and use) the absolute form
+for some purposes, this only applies to the resulting output.
+
+
+
+
+
+
+graphic.default.extension
+string
+
+
+graphic.default.extension
+Default extension for graphic filenames
+
+
+
+<xsl:param name="graphic.default.extension"></xsl:param>
+
+
+Description
+
+If a graphic or mediaobject
+includes a reference to a filename that does not include an extension,
+and the format attribute is
+unspecified, the default extension will be used.
+
+
+
+
+
+
+
+default.image.width
+length
+
+
+default.image.width
+The default width of images
+
+
+
+
+<xsl:param name="default.image.width"></xsl:param>
+
+
+
+Description
+
+If specified, this value will be used for the
+width attribute on
+images that do not specify any
+viewport
+dimensions.
+
+
+
+
+
+
+nominal.image.width
+length
+
+
+nominal.image.width
+The nominal image width
+
+
+
+
+<xsl:param name="nominal.image.width" select="6 * $pixels.per.inch"></xsl:param>
+
+
+
+Description
+
+Graphic widths expressed as a percentage are problematic. In the
+following discussion, we speak of width and contentwidth, but
+the same issues apply to depth and contentdepth.
+
+A width of 50% means "half of the available space for the image."
+That's fine. But note that in HTML, this is a dynamic property and
+the image size will vary if the browser window is resized.
+
+A contentwidth of 50% means "half of the actual image width".
+But what does that mean if the stylesheets cannot assess the image's
+actual size? Treating this as a width of 50% is one possibility, but
+it produces behavior (dynamic scaling) that seems entirely out of
+character with the meaning.
+
+Instead, the stylesheets define a
+nominal.image.width and convert percentages to
+actual values based on that nominal size.
+
+
+
+
+
+
+nominal.image.depth
+length
+
+
+nominal.image.depth
+Nominal image depth
+
+
+
+
+<xsl:param name="nominal.image.depth" select="4 * $pixels.per.inch"></xsl:param>
+
+
+
+Description
+
+See nominal.image.width.
+
+
+
+
+
+
+use.embed.for.svg
+boolean
+
+
+use.embed.for.svg
+Use HTML embed for SVG?
+
+
+
+
+<xsl:param name="use.embed.for.svg" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, an embed element will be created for
+SVG figures. An object is always created,
+this parameter merely controls whether or not an additional embed
+is generated inside the object.
+
+On the plus side, this may be more portable among browsers and plug-ins.
+On the minus side, it isn't valid HTML.
+
+
+
+
+
+
+make.graphic.viewport
+boolean
+
+
+make.graphic.viewport
+Use tables in HTML to make viewports for graphics
+
+
+
+
+<xsl:param name="make.graphic.viewport" select="1"></xsl:param>
+
+
+
+Description
+
+The HTML img element only supports the notion
+of content-area scaling; it doesn't support the distinction between a
+content-area and a viewport-area, so we have to make some compromises.
+
+If make.graphic.viewport is non-zero, a table
+will be used to frame the image. This creates an effective viewport-area.
+
+
+Tables and alignment don't work together, so this parameter is ignored
+if alignment is specified on an image.
+
+
+
+
+
+preferred.mediaobject.role
+string
+
+
+preferred.mediaobject.role
+Select which mediaobject to use based on
+this value of an object's role attribute.
+
+
+
+
+
+<xsl:param name="preferred.mediaobject.role"></xsl:param>
+
+
+
+Description
+
+A mediaobject may contain several objects such as imageobjects.
+If the parameter use.role.for.mediaobject is
+non-zero, then the role attribute on
+imageobjects and other objects within a
+mediaobject container will be used to select which object
+will be used. If one of the objects has a role value that matches the
+preferred.mediaobject.role parameter, then it
+has first priority for selection. If more than one has such a role
+value, the first one is used.
+
+
+See the use.role.for.mediaobject parameter
+for the sequence of selection.
+
+
+
+
+
+use.role.for.mediaobject
+boolean
+
+
+use.role.for.mediaobject
+Use role attribute
+value for selecting which of several objects within a mediaobject to use.
+
+
+
+
+
+<xsl:param name="use.role.for.mediaobject" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, the role attribute on
+imageobjects or other objects within a mediaobject container will be used to select which object will be
+used.
+
+
+The order of selection when then parameter is non-zero is:
+
+
+
+ If the stylesheet parameter preferred.mediaobject.role has a value, then the object whose role equals that value is selected.
+
+
+Else if an object's role attribute has a value of
+html for HTML processing or
+fo for FO output, then the first
+of such objects is selected.
+
+
+
+Else the first suitable object is selected.
+
+
+
+If the value of
+use.role.for.mediaobject
+is zero, then role attributes are not considered
+and the first suitable object
+with or without a role value is used.
+
+
+
+
+
+
+ignore.image.scaling
+boolean
+
+
+ignore.image.scaling
+Tell the stylesheets to ignore the author's image scaling attributes
+
+
+
+
+<xsl:param name="ignore.image.scaling" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the scaling attributes on graphics and media objects are
+ignored.
+
+
+
+
+
+Chunking
+
+
+chunker.output.cdata-section-elements
+string
+
+
+chunker.output.cdata-section-elements
+List of elements to escape with CDATA sections
+
+
+
+<xsl:param name="chunker.output.cdata-section-elements"></xsl:param>
+
+
+Description
+This parameter specifies the list of elements that should be escaped
+as CDATA sections by the chunking stylesheet. Not all processors support
+specification of this parameter.
+
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+
+
+
+
+
+
+chunker.output.doctype-public
+string
+
+
+chunker.output.doctype-public
+Public identifer to use in the document type of generated pages
+
+
+
+<xsl:param name="chunker.output.doctype-public"></xsl:param>
+
+
+Description
+This parameter specifies the public identifier that should be used by
+the chunking stylesheet in the document type declaration of chunked pages.
+Not all processors support specification of
+this parameter.
+
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+
+
+
+
+
+
+chunker.output.doctype-system
+uri
+
+
+chunker.output.doctype-system
+System identifier to use for the document type in generated pages
+
+
+
+<xsl:param name="chunker.output.doctype-system"></xsl:param>
+
+
+Description
+This parameter specifies the system identifier that should be used by
+the chunking stylesheet in the document type declaration of chunked pages.
+Not all processors support specification of
+this parameter.
+
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+
+
+
+
+
+
+chunker.output.encoding
+string
+
+
+chunker.output.encoding
+Encoding used in generated pages
+
+
+
+<xsl:param name="chunker.output.encoding">ISO-8859-1</xsl:param>
+
+
+Description
+This parameter specifies the encoding to be used in files
+generated by the chunking stylesheet. Not all processors support
+specification of this parameter.
+
+This parameter used to be named default.encoding.
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+
+
+
+
+
+
+chunker.output.indent
+string
+
+
+chunker.output.indent
+Specification of indentation on generated pages
+
+
+
+<xsl:param name="chunker.output.indent">no</xsl:param>
+
+
+Description
+This parameter specifies the value of the indent
+specification for generated pages. Not all processors support
+specification of this parameter.
+
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+
+
+
+
+
+
+chunker.output.media-type
+string
+
+
+chunker.output.media-type
+Media type to use in generated pages
+
+
+
+<xsl:param name="chunker.output.media-type"></xsl:param>
+
+
+Description
+This parameter specifies the media type that should be used by
+the chunking stylesheet. Not all processors support specification of
+this parameter.
+
+This parameter specifies the media type that should be used by the
+chunking stylesheet. This should be one from those defined in
+[RFC2045] and
+ [RFC2046]
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+It must be one from html, xml or text
+
+
+
+
+
+
+chunker.output.method
+list
+html
+xml
+
+
+chunker.output.method
+Method used in generated pages
+
+
+
+<xsl:param name="chunker.output.method">html</xsl:param>
+
+
+Description
+This parameter specifies the output method to be used in files
+generated by the chunking stylesheet.
+
+This parameter used to be named output.method.
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+
+
+
+
+
+
+chunker.output.omit-xml-declaration
+string
+
+
+chunker.output.omit-xml-declaration
+Omit-xml-declaration for generated pages
+
+
+
+<xsl:param name="chunker.output.omit-xml-declaration">no</xsl:param>
+
+
+Description
+This parameter specifies the value of the omit-xml-declaration
+specification for generated pages. Not all processors support
+specification of this parameter.
+
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+
+
+
+
+
+
+chunker.output.standalone
+string
+
+
+chunker.output.standalone
+Standalone declaration for generated pages
+
+
+
+<xsl:param name="chunker.output.standalone">no</xsl:param>
+
+
+Description
+This parameter specifies the value of the standalone
+ specification for generated pages. It must be either
+ yes or no. Not all
+ processors support specification of this parameter.
+
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+
+
+
+
+
+
+saxon.character.representation
+string
+
+
+saxon.character.representation
+Saxon character representation used in generated HTML pages
+
+
+
+ <xsl:param name="saxon.character.representation" select="'entity;decimal'"></xsl:param>
+
+
+Description
+
+This parameter has effect only when Saxon 6 is used (version 6.4.2 or later).
+It sets the character representation in files generated by the chunking stylesheets.
+If you want to suppress entity references for characters with direct representations in
+chunker.output.encoding, set the parameter value to native.
+
+
+ For more information, see Saxon output character representation.
+
+
+This parameter is documented here, but the declaration is actually
+in the chunker.xsl stylesheet module.
+
+
+
+
+
+
+
+
+html.ext
+string
+
+
+html.ext
+Identifies the extension of generated HTML files
+
+
+
+
+<xsl:param name="html.ext">.html</xsl:param>
+
+
+
+Description
+
+The extension identified by html.ext will
+be used as the filename extension for chunks created by this
+stylesheet.
+
+
+
+
+
+
+use.id.as.filename
+boolean
+
+
+use.id.as.filename
+Use ID value of chunk elements as the filename?
+
+
+
+
+<xsl:param name="use.id.as.filename" select="0"></xsl:param>
+
+
+
+Description
+
+If use.id.as.filename
+is non-zero, the filename of chunk elements that have IDs will be
+derived from the ID value.
+
+
+
+
+
+
+
+html.extra.head.links
+boolean
+
+
+html.extra.head.links
+Toggle extra HTML head link information
+
+
+
+
+<xsl:param name="html.extra.head.links" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, extra link elements will be
+generated in the head of chunked HTML files. These
+extra links point to chapters, appendixes, sections, etc. as supported
+by the Site Navigation Bar in Mozilla 1.0 (as of CR1, at least).
+
+
+
+
+
+
+
+root.filename
+uri
+
+
+root.filename
+Identifies the name of the root HTML file when chunking
+
+
+
+
+<xsl:param name="root.filename">index</xsl:param>
+
+
+
+Description
+
+The root.filename is the base filename for
+the chunk created for the root of each document processed.
+
+
+
+
+
+
+
+base.dir
+uri
+
+
+base.dir
+The base directory of chunks
+
+
+
+
+<xsl:param name="base.dir"></xsl:param>
+
+
+
+Description
+
+If specified, the base.dir identifies
+the output directory for chunks. (If not specified, the output directory
+is system dependent.)
+
+
+
+
+
+
+ generate.manifest
+ boolean
+
+
+ generate.manifest
+ Generate a manifest file?
+
+
+
+ <xsl:param name="generate.manifest" select="0"></xsl:param>
+
+
+ Description
+
+ If non-zero, a list of HTML files generated by the
+ stylesheet transformation is written to the file named by
+ the manifest parameter.
+
+
+
+
+
+
+ manifest
+ string
+
+
+ manifest
+ Name of manifest file
+
+
+
+
+ <xsl:param name="manifest">HTML.manifest</xsl:param>
+
+
+
+ Description
+
+ The name of the file to which a manifest is written (if the
+ value of the generate.manifest parameter
+ is non-zero).
+
+
+
+
+
+
+manifest.in.base.dir
+boolean
+
+
+manifest.in.base.dir
+Should the manifest file be written into base.dir?
+
+
+
+
+<xsl:param name="manifest.in.base.dir" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the manifest file as well as project files for HTML Help and
+Eclipse Help are written into base.dir instead
+of the current directory.
+
+
+
+
+
+
+chunk.toc
+string
+
+
+chunk.toc
+An explicit TOC to be used for chunking
+
+
+
+
+<xsl:param name="chunk.toc"></xsl:param>
+
+
+
+Description
+
+The chunk.toc identifies an explicit TOC that
+will be used for chunking. This parameter is only used by the
+chunktoc.xsl stylesheet (and customization layers built
+from it).
+
+
+
+
+
+
+chunk.tocs.and.lots
+boolean
+
+
+chunk.tocs.and.lots
+Should ToC and LoTs be in separate chunks?
+
+
+
+
+<xsl:param name="chunk.tocs.and.lots" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, ToC and LoT (List of Examples, List of Figures, etc.)
+will be put in a separate chunk. At the moment, this chunk is not in the
+normal forward/backward navigation list. Instead, a new link is added to the
+navigation footer.
+
+This feature is still somewhat experimental. Feedback welcome.
+
+
+
+
+
+
+chunk.separate.lots
+boolean
+
+
+chunk.separate.lots
+Should each LoT be in its own separate chunk?
+
+
+
+
+<xsl:param name="chunk.separate.lots" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, each of the ToC and LoTs
+(List of Examples, List of Figures, etc.)
+will be put in its own separate chunk.
+The title page includes generated links to each of the separate files.
+
+
+This feature depends on the
+chunk.tocs.and.lots
+parameter also being non-zero.
+
+
+
+
+
+
+
+chunk.tocs.and.lots.has.title
+boolean
+
+
+chunk.tocs.and.lots.has.title
+Should ToC and LoTs in a separate chunks have title?
+
+
+
+
+<xsl:param name="chunk.tocs.and.lots.has.title" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero title of document is shown before ToC/LoT in
+separate chunk.
+
+
+
+
+
+
+chunk.section.depth
+integer
+
+
+chunk.section.depth
+Depth to which sections should be chunked
+
+
+
+
+<xsl:param name="chunk.section.depth" select="1"></xsl:param>
+
+
+
+Description
+
+This parameter sets the depth of section chunking.
+
+
+
+
+
+
+chunk.first.sections
+boolean
+
+
+chunk.first.sections
+Chunk the first top-level section?
+
+
+
+
+<xsl:param name="chunk.first.sections" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, a chunk will be created for the first top-level
+sect1 or section elements in
+each component. Otherwise, that section will be part of the chunk for
+its parent.
+
+
+
+
+
+
+
+chunk.quietly
+boolean
+
+
+chunk.quietly
+Omit the chunked filename messages.
+
+
+
+
+<xsl:param name="chunk.quietly" select="0"></xsl:param>
+
+
+
+Description
+
+If zero (the default), the XSL processor emits a message naming
+each separate chunk filename as it is being output.
+If nonzero, then the messages are suppressed.
+
+
+
+
+
+
+
+chunk.append
+string
+
+
+chunk.append
+Specifies content to append to chunked HTML output
+
+
+
+<xsl:param name="chunk.append"></xsl:param>
+
+
+Description
+
+Specifies content to append to the end of HTML files output by
+the html/chunk.xsl stylesheet, after the closing
+<html> tag. You probably don’t want to set any value
+for this parameter; but if you do, the only value it should ever be
+set to is a newline character: 
 or
+
+
+
+
+
+
+
+navig.graphics
+boolean
+
+
+navig.graphics
+Use graphics in navigational headers and footers?
+
+
+
+
+<xsl:param name="navig.graphics" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the navigational headers and footers in chunked
+HTML are presented in an alternate style that uses graphical icons for
+Next, Previous, Up, and Home. Default graphics are provided in the
+distribution. If zero, text is used instead of graphics.
+
+
+
+
+
+
+
+navig.graphics.extension
+string
+
+
+navig.graphics.extension
+Extension for navigational graphics
+
+
+
+
+<xsl:param name="navig.graphics.extension">.gif</xsl:param>
+
+
+
+Description
+
+Sets the filename extension to use on navigational graphics used
+in the headers and footers of chunked HTML.
+
+
+
+
+
+
+navig.graphics.path
+string
+
+
+navig.graphics.path
+Path to navigational graphics
+
+
+
+
+<xsl:param name="navig.graphics.path">images/</xsl:param>
+
+
+
+Description
+
+Sets the path, probably relative to the directory where the HTML
+files are created, to the navigational graphics used in the
+headers and footers of chunked HTML.
+
+
+
+
+
+
+
+navig.showtitles
+boolean
+
+
+navig.showtitles
+Display titles in HTML headers and footers?
+
+
+
+<xsl:param name="navig.showtitles">1</xsl:param>
+
+
+Description
+
+If non-zero,
+the headers and footers of chunked HTML
+display the titles of the next and previous chunks,
+along with the words 'Next' and 'Previous' (or the
+equivalent graphical icons if navig.graphics is true).
+If false (zero), then only the words 'Next' and 'Previous'
+(or the icons) are displayed.
+
+
+
+
+
+
+Profiling
+
+The following parameters can be used for attribute-based
+profiling of your document. For more information about profiling, see
+Profiling (conditional text).
+
+
+
+profile.arch
+string
+
+
+profile.arch
+Target profile for arch
+attribute
+
+
+
+
+<xsl:param name="profile.arch"></xsl:param>
+
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.audience
+string
+
+
+profile.audience
+Target profile for audience
+attribute
+
+
+
+
+<xsl:param name="profile.audience"></xsl:param>
+
+
+
+Description
+
+Value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.condition
+string
+
+
+profile.condition
+Target profile for condition
+attribute
+
+
+
+
+<xsl:param name="profile.condition"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.conformance
+string
+
+
+profile.conformance
+Target profile for conformance
+attribute
+
+
+
+
+<xsl:param name="profile.conformance"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.lang
+string
+
+
+profile.lang
+Target profile for lang
+attribute
+
+
+
+
+<xsl:param name="profile.lang"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.os
+string
+
+
+profile.os
+Target profile for os
+attribute
+
+
+
+
+<xsl:param name="profile.os"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.revision
+string
+
+
+profile.revision
+Target profile for revision
+attribute
+
+
+
+
+<xsl:param name="profile.revision"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.revisionflag
+string
+
+
+profile.revisionflag
+Target profile for revisionflag
+attribute
+
+
+
+
+<xsl:param name="profile.revisionflag"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.role
+string
+
+
+profile.role
+Target profile for role
+attribute
+
+
+
+
+<xsl:param name="profile.role"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+Note that role is often
+used for other purposes than profiling. For example it is commonly
+used to get emphasize in bold font:
+
+<emphasis role="bold">very important</emphasis>
+
+If you are using role for
+these purposes do not forget to add values like bold to
+value of this parameter. If you forgot you will get document with
+small pieces missing which are very hard to track.
+
+For this reason it is not recommended to use role attribute for profiling. You should
+rather use profiling specific attributes like userlevel, os, arch, condition, etc.
+
+
+
+
+
+
+
+profile.security
+string
+
+
+profile.security
+Target profile for security
+attribute
+
+
+
+
+<xsl:param name="profile.security"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.status
+string
+
+
+profile.status
+Target profile for status
+attribute
+
+
+
+
+<xsl:param name="profile.status"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.userlevel
+string
+
+
+profile.userlevel
+Target profile for userlevel
+attribute
+
+
+
+
+<xsl:param name="profile.userlevel"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.vendor
+string
+
+
+profile.vendor
+Target profile for vendor
+attribute
+
+
+
+
+<xsl:param name="profile.vendor"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.wordsize
+string
+
+
+profile.wordsize
+Target profile for wordsize
+attribute
+
+
+
+
+<xsl:param name="profile.wordsize"></xsl:param>
+
+
+
+Description
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.attribute
+string
+
+
+profile.attribute
+Name of user-specified profiling attribute
+
+
+
+
+<xsl:param name="profile.attribute"></xsl:param>
+
+
+
+Description
+
+This parameter is used in conjuction with
+profile.value.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.value
+string
+
+
+profile.value
+Target profile for user-specified attribute
+
+
+
+
+<xsl:param name="profile.value"></xsl:param>
+
+
+
+Description
+
+When you are using this parameter you must also specify name of
+profiling attribute with parameter
+profile.attribute.
+
+The value of this parameter specifies profiles which should be
+included in the output. You can specify multiple profiles by
+separating them by semicolon. You can change separator character by
+profile.separator
+parameter.
+
+This parameter has effect only when you are using profiling
+stylesheets (profile-docbook.xsl,
+profile-chunk.xsl, …) instead of normal
+ones (docbook.xsl,
+chunk.xsl, …).
+
+
+
+
+
+
+profile.separator
+string
+
+
+profile.separator
+Separator character for compound profile values
+
+
+
+
+<xsl:param name="profile.separator">;</xsl:param>
+
+
+
+Description
+
+Separator character used for compound profile values. See profile.arch
+
+
+
+
+
+HTML Help
+
+
+htmlhelp.encoding
+string
+
+
+htmlhelp.encoding
+Character encoding to use in files for HTML Help compiler.
+
+
+
+
+<xsl:param name="htmlhelp.encoding">iso-8859-1</xsl:param>
+
+
+
+Description
+
+HTML Help Compiler is not UTF-8 aware, so you should always use an
+appropriate single-byte encoding here. Use one from iana, the registered charset values.
+
+
+
+
+
+
+htmlhelp.autolabel
+boolean
+
+
+htmlhelp.autolabel
+Should tree-like ToC use autonumbering feature?
+
+
+
+
+<xsl:param name="htmlhelp.autolabel" select="0"></xsl:param>
+
+
+
+Description
+
+Set this to non-zero to include chapter and section numbers into ToC
+in the left panel.
+
+
+
+
+
+
+htmlhelp.chm
+string
+
+
+htmlhelp.chm
+Filename of output HTML Help file.
+
+
+
+
+<xsl:param name="htmlhelp.chm">htmlhelp.chm</xsl:param>
+
+
+
+Description
+
+Set the name of resulting CHM file
+
+
+
+
+
+
+htmlhelp.default.topic
+string
+
+
+htmlhelp.default.topic
+Name of file with default topic
+
+
+
+
+<xsl:param name="htmlhelp.default.topic"></xsl:param>
+
+
+
+Description
+
+Normally first chunk of document is displayed when you open HTML
+Help file. If you want to display another topic, simply set its
+filename by this parameter.
+
+This is useful especially if you don't generate ToC in front of
+your document and you also hide root element in ToC. E.g.:
+
+<xsl:param name="generate.book.toc" select="0"/>
+<xsl:param name="htmlhelp.hhc.show.root" select="0"/>
+<xsl:param name="htmlhelp.default.topic">pr01.html</xsl:param>
+
+
+
+
+
+
+
+htmlhelp.display.progress
+boolean
+
+
+htmlhelp.display.progress
+Display compile progress?
+
+
+
+
+<xsl:param name="htmlhelp.display.progress" select="1"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to to display compile progress
+
+
+
+
+
+
+
+htmlhelp.hhp
+string
+
+
+htmlhelp.hhp
+Filename of project file.
+
+
+
+
+<xsl:param name="htmlhelp.hhp">htmlhelp.hhp</xsl:param>
+
+
+
+Description
+
+Change this parameter if you want different name of project
+file than htmlhelp.hhp.
+
+
+
+
+
+
+htmlhelp.hhc
+string
+
+
+htmlhelp.hhc
+Filename of TOC file.
+
+
+
+
+<xsl:param name="htmlhelp.hhc">toc.hhc</xsl:param>
+
+
+
+Description
+
+Set the name of the TOC file. The default is toc.hhc.
+
+
+
+
+
+
+htmlhelp.hhk
+string
+
+
+htmlhelp.hhk
+Filename of index file.
+
+
+
+
+<xsl:param name="htmlhelp.hhk">index.hhk</xsl:param>
+
+
+
+Description
+
+set the name of the index file. The default is index.hhk.
+
+
+
+
+
+
+htmlhelp.hhp.tail
+string
+
+
+htmlhelp.hhp.tail
+Additional content for project file.
+
+
+
+
+<xsl:param name="htmlhelp.hhp.tail"></xsl:param>
+
+
+
+Description
+
+If you want to include some additional parameters into project file,
+store appropriate part of project file into this parameter.
+
+
+
+
+
+
+htmlhelp.hhp.window
+string
+
+
+htmlhelp.hhp.window
+Name of default window.
+
+
+
+
+<xsl:param name="htmlhelp.hhp.window">Main</xsl:param>
+
+
+
+Description
+
+Name of default window. If empty no [WINDOWS] section will be
+added to project file.
+
+
+
+
+
+
+htmlhelp.hhp.windows
+string
+
+
+htmlhelp.hhp.windows
+Definition of additional windows
+
+
+
+
+<xsl:param name="htmlhelp.hhp.windows"></xsl:param>
+
+
+
+Description
+
+Content of this parameter is placed at the end of [WINDOWS]
+section of project file. You can use it for defining your own
+addtional windows.
+
+
+
+
+
+
+htmlhelp.enhanced.decompilation
+boolean
+
+
+htmlhelp.enhanced.decompilation
+Allow enhanced decompilation of CHM?
+
+
+
+
+<xsl:param name="htmlhelp.enhanced.decompilation" select="0"></xsl:param>
+
+
+
+Description
+
+When non-zero this parameter enables enhanced decompilation of CHM.
+
+
+
+
+
+
+htmlhelp.enumerate.images
+boolean
+
+
+htmlhelp.enumerate.images
+Should the paths to all used images be added to the project file?
+
+
+
+
+<xsl:param name="htmlhelp.enumerate.images" select="0"></xsl:param>
+
+
+
+Description
+
+Set to non-zero if you insert images into your documents as
+external binary entities or if you are using absolute image paths.
+
+
+
+
+
+
+htmlhelp.force.map.and.alias
+boolean
+
+
+htmlhelp.force.map.and.alias
+Should [MAP] and [ALIAS] sections be added to the project file unconditionally?
+
+
+
+<xsl:param name="htmlhelp.force.map.and.alias" select="0"></xsl:param>
+
+
+Description
+ Set to non-zero if you have your own
+ alias.h and context.h
+ files and you want to include references to them in the project
+ file.
+
+
+
+
+
+htmlhelp.map.file
+string
+
+
+htmlhelp.map.file
+Filename of map file.
+
+
+
+<xsl:param name="htmlhelp.map.file">context.h</xsl:param>
+
+
+Description
+Set the name of map file. The default is
+ context.h. (used for context-sensitive
+ help).
+
+
+
+
+
+htmlhelp.alias.file
+string
+
+
+htmlhelp.alias.file
+Filename of alias file.
+
+
+
+
+<xsl:param name="htmlhelp.alias.file">alias.h</xsl:param>
+
+
+
+Description
+
+Specifies the filename of the alias file (used for context-sensitive help).
+
+
+
+
+
+
+htmlhelp.hhc.section.depth
+integer
+
+
+htmlhelp.hhc.section.depth
+Depth of TOC for sections in a left pane.
+
+
+
+
+<xsl:param name="htmlhelp.hhc.section.depth">5</xsl:param>
+
+
+
+Description
+
+Set the section depth in the left pane of HTML Help viewer.
+
+
+
+
+
+
+htmlhelp.hhc.show.root
+boolean
+
+
+htmlhelp.hhc.show.root
+Should there be an entry for the root element in the ToC?
+
+
+
+
+<xsl:param name="htmlhelp.hhc.show.root" select="1"></xsl:param>
+
+
+
+Description
+
+If set to zero, there will be no entry for the root element in the
+ToC. This is useful when you want to provide the user with an expanded
+ToC as a default.
+
+
+
+
+
+
+htmlhelp.hhc.folders.instead.books
+boolean
+
+
+htmlhelp.hhc.folders.instead.books
+Use folder icons in ToC (instead of book icons)?
+
+
+
+
+<xsl:param name="htmlhelp.hhc.folders.instead.books" select="1"></xsl:param>
+
+
+
+Description
+
+Set non-zero for folder-like icons or zero for book-like icons in the TOC
+ToC. If you want to use folder-like icons you must swith off binary
+ToC using (xref) htmlhelp.hhc.binary.
+
+
+
+
+
+
+
+
+
+
+htmlhelp.hhc.binary
+boolean
+
+
+htmlhelp.hhc.binary
+Generate binary ToC?
+
+
+
+
+<xsl:param name="htmlhelp.hhc.binary" select="1"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to generate a binary TOC. You must create a binary TOC
+if you want to add Prev/Next buttons to toolbar (which is default
+behaviour). Files with binary TOC can't be merged.
+
+
+
+
+
+
+htmlhelp.hhc.width
+integer
+
+
+htmlhelp.hhc.width
+Width of navigation pane
+
+
+
+
+<xsl:param name="htmlhelp.hhc.width"></xsl:param>
+
+
+
+Description
+
+This parameter specifies the width of the navigation pane (containing TOC and
+other navigation tabs) in pixels.
+
+
+
+
+
+
+htmlhelp.title
+string
+
+
+htmlhelp.title
+Title of HTML Help
+
+
+
+
+<xsl:param name="htmlhelp.title"></xsl:param>
+
+
+
+Description
+
+Content of this parameter will be used as a title for generated
+HTML Help. If empty, title will be automatically taken from document.
+
+
+
+
+
+
+htmlhelp.show.menu
+boolean
+
+
+htmlhelp.show.menu
+Should the menu bar be shown?
+
+
+
+
+<xsl:param name="htmlhelp.show.menu" select="0"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to have an application menu bar in your HTML Help window.
+
+
+
+
+
+
+
+htmlhelp.show.toolbar.text
+boolean
+
+
+htmlhelp.show.toolbar.text
+Show text under toolbar buttons?
+
+
+
+
+<xsl:param name="htmlhelp.show.toolbar.text" select="1"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to display texts under toolbar buttons, zero to switch
+off displays.
+
+
+
+
+
+
+htmlhelp.show.advanced.search
+boolean
+
+
+htmlhelp.show.advanced.search
+Should advanced search features be available?
+
+
+
+
+<xsl:param name="htmlhelp.show.advanced.search" select="0"></xsl:param>
+
+
+
+Description
+
+If you want advanced search features in your help, turn this
+parameter to 1.
+
+
+
+
+
+
+htmlhelp.show.favorities
+boolean
+
+
+htmlhelp.show.favorities
+Should the Favorites tab be shown?
+
+
+
+
+<xsl:param name="htmlhelp.show.favorities" select="0"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include a Favorites tab in the navigation pane
+of the help window.
+
+
+
+
+
+
+htmlhelp.button.hideshow
+boolean
+
+
+htmlhelp.button.hideshow
+Should the Hide/Show button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.hideshow" select="1"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Hide/Show button shown on toolbar
+
+
+
+
+
+
+htmlhelp.button.back
+boolean
+
+
+htmlhelp.button.back
+Should the Back button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.back" select="1"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Hide/Show button shown on toolbar
+
+
+
+
+
+
+htmlhelp.button.forward
+boolean
+
+
+htmlhelp.button.forward
+Should the Forward button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.forward" select="0"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Forward button on the toolbar.
+
+
+
+
+
+
+htmlhelp.button.stop
+boolean
+
+
+htmlhelp.button.stop
+Should the Stop button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.stop" select="0"></xsl:param>
+
+
+
+Description
+
+If you want Stop button shown on toolbar, turn this
+parameter to 1.
+
+
+
+
+
+
+htmlhelp.button.refresh
+boolean
+
+
+htmlhelp.button.refresh
+Should the Refresh button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.refresh" select="0"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Stop button on the toolbar.
+
+
+
+
+
+
+htmlhelp.button.home
+boolean
+
+
+htmlhelp.button.home
+Should the Home button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.home" select="0"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Home button on the toolbar.
+
+
+
+
+
+
+htmlhelp.button.home.url
+string
+
+
+htmlhelp.button.home.url
+URL address of page accessible by Home button
+
+
+
+
+<xsl:param name="htmlhelp.button.home.url"></xsl:param>
+
+
+
+Description
+
+URL address of page accessible by Home button.
+
+
+
+
+
+
+htmlhelp.button.options
+boolean
+
+
+htmlhelp.button.options
+Should the Options button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.options" select="1"></xsl:param>
+
+
+
+Description
+
+If you want Options button shown on toolbar, turn this
+parameter to 1.
+
+
+
+
+
+
+htmlhelp.button.print
+boolean
+
+
+htmlhelp.button.print
+Should the Print button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.print" select="1"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Print button on the toolbar.
+
+
+
+
+
+
+
+htmlhelp.button.locate
+boolean
+
+
+htmlhelp.button.locate
+Should the Locate button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.locate" select="0"></xsl:param>
+
+
+
+Description
+
+If you want Locate button shown on toolbar, turn this
+parameter to 1.
+
+
+
+
+
+
+htmlhelp.button.jump1
+boolean
+
+
+htmlhelp.button.jump1
+Should the Jump1 button be shown?
+
+
+
+<xsl:param name="htmlhelp.button.jump1" select="0"></xsl:param>
+
+
+Description
+ Set to non-zero to include the Jump1 button on the toolbar.
+
+
+
+
+
+htmlhelp.button.jump1.url
+string
+
+
+htmlhelp.button.jump1.url
+URL address of page accessible by Jump1 button
+
+
+
+
+<xsl:param name="htmlhelp.button.jump1.url"></xsl:param>
+
+
+
+Description
+
+URL address of page accessible by Jump1 button.
+
+
+
+
+
+
+htmlhelp.button.jump1.title
+string
+
+
+htmlhelp.button.jump1.title
+Title of Jump1 button
+
+
+
+
+<xsl:param name="htmlhelp.button.jump1.title">User1</xsl:param>
+
+
+
+Description
+
+Title of Jump1 button.
+
+
+
+
+
+
+htmlhelp.button.jump2
+boolean
+
+
+htmlhelp.button.jump2
+Should the Jump2 button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.jump2" select="0"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Jump2 button on the toolbar.
+
+
+
+
+
+
+htmlhelp.button.jump2.url
+string
+
+
+htmlhelp.button.jump2.url
+URL address of page accessible by Jump2 button
+
+
+
+
+<xsl:param name="htmlhelp.button.jump2.url"></xsl:param>
+
+
+
+Description
+
+URL address of page accessible by Jump2 button.
+
+
+
+
+
+
+htmlhelp.button.jump2.title
+string
+
+
+htmlhelp.button.jump2.title
+Title of Jump2 button
+
+
+
+
+<xsl:param name="htmlhelp.button.jump2.title">User2</xsl:param>
+
+
+
+Description
+
+Title of Jump2 button.
+
+
+
+
+
+
+htmlhelp.button.next
+boolean
+
+
+htmlhelp.button.next
+Should the Next button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.next" select="1"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Next button on the toolbar.
+
+
+
+
+
+
+htmlhelp.button.prev
+boolean
+
+
+htmlhelp.button.prev
+Should the Prev button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.prev" select="1"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Prev button on the toolbar.
+
+
+
+
+
+
+
+htmlhelp.button.zoom
+boolean
+
+
+htmlhelp.button.zoom
+Should the Zoom button be shown?
+
+
+
+
+<xsl:param name="htmlhelp.button.zoom" select="0"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to include the Zoom button on the toolbar.
+
+
+
+
+
+
+
+htmlhelp.remember.window.position
+boolean
+
+
+htmlhelp.remember.window.position
+Remember help window position?
+
+
+
+
+<xsl:param name="htmlhelp.remember.window.position" select="0"></xsl:param>
+
+
+
+Description
+
+Set to non-zero to remember help window position between starts.
+
+
+
+
+
+
+htmlhelp.window.geometry
+string
+
+
+htmlhelp.window.geometry
+Set initial geometry of help window
+
+
+
+
+<xsl:param name="htmlhelp.window.geometry"></xsl:param>
+
+
+
+Description
+
+This parameter specifies initial position of help
+window. E.g.
+
+<xsl:param name="htmlhelp.window.geometry">[160,64,992,704]</xsl:param>
+
+
+
+
+
+
+htmlhelp.use.hhk
+boolean
+
+
+htmlhelp.use.hhk
+Should the index be built using the HHK file?
+
+
+
+
+<xsl:param name="htmlhelp.use.hhk" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the index is created using the HHK file (instead of using object
+elements in the HTML files). For more information, see Generating an index.
+
+
+
+
+
+htmlhelp.only
+boolean
+
+
+htmlhelp.only
+Should only project files be generated?
+
+
+
+
+<xsl:param name="htmlhelp.only" select="0"></xsl:param>
+
+
+
+Description
+
+
+Set to non-zero if you want to play with various HTML Help parameters
+and you don't need to regenerate all HTML files. This setting will not
+process whole document, only project files (hhp, hhc, hhk,...) will be
+generated.
+
+
+
+
+
+
+Eclipse Help Platform
+
+
+eclipse.autolabel
+boolean
+
+
+eclipse.autolabel
+Should tree-like ToC use autonumbering feature?
+
+
+
+
+<xsl:param name="eclipse.autolabel" select="0"></xsl:param>
+
+
+
+Description
+
+If you want to include chapter and section numbers into ToC in
+the left panel, set this parameter to 1.
+
+
+
+
+
+
+eclipse.plugin.name
+string
+
+
+eclipse.plugin.name
+Eclipse Help plugin name
+
+
+
+
+<xsl:param name="eclipse.plugin.name">DocBook Online Help Sample</xsl:param>
+
+
+
+Description
+
+Eclipse Help plugin name.
+
+
+
+
+
+
+eclipse.plugin.id
+string
+
+
+eclipse.plugin.id
+Eclipse Help plugin id
+
+
+
+
+<xsl:param name="eclipse.plugin.id">com.example.help</xsl:param>
+
+
+
+Description
+
+Eclipse Help plugin id. You should change this id to something
+unique for each help.
+
+
+
+
+
+
+eclipse.plugin.provider
+string
+
+
+eclipse.plugin.provider
+Eclipse Help plugin provider name
+
+
+
+
+<xsl:param name="eclipse.plugin.provider">Example provider</xsl:param>
+
+
+
+Description
+
+Eclipse Help plugin provider name.
+
+
+
+
+
+JavaHelp
+
+
+javahelp.encoding
+string
+
+
+javahelp.encoding
+Character encoding to use in control files for JavaHelp.
+
+
+
+
+<xsl:param name="javahelp.encoding">iso-8859-1</xsl:param>
+
+
+
+Description
+
+JavaHelp crashes on some characters when written as character
+references. In that case you can use this parameter to select an appropriate encoding.
+
+
+
+
+
+
+
+
+Localization
+
+
+l10n.gentext.language
+string
+
+
+l10n.gentext.language
+Sets the gentext language
+
+
+
+
+<xsl:param name="l10n.gentext.language"></xsl:param>
+
+
+
+Description
+
+If this parameter is set to any value other than the empty string, its
+value will be used as the value for the language when generating text. Setting
+l10n.gentext.language overrides any settings within the
+document being formatted.
+
+It's much more likely that you might want to set the
+l10n.gentext.default.language parameter.
+
+
+
+
+
+
+ l10n.gentext.default.language
+ string
+
+
+ l10n.gentext.default.language
+ Sets the default language for generated text
+
+
+
+
+<xsl:param name="l10n.gentext.default.language">en</xsl:param>
+
+
+
+Description
+
+The value of the l10n.gentext.default.language
+parameter is used as the language for generated text if no setting is provided
+in the source document.
+
+
+
+
+
+
+l10n.gentext.use.xref.language
+boolean
+
+
+l10n.gentext.use.xref.language
+Use the language of target when generating cross-reference text?
+
+
+
+
+<xsl:param name="l10n.gentext.use.xref.language" select="0"></xsl:param>
+
+
+
+Description
+
+If non-zero, the language of the target will be used when
+generating cross reference text. Usually, the current
+language is used when generating text (that is, the language of the
+element that contains the cross-reference element). But setting this parameter
+allows the language of the element pointed to to control
+the generated text.
+
+Consider the following example:
+
+
+<para lang="en">See also <xref linkend="chap3"/>.</para>
+
+
+
+Suppose that Chapter 3 happens to be written in German.
+If l10n.gentext.use.xref.language is non-zero, the
+resulting text will be something like this:
+
+
+See also Kapital 3.
+
+
+Where the more traditional rendering would be:
+
+
+See also Chapter 3.
+
+
+
+
+
+
+
+l10n.lang.value.rfc.compliant
+boolean
+
+
+l10n.lang.value.rfc.compliant
+Make value of lang attribute RFC compliant?
+
+
+
+
+<xsl:param name="l10n.lang.value.rfc.compliant" select="1"></xsl:param>
+
+
+
+Description
+
+If non-zero, ensure that the values for all lang attributes in HTML output are RFC
+compliantSection 8.1.1, Language Codes, in the HTML 4.0 Recommendation states that:
+
+
[RFC1766] defines and explains the language codes
+that must be used in HTML documents.
+Briefly, language codes consist of a primary code and a possibly
+empty series of subcodes:
+
+language-code = primary-code ( "-" subcode )*
+
+And in RFC 1766, Tags for the Identification
+of Languages, the EBNF for "language tag" is given as:
+
+Language-Tag = Primary-tag *( "-" Subtag )
+Primary-tag = 1*8ALPHA
+Subtag = 1*8ALPHA
+
+
+.
+
+by taking any underscore characters in any lang values found in source documents, and
+replacing them with hyphen characters in output HTML files. For
+example, zh_CN in a source document becomes
+zh-CN in the HTML output form that source.
+
+
+This parameter does not cause any case change in lang values, because RFC 1766
+explicitly states that all "language tags" (as it calls them) "are
+to be treated as case insensitive".
+
+
+
+
+
+
+
+The Stylesheet
+
+The param.xsl stylesheet is just a wrapper
+around all these parameters.
+
+
+
+<!-- This file is generated from param.xweb -->
+
+<xsl:stylesheet exclude-result-prefixes="src" version="1.0">
+
+<!-- ********************************************************************
+ $Id: param.xweb 8092 2008-07-18 21:26:36Z kosek $
+ ********************************************************************
+
+ This file is part of the XSL DocBook Stylesheet distribution.
+ See ../README or http://docbook.sf.net/release/xsl/current/ for
+ copyright and other information.
+
+ ******************************************************************** -->
+
+<src:fragref linkend="admon.graphics.extension.frag"></src:fragref>
+<src:fragref linkend="admon.graphics.frag"></src:fragref>
+<src:fragref linkend="admon.graphics.path.frag"></src:fragref>
+<src:fragref linkend="admon.style.frag"></src:fragref>
+<src:fragref linkend="admon.textlabel.frag"></src:fragref>
+<src:fragref linkend="annotate.toc.frag"></src:fragref>
+<src:fragref linkend="annotation.css.frag"></src:fragref>
+<src:fragref linkend="annotation.js.frag"></src:fragref>
+<src:fragref linkend="annotation.graphic.open.frag"></src:fragref>
+<src:fragref linkend="annotation.graphic.close.frag"></src:fragref>
+<src:fragref linkend="annotation.support.frag"></src:fragref>
+<src:fragref linkend="appendix.autolabel.frag"></src:fragref>
+<src:fragref linkend="author.othername.in.middle.frag"></src:fragref>
+<src:fragref linkend="autotoc.label.separator.frag"></src:fragref>
+<src:fragref linkend="autotoc.label.in.hyperlink.frag"></src:fragref>
+<src:fragref linkend="base.dir.frag"></src:fragref>
+<src:fragref linkend="biblioentry.item.separator.frag"></src:fragref>
+<src:fragref linkend="bibliography.collection.frag"></src:fragref>
+<src:fragref linkend="bibliography.numbered.frag"></src:fragref>
+<src:fragref linkend="bibliography.style.frag"></src:fragref>
+<src:fragref linkend="blurb.on.titlepage.enabled.frag"></src:fragref>
+<src:fragref linkend="bridgehead.in.toc.frag"></src:fragref>
+<src:fragref linkend="callout.defaultcolumn.frag"></src:fragref>
+<src:fragref linkend="callout.graphics.extension.frag"></src:fragref>
+<src:fragref linkend="callout.graphics.frag"></src:fragref>
+<src:fragref linkend="callout.graphics.number.limit.frag"></src:fragref>
+<src:fragref linkend="callout.graphics.path.frag"></src:fragref>
+<src:fragref linkend="callout.list.table.frag"></src:fragref>
+<src:fragref linkend="callout.unicode.frag"></src:fragref>
+<src:fragref linkend="callout.unicode.number.limit.frag"></src:fragref>
+<src:fragref linkend="callout.unicode.start.character.frag"></src:fragref>
+<src:fragref linkend="callouts.extension.frag"></src:fragref>
+<src:fragref linkend="chapter.autolabel.frag"></src:fragref>
+<src:fragref linkend="chunk.append.frag"></src:fragref>
+<src:fragref linkend="chunk.first.sections.frag"></src:fragref>
+<src:fragref linkend="chunk.quietly.frag"></src:fragref>
+<src:fragref linkend="chunk.section.depth.frag"></src:fragref>
+<src:fragref linkend="chunk.toc.frag"></src:fragref>
+<src:fragref linkend="chunk.tocs.and.lots.frag"></src:fragref>
+<src:fragref linkend="chunk.tocs.and.lots.has.title.frag"></src:fragref>
+<src:fragref linkend="chunk.separate.lots.frag"></src:fragref>
+<src:fragref linkend="citerefentry.link.frag"></src:fragref>
+<src:fragref linkend="collect.xref.targets.frag"></src:fragref>
+<src:fragref linkend="component.label.includes.part.label.frag"></src:fragref>
+<src:fragref linkend="contrib.inline.enabled.frag"></src:fragref>
+<src:fragref linkend="css.decoration.frag"></src:fragref>
+<src:fragref linkend="current.docid.frag"></src:fragref>
+<src:fragref linkend="default.float.class.frag"></src:fragref>
+<src:fragref linkend="default.image.width.frag"></src:fragref>
+<src:fragref linkend="default.table.width.frag"></src:fragref>
+<src:fragref linkend="default.table.frame.frag"></src:fragref>
+<src:fragref linkend="draft.mode.frag"></src:fragref>
+<src:fragref linkend="draft.watermark.image.frag"></src:fragref>
+<src:fragref linkend="ebnf.table.bgcolor.frag"></src:fragref>
+<src:fragref linkend="ebnf.table.border.frag"></src:fragref>
+<src:fragref linkend="ebnf.assignment.frag"></src:fragref>
+<src:fragref linkend="ebnf.statement.terminator.frag"></src:fragref>
+<src:fragref linkend="eclipse.autolabel.frag"></src:fragref>
+<src:fragref linkend="eclipse.plugin.name.frag"></src:fragref>
+<src:fragref linkend="eclipse.plugin.id.frag"></src:fragref>
+<src:fragref linkend="eclipse.plugin.provider.frag"></src:fragref>
+<src:fragref linkend="editedby.enabled.frag"></src:fragref>
+<src:fragref linkend="email.delimiters.enabled.frag"></src:fragref>
+<src:fragref linkend="emphasis.propagates.style.frag"></src:fragref>
+<src:fragref linkend="entry.propagates.style.frag"></src:fragref>
+<src:fragref linkend="firstterm.only.link.frag"></src:fragref>
+<src:fragref linkend="footer.rule.frag"></src:fragref>
+<src:fragref linkend="footnote.number.format.frag"></src:fragref>
+<src:fragref linkend="footnote.number.symbols.frag"></src:fragref>
+<src:fragref linkend="formal.procedures.frag"></src:fragref>
+<src:fragref linkend="formal.title.placement.frag"></src:fragref>
+<src:fragref linkend="funcsynopsis.decoration.frag"></src:fragref>
+<src:fragref linkend="funcsynopsis.style.frag"></src:fragref>
+<src:fragref linkend="function.parens.frag"></src:fragref>
+<src:fragref linkend="generate.id.attributes.frag"></src:fragref>
+<src:fragref linkend="generate.index.frag"></src:fragref>
+<src:fragref linkend="generate.legalnotice.link.frag"></src:fragref>
+<src:fragref linkend="generate.revhistory.link.frag"></src:fragref>
+<src:fragref linkend="generate.manifest.frag"></src:fragref>
+<src:fragref linkend="generate.meta.abstract.frag"></src:fragref>
+<src:fragref linkend="generate.section.toc.level.frag"></src:fragref>
+<src:fragref linkend="generate.toc.frag"></src:fragref>
+<src:fragref linkend="glossary.collection.frag"></src:fragref>
+<src:fragref linkend="glossary.sort.frag"></src:fragref>
+<src:fragref linkend="glossentry.show.acronym.frag"></src:fragref>
+<src:fragref linkend="glossterm.auto.link.frag"></src:fragref>
+<src:fragref linkend="graphic.default.extension.frag"></src:fragref>
+<src:fragref linkend="graphicsize.extension.frag"></src:fragref>
+<src:fragref linkend="graphicsize.use.img.src.path.frag"></src:fragref>
+<src:fragref linkend="header.rule.frag"></src:fragref>
+<src:fragref linkend="highlight.default.language.frag"></src:fragref>
+<src:fragref linkend="highlight.source.frag"></src:fragref>
+<src:fragref linkend="highlight.xslthl.config.frag"></src:fragref>
+<src:fragref linkend="html.append.frag"></src:fragref>
+<src:fragref linkend="html.base.frag"></src:fragref>
+<src:fragref linkend="html.cellpadding.frag"></src:fragref>
+<src:fragref linkend="html.cellspacing.frag"></src:fragref>
+<src:fragref linkend="html.cleanup.frag"></src:fragref>
+<src:fragref linkend="html.ext.frag"></src:fragref>
+<src:fragref linkend="html.extra.head.links.frag"></src:fragref>
+<src:fragref linkend="html.head.legalnotice.link.types.frag"></src:fragref>
+<src:fragref linkend="html.head.legalnotice.link.multiple.frag"></src:fragref>
+<src:fragref linkend="html.longdesc.frag"></src:fragref>
+<src:fragref linkend="html.longdesc.link.frag"></src:fragref>
+<src:fragref linkend="html.stylesheet.frag"></src:fragref>
+<src:fragref linkend="html.stylesheet.type.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.alias.file.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.autolabel.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.back.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.forward.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.hideshow.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.home.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.home.url.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.jump1.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.jump1.title.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.jump1.url.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.jump2.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.jump2.title.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.jump2.url.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.locate.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.next.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.options.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.prev.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.print.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.refresh.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.stop.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.button.zoom.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.chm.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.default.topic.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.display.progress.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.encoding.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.enhanced.decompilation.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.enumerate.images.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.force.map.and.alias.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhc.binary.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhc.folders.instead.books.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhc.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhc.section.depth.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhc.show.root.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhc.width.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhk.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhp.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhp.tail.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhp.window.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.hhp.windows.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.map.file.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.only.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.remember.window.position.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.show.advanced.search.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.show.favorities.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.show.menu.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.show.toolbar.text.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.title.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.use.hhk.frag"></src:fragref>
+<src:fragref linkend="htmlhelp.window.geometry.frag"></src:fragref>
+<src:fragref linkend="img.src.path.frag"></src:fragref>
+<src:fragref linkend="id.warnings.frag"></src:fragref>
+<src:fragref linkend="index.method.frag"></src:fragref>
+<src:fragref linkend="index.on.role.frag"></src:fragref>
+<src:fragref linkend="index.on.type.frag"></src:fragref>
+<src:fragref linkend="index.number.separator.frag"></src:fragref>
+<src:fragref linkend="index.term.separator.frag"></src:fragref>
+<src:fragref linkend="index.range.separator.frag"></src:fragref>
+<src:fragref linkend="index.prefer.titleabbrev.frag"></src:fragref>
+<src:fragref linkend="ignore.image.scaling.frag"></src:fragref>
+<src:fragref linkend="inherit.keywords.frag"></src:fragref>
+<src:fragref linkend="insert.xref.page.number.frag"></src:fragref>
+<src:fragref linkend="javahelp.encoding.frag"></src:fragref>
+<src:fragref linkend="keep.relative.image.uris.frag"></src:fragref>
+<src:fragref linkend="l10n.gentext.default.language.frag"></src:fragref>
+<src:fragref linkend="l10n.gentext.language.frag"></src:fragref>
+<src:fragref linkend="l10n.gentext.use.xref.language.frag"></src:fragref>
+<src:fragref linkend="l10n.lang.value.rfc.compliant.frag"></src:fragref>
+<src:fragref linkend="label.from.part.frag"></src:fragref>
+<src:fragref linkend="linenumbering.everyNth.frag"></src:fragref>
+<src:fragref linkend="linenumbering.extension.frag"></src:fragref>
+<src:fragref linkend="linenumbering.separator.frag"></src:fragref>
+<src:fragref linkend="linenumbering.width.frag"></src:fragref>
+<src:fragref linkend="link.mailto.url.frag"></src:fragref>
+<src:fragref linkend="make.graphic.viewport.frag"></src:fragref>
+<src:fragref linkend="make.single.year.ranges.frag"></src:fragref>
+<src:fragref linkend="make.valid.html.frag"></src:fragref>
+<src:fragref linkend="make.year.ranges.frag"></src:fragref>
+<src:fragref linkend="manifest.frag"></src:fragref>
+<src:fragref linkend="manifest.in.base.dir.frag"></src:fragref>
+<src:fragref linkend="manual.toc.frag"></src:fragref>
+<src:fragref linkend="menuchoice.menu.separator.frag"></src:fragref>
+<src:fragref linkend="menuchoice.separator.frag"></src:fragref>
+<src:fragref linkend="navig.graphics.extension.frag"></src:fragref>
+<src:fragref linkend="navig.graphics.frag"></src:fragref>
+<src:fragref linkend="navig.graphics.path.frag"></src:fragref>
+<src:fragref linkend="navig.showtitles.frag"></src:fragref>
+<src:fragref linkend="nominal.image.depth.frag"></src:fragref>
+<src:fragref linkend="nominal.image.width.frag"></src:fragref>
+<src:fragref linkend="nominal.table.width.frag"></src:fragref>
+<src:fragref linkend="olink.base.uri.frag"></src:fragref>
+<src:fragref linkend="olink.debug.frag"></src:fragref>
+<src:fragref linkend="olink.properties.frag"></src:fragref>
+<src:fragref linkend="insert.olink.page.number.frag"></src:fragref>
+<src:fragref linkend="insert.olink.pdf.frag.frag"></src:fragref>
+<src:fragref linkend="prefer.internal.olink.frag"></src:fragref>
+<src:fragref linkend="olink.lang.fallback.sequence.frag"></src:fragref>
+<src:fragref linkend="olink.doctitle.frag"></src:fragref>
+<src:fragref linkend="olink.fragid.frag"></src:fragref>
+<src:fragref linkend="olink.outline.ext.frag"></src:fragref>
+<src:fragref linkend="olink.pubid.frag"></src:fragref>
+<src:fragref linkend="olink.resolver.frag"></src:fragref>
+<src:fragref linkend="olink.sysid.frag"></src:fragref>
+<src:fragref linkend="abstract.notitle.enabled.frag"></src:fragref>
+<src:fragref linkend="othercredit.like.author.enabled.frag"></src:fragref>
+<src:fragref linkend="para.propagates.style.frag"></src:fragref>
+<src:fragref linkend="part.autolabel.frag"></src:fragref>
+<src:fragref linkend="phrase.propagates.style.frag"></src:fragref>
+<src:fragref linkend="pixels.per.inch.frag"></src:fragref>
+<src:fragref linkend="points.per.em.frag"></src:fragref>
+<src:fragref linkend="preface.autolabel.frag"></src:fragref>
+<src:fragref linkend="preferred.mediaobject.role.frag"></src:fragref>
+<src:fragref linkend="process.empty.source.toc.frag"></src:fragref>
+<src:fragref linkend="process.source.toc.frag"></src:fragref>
+<src:fragref linkend="profile.arch.frag"></src:fragref>
+<src:fragref linkend="profile.audience.frag"></src:fragref>
+<src:fragref linkend="profile.attribute.frag"></src:fragref>
+<src:fragref linkend="profile.condition.frag"></src:fragref>
+<src:fragref linkend="profile.conformance.frag"></src:fragref>
+<src:fragref linkend="profile.lang.frag"></src:fragref>
+<src:fragref linkend="profile.os.frag"></src:fragref>
+<src:fragref linkend="profile.revision.frag"></src:fragref>
+<src:fragref linkend="profile.revisionflag.frag"></src:fragref>
+<src:fragref linkend="profile.role.frag"></src:fragref>
+<src:fragref linkend="profile.security.frag"></src:fragref>
+<src:fragref linkend="profile.separator.frag"></src:fragref>
+<src:fragref linkend="profile.status.frag"></src:fragref>
+<src:fragref linkend="profile.userlevel.frag"></src:fragref>
+<src:fragref linkend="profile.value.frag"></src:fragref>
+<src:fragref linkend="profile.vendor.frag"></src:fragref>
+<src:fragref linkend="profile.wordsize.frag"></src:fragref>
+<src:fragref linkend="punct.honorific.frag"></src:fragref>
+<src:fragref linkend="qanda.defaultlabel.frag"></src:fragref>
+<src:fragref linkend="qanda.inherit.numeration.frag"></src:fragref>
+<src:fragref linkend="qanda.in.toc.frag"></src:fragref>
+<src:fragref linkend="qanda.nested.in.toc.frag"></src:fragref>
+<src:fragref linkend="qandadiv.autolabel.frag"></src:fragref>
+<src:fragref linkend="refentry.generate.name.frag"></src:fragref>
+<src:fragref linkend="refentry.generate.title.frag"></src:fragref>
+<src:fragref linkend="refentry.separator.frag"></src:fragref>
+<src:fragref linkend="refentry.xref.manvolnum.frag"></src:fragref>
+<src:fragref linkend="reference.autolabel.frag"></src:fragref>
+<src:fragref linkend="refclass.suppress.frag"></src:fragref>
+<src:fragref linkend="root.filename.frag"></src:fragref>
+<src:fragref linkend="rootid.frag"></src:fragref>
+<src:fragref linkend="runinhead.default.title.end.punct.frag"></src:fragref>
+<src:fragref linkend="runinhead.title.end.punct.frag"></src:fragref>
+<src:fragref linkend="section.autolabel.frag"></src:fragref>
+<src:fragref linkend="section.autolabel.max.depth.frag"></src:fragref>
+<src:fragref linkend="section.label.includes.component.label.frag"></src:fragref>
+<src:fragref linkend="segmentedlist.as.table.frag"></src:fragref>
+<src:fragref linkend="shade.verbatim.frag"></src:fragref>
+<src:fragref linkend="shade.verbatim.style.frag"></src:fragref>
+<src:fragref linkend="show.comments.frag"></src:fragref>
+<src:fragref linkend="show.revisionflag.frag"></src:fragref>
+<src:fragref linkend="simplesect.in.toc.frag"></src:fragref>
+<src:fragref linkend="spacing.paras.frag"></src:fragref>
+<src:fragref linkend="suppress.footer.navigation.frag"></src:fragref>
+<src:fragref linkend="suppress.header.navigation.frag"></src:fragref>
+<src:fragref linkend="suppress.navigation.frag"></src:fragref>
+<src:fragref linkend="table.borders.with.css.frag"></src:fragref>
+<src:fragref linkend="table.cell.border.color.frag"></src:fragref>
+<src:fragref linkend="table.cell.border.style.frag"></src:fragref>
+<src:fragref linkend="table.cell.border.thickness.frag"></src:fragref>
+<src:fragref linkend="table.footnote.number.format.frag"></src:fragref>
+<src:fragref linkend="table.footnote.number.symbols.frag"></src:fragref>
+<src:fragref linkend="table.frame.border.color.frag"></src:fragref>
+<src:fragref linkend="table.frame.border.style.frag"></src:fragref>
+<src:fragref linkend="table.frame.border.thickness.frag"></src:fragref>
+<src:fragref linkend="tablecolumns.extension.frag"></src:fragref>
+<src:fragref linkend="target.database.document.frag"></src:fragref>
+<src:fragref linkend="targets.filename.frag"></src:fragref>
+<src:fragref linkend="textdata.default.encoding.frag"></src:fragref>
+<src:fragref linkend="tex.math.delims.frag"></src:fragref>
+<src:fragref linkend="tex.math.file.frag"></src:fragref>
+<src:fragref linkend="tex.math.in.alt.frag"></src:fragref>
+<src:fragref linkend="textinsert.extension.frag"></src:fragref>
+<src:fragref linkend="toc.list.type.frag"></src:fragref>
+<src:fragref linkend="toc.section.depth.frag"></src:fragref>
+<src:fragref linkend="toc.max.depth.frag"></src:fragref>
+<src:fragref linkend="ulink.target.frag"></src:fragref>
+<src:fragref linkend="use.embed.for.svg.frag"></src:fragref>
+<src:fragref linkend="use.extensions.frag"></src:fragref>
+<src:fragref linkend="use.id.as.filename.frag"></src:fragref>
+<src:fragref linkend="use.local.olink.style.frag"></src:fragref>
+<src:fragref linkend="use.role.as.xrefstyle.frag"></src:fragref>
+<src:fragref linkend="use.role.for.mediaobject.frag"></src:fragref>
+<src:fragref linkend="use.svg.frag"></src:fragref>
+<src:fragref linkend="variablelist.as.table.frag"></src:fragref>
+<src:fragref linkend="variablelist.term.separator.frag"></src:fragref>
+<src:fragref linkend="variablelist.term.break.after.frag"></src:fragref>
+<src:fragref linkend="xref.with.number.and.title.frag"></src:fragref>
+<src:fragref linkend="xref.label-title.separator.frag"></src:fragref>
+<src:fragref linkend="xref.label-page.separator.frag"></src:fragref>
+<src:fragref linkend="xref.title-page.separator.frag"></src:fragref>
+
+</xsl:stylesheet>
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/param.xsl b/doc/reference/lib/docbook-xsl-snapshot/html/param.xsl
new file mode 100644
index 00000000..d977849a
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/param.xsl
@@ -0,0 +1,413 @@
+
+
+
+
+
+
+.png
+
+images/
+
+ margin-left: 0.5in; margin-right: 0.5in;
+
+
+
+
+/* ======================================================================
+ Annotations
+*/
+
+div.annotation-list { visibility: hidden;
+ }
+
+div.annotation-nocss { position: absolute;
+ visibility: hidden;
+ }
+
+div.annotation-popup { position: absolute;
+ z-index: 4;
+ visibility: hidden;
+ padding: 0px;
+ margin: 2px;
+ border-style: solid;
+ border-width: 1px;
+ width: 200px;
+ background-color: white;
+ }
+
+div.annotation-title { padding: 1px;
+ font-weight: bold;
+ border-bottom-style: solid;
+ border-bottom-width: 1px;
+ color: white;
+ background-color: black;
+ }
+
+div.annotation-body { padding: 2px;
+ }
+
+div.annotation-body p { margin-top: 0px;
+ padding-top: 0px;
+ }
+
+div.annotation-close { position: absolute;
+ top: 2px;
+ right: 2px;
+ }
+
+
+
+http://docbook.sourceforge.net/release/script/AnchorPosition.js http://docbook.sourceforge.net/release/script/PopupWindow.js
+
+http://docbook.sourceforge.net/release/images/annot-open.png
+
+http://docbook.sourceforge.net/release/images/annot-close.png
+
+A
+
+.
+
+
+.
+http://docbook.sourceforge.net/release/bibliography/bibliography.xml
+
+
+normal
+
+
+60
+.png
+
+
+15
+
+images/callouts/
+
+
+10
+10102
+
+
+
+
+
+
+
+
+
+
+
+no
+
+1
+
+
+
+
+ left
+ before
+
+
+
+
+all
+maybe
+http://docbook.sourceforge.net/release/images/draft.png
+#F5DCB3
+
+
+::=
+
+
+
+
+
+DocBook Online Help Sample
+com.example.help
+Example provider
+1
+
+
+
+
+
+1
+
+
+
+figure before
+example before
+equation before
+table before
+procedure before
+task before
+
+
+kr
+
+
+
+
+
+
+
+
+
+appendix toc,title
+article/appendix nop
+article title
+book toc,title
+chapter title
+part toc,title
+preface toc,title
+qandadiv toc
+qandaset toc
+reference toc,title
+sect1 toc
+sect2 toc
+sect3 toc
+sect4 toc
+sect5 toc
+section toc
+set toc,title
+
+
+
+
+no
+
+
+
+
+
+
+
+
+
+
+
+
+
+.html
+
+copyright
+
+
+
+
+text/css
+alias.h
+
+
+
+
+
+
+
+User1
+
+
+User2
+
+
+
+
+
+
+
+
+
+htmlhelp.chm
+
+
+iso-8859-1
+
+
+
+
+
+toc.hhc
+5
+
+
+index.hhk
+htmlhelp.hhp
+
+Main
+
+context.h
+
+
+
+
+
+
+
+
+
+
+
+basic
+
+
+
+
+
+
+
+
+no
+iso-8859-1
+
+
+en
+
+
+
+
+5
+
+
+3
+
+
+
+
+
+ HTML.manifest
+
+
+
+ →
++
+.gif
+
+images/
+1
+
+
+6in
+
+
+
+ replace
+
+no
+
+
+
+no
+fragid=
+.olink
+pubid
+ /cgi-bin/olink
+sysid
+
+0
+
+I
+
+90
+10
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+;
+
+
+
+
+
+.
+number
+
+
+
+
+
+
+
+
+ I
+
+index
+
+.
+.!?:
+
+8
+
+
+
+
+ 0
+ #E0E0E0
+
+
+
+
+
+
+0
+
+
+
+
+
+solid
+0.5pt
+a
+
+
+
+solid
+0.5pt
+
+ olinkdb.xml
+target.db
+
+
+tex-math-equations.tex
+
+
+dl
+2
+8
+_top
+
+
+
+
+
+
+
+
+,
+0
+
+:
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/pi.xml b/doc/reference/lib/docbook-xsl-snapshot/html/pi.xml
new file mode 100644
index 00000000..25c33062
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/pi.xml
@@ -0,0 +1,1113 @@
+
+
+HTML Processing Instruction Reference
+
+ $Id: pi.xsl 8097 2008-08-03 13:20:21Z mzjn $
+
+
+
+ Introduction
+
+This is generated reference documentation for all
+ user-specifiable processing instructions (PIs) in the DocBook
+ XSL stylesheets for HTML output.
+
+
+You add these PIs at particular points in a document to
+ cause specific “exceptions” to formatting/output behavior. To
+ make global changes in formatting/output behavior across an
+ entire document, it’s better to do it by setting an
+ appropriate stylesheet parameter (if there is one).
+
+
+
+
+
+
+
+
+dbhtml_background-color
+Sets background color for an image
+
+
+
+ dbhtml background-color="color"
+
+
+Description
+
+Use the dbhtml background-color PI before or
+ after an image (graphic, inlinegraphic,
+ imagedata, or videodata element) as a
+ sibling to the element, to set a background color for the
+ image.
+
+ Parameters
+
+
+ background-color="color"
+
+
+An HTML color value
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Background color
+
+
+
+
+
+dbhtml_bgcolor
+Sets background color on a CALS table row or table cell
+
+
+
+ dbhtml bgcolor="color"
+
+
+Description
+
+Use the dbhtml bgcolor PI as child of a CALS table row
+ or cell to set a background color for that table row or cell.
+
+ Parameters
+
+
+ bgcolor="color"
+
+
+An HTML color value
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Cell background color
+
+
+
+
+
+dbhtml_cellpadding
+Specifies cellpadding in CALS table or qandaset output
+
+
+
+ dbhtml cellpadding="number"
+
+
+Description
+
+Use the dbhtml cellpadding PI as a child of a
+ CALS table or qandaset to specify the value
+ for the HTML cellpadding attribute in the
+ output HTML table.
+
+ Parameters
+
+
+ cellpadding="number"
+
+
+Specifies the cellpadding
+
+
+
+
+
+ Related Global Parameters
+
+html.cellpadding
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Cell spacing and cell padding,
+ Q and A formatting
+
+
+
+
+
+dbhtml_cellspacing
+Specifies cellspacing in CALS table or qandaset output
+
+
+
+ dbhtml cellspacing="number"
+
+
+Description
+
+Use the dbhtml cellspacing PI as a child of a
+ CALS table or qandaset to specify the value
+ for the HTML cellspacing attribute in the
+ output HTML table.
+
+ Parameters
+
+
+ cellspacing="number"
+
+
+Specifies the cellspacing
+
+
+
+
+
+ Related Global Parameters
+
+html.cellspacing
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Cell spacing and cell padding,
+ Q and A formatting
+
+
+
+
+
+dbhtml_class
+Set value of the class attribute for a CALS table row
+
+
+
+ dbhtml class="name"
+
+
+Description
+
+Use the dbhtml class PI as a child of a
+ row to specify a class
+ attribute and value in the HTML output for that row.
+
+ Parameters
+
+
+ class="name"
+
+
+Specifies the class name
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Table styles in HTML output
+
+
+
+
+
+dbhtml_dir
+Specifies a directory name in which to write files
+
+
+
+ dbhtml dir="path"
+
+
+Description
+
+When chunking output, use the dbhtml dir PI
+ as a child of a chunk source to cause the output of that
+ chunk to be written to the specified directory; also, use it
+ as a child of a mediaobject to specify a
+ directory into which any long-description files for that
+ mediaobject will be written.
+
+ Parameters
+
+
+ dir="path"
+
+
+Specifies the pathname for the directory
+
+
+
+
+
+ Related Global Parameters
+
+base.dir
+
+ Related Information in DocBook XSL: The Complete Guide
+
+dbhtml dir processing instruction
+
+
+
+
+
+dbhtml_filename
+Specifies a filename for a chunk
+
+
+
+ dbhtml filename="filename"
+
+
+Description
+
+When chunking output, use the dbhtml filename
+ PI as a child of a chunk source to specify a filename for
+ the output file for that chunk.
+
+ Parameters
+
+
+ filename="path"
+
+
+Specifies the filename for the file
+
+
+
+
+
+ Related Global Parameters
+
+use.id.as.filename
+
+ Related Information in DocBook XSL: The Complete Guide
+
+dbhtml filenames
+
+
+
+
+
+dbhtml_funcsynopsis-style
+Specifies presentation style for a funcsynopsis
+
+
+
+ dbhtml funcsynopsis-style="kr"|"ansi"
+
+
+Description
+
+Use the dbhtml funcsynopsis-style PI as a child of
+ a funcsynopsis or anywhere within a funcsynopsis
+ to control the presentation style for output of all
+ funcprototype instances within that funcsynopsis.
+
+ Parameters
+
+
+ funcsynopsis-style="kr"
+
+
+Displays funcprototype output in K&R style
+
+
+
+ funcsynopsis-style="ansi"
+
+
+Displays funcprototype output in ANSI style
+
+
+
+
+
+ Related Global Parameters
+
+funcsynopsis.style
+
+
+
+
+
+dbhtml_img.src.path
+Specifies a path to the location of an image file
+
+
+
+ dbhtml img.src.path="path"
+
+
+Description
+
+Use the dbhtml img.src.path PI before or
+ after an image (graphic,
+ inlinegraphic, imagedata, or
+ videodata element) as a sibling to the element,
+ to specify a path to the location of the image; in HTML
+ output, the value specified for the
+ img.src.path attribute is prepended to the
+ filename.
+
+ Parameters
+
+
+ img.src.path="path"
+
+
+Specifies the pathname to prepend to the name of the image file
+
+
+
+
+
+ Related Global Parameters
+
+img.src.path
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Using fileref
+
+
+
+
+
+dbhtml_label-width
+Specifies the label width for a qandaset
+
+
+
+ dbhtml label-width="width"
+
+
+Description
+
+Use the dbhtml label-width PI as a child of a
+ qandaset to specify the width of labels.
+
+ Parameters
+
+
+ label-width="width"
+
+
+Specifies the label width (including units)
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Q and A formatting
+
+
+
+
+
+dbhtml_linenumbering.everyNth
+Specifies interval for line numbers in verbatims
+
+
+
+ dbhtml linenumbering.everyNth="N"
+
+
+Description
+
+Use the dbhtml linenumbering.everyNth PI as a child
+ of a “verbatim” element – programlisting,
+ screen, synopsis — to specify
+ the interval at which lines are numbered.
+
+ Parameters
+
+
+ linenumbering.everyNth="N"
+
+
+Specifies numbering interval; a number is output
+ before every Nth line
+
+
+
+
+
+ Related Global Parameters
+
+linenumbering.everyNth
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Line numbering
+
+
+
+
+
+dbhtml_linenumbering.separator
+Specifies separator text for line numbers in verbatims
+
+
+
+ dbhtml linenumbering.separator="text"
+
+
+Description
+
+Use the dbhtml linenumbering.separator PI as a child
+ of a “verbatim” element – programlisting,
+ screen, synopsis — to specify
+ the separator text output between the line numbers and content.
+
+ Parameters
+
+
+ linenumbering.separator="text"
+
+
+Specifies the text (zero or more characters)
+
+
+
+
+
+ Related Global Parameters
+
+linenumbering.separator
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Line numbering
+
+
+
+
+
+dbhtml_linenumbering.width
+Specifies width for line numbers in verbatims
+
+
+
+ dbhtml linenumbering.width="width"
+
+
+Description
+
+Use the dbhtml linenumbering.width PI as a child
+ of a “verbatim” element – programlisting,
+ screen, synopsis — to specify
+ the width set aside for line numbers.
+
+ Parameters
+
+
+ linenumbering.width="width"
+
+
+Specifies the width (inluding units)
+
+
+
+
+
+ Related Global Parameters
+
+linenumbering.width
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Line numbering
+
+
+
+
+
+dbhtml_list-presentation
+Specifies presentation style for a variablelist or
+ segmentedlist
+
+
+
+ dbhtml list-presentation="list"|"table"
+
+
+Description
+
+Use the dbhtml list-presentation PI as a child of
+ a variablelist or segmentedlist to
+ control the presentation style for the list (to cause it, for
+ example, to be displayed as a table).
+
+ Parameters
+
+
+ list-presentation="list"
+
+
+Displays the list as a list
+
+
+
+ list-presentation="table"
+
+
+Displays the list as a table
+
+
+
+
+
+ Related Global Parameters
+
+
+
+
+variablelist.as.table
+
+
+
+
+segmentedlist.as.table
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Variable list formatting in HTML
+
+
+
+
+
+dbhtml_list-width
+Specifies the width of a variablelist or simplelist
+
+
+
+ dbhtml list-width="width"
+
+
+Description
+
+Use the dbhtml list-width PI as a child of a
+ variablelist or a simplelist presented
+ as a table, to specify the output width.
+
+ Parameters
+
+
+ list-width="width"
+
+
+Specifies the output width (including units)
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Variable list formatting in HTML
+
+
+
+
+
+dbhtml_row-height
+Specifies the height for a CALS table row
+
+
+
+ dbhtml row-height="height"
+
+
+Description
+
+Use the dbhtml row-height PI as a child of a
+ row to specify the height of the row.
+
+ Parameters
+
+
+ row-height="height"
+
+
+Specifies the label height (including units)
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Row height
+
+
+
+
+
+dbhtml_start
+(obsolete) Sets the starting number on an ordered list
+
+
+
+ dbhtml start="character"
+
+
+Description
+
+This PI is obsolete. The intent of
+ this PI was to provide a means for setting a specific starting
+ number for an ordered list. Instead of this PI, set a value
+ for the override attribute on the first
+ listitem in the list; that will have the same
+ effect as what this PI was intended for.
+
+ Parameters
+
+
+ start="character"
+
+
+Specifies the character to use as the starting
+ number; use 0-9, a-z, A-Z, or lowercase or uppercase
+ Roman numerals
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+List starting number
+
+
+
+
+
+dbhtml_stop-chunking
+Do not chunk any descendants of this element.
+
+
+
+ dbhtml stop-chunking
+
+
+Description
+
+When generating chunked HTML output, adding this PI as the child of an element that contains elements that would normally be generated on separate pages if generating chunked output causes chunking to stop at this point. No descendants of the current element will be split into new HTML pages:
+<section>
+<title>Configuring pencil</title>
+<?dbhtml stop-chunking?>
+
+...
+
+</section>
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Chunking into multiple HTML files
+
+
+
+
+
+dbhtml_table-summary
+Specifies summary for CALS table, variablelist, segmentedlist, or qandaset output
+
+
+
+ dbhtml table-summary="text"
+
+
+Description
+
+Use the dbhtml table-summary PI as a child of
+ a CALS table, variablelist,
+ segmentedlist, or qandaset to specify
+ the text for the HTML summary attribute
+ in the output HTML table.
+
+ Parameters
+
+
+ table-summary="text"
+
+
+Specifies the summary text (zero or more characters)
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Variable list formatting in HTML,
+ Table summary text
+
+
+
+
+
+dbhtml_table-width
+Specifies the width for a CALS table
+
+
+
+ dbhtml table-width="width"
+
+
+Description
+
+Use the dbhtml table-width PI as a child of a
+ CALS table to specify the width of the table in
+ output.
+
+ Parameters
+
+
+ table-width="width"
+
+
+Specifies the table width (including units or as a percentage)
+
+
+
+
+
+ Related Global Parameters
+
+default.table.width
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Table width
+
+
+
+
+
+dbhtml_term-presentation
+Sets character formatting for terms in a variablelist
+
+
+
+ dbhtml term-presentation="bold"|"italic"|"bold-italic"
+
+
+Description
+
+Use the dbhtml term-presentation PI as a child
+ of a variablelist to set character formatting for
+ the term output of the list.
+
+ Parameters
+
+
+ term-presentation="bold"
+
+
+Specifies that terms are displayed in bold
+
+
+
+ term-presentation="italic"
+
+
+Specifies that terms are displayed in italic
+
+
+
+ term-presentation="bold-italic"
+
+
+Specifies that terms are displayed in bold-italic
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Variable list formatting in HTML
+
+
+
+
+
+dbhtml_term-separator
+Specifies separator text among terms in a varlistentry
+
+
+
+ dbhtml term-separator="text"
+
+
+Description
+
+Use the dbhtml term-separator PI as a child
+ of a variablelist to specify the separator text
+ among term instances.
+
+ Parameters
+
+
+ term-separator="text"
+
+
+Specifies the text (zero or more characters)
+
+
+
+
+
+ Related Global Parameters
+
+variablelist.term.separator
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Variable list formatting in HTML
+
+
+
+
+
+dbhtml_term-width
+Specifies the term width for a variablelist
+
+
+
+ dbhtml term-width="width"
+
+
+Description
+
+Use the dbhtml term-width PI as a child of a
+ variablelist to specify the width for
+ term output.
+
+ Parameters
+
+
+ term-width="width"
+
+
+Specifies the term width (including units)
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Variable list formatting in HTML
+
+
+
+
+
+dbhtml_toc
+Specifies whether a TOC should be generated for a qandaset
+
+
+
+ dbhtml toc="0"|"1"
+
+
+Description
+
+Use the dbhtml toc PI as a child of a
+ qandaset to specify whether a table of contents
+ (TOC) is generated for the qandaset.
+
+ Parameters
+
+
+ toc="0"
+
+
+If zero, no TOC is generated
+
+
+
+ toc="1"
+
+
+If 1 (or any non-zero value),
+ a TOC is generated
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Q and A list of questions,
+ Q and A formatting
+
+
+
+
+
+dbcmdlist
+Generates a hyperlinked list of commands
+
+
+
+ dbcmdlist
+
+
+Description
+
+Use the dbcmdlist PI as the child of any
+ element (for example, refsynopsisdiv) containing multiple
+ cmdsynopsis instances; a hyperlinked navigational
+ “command list” will be generated at the top of output for that
+ element, enabling users to quickly jump
+ to each command synopsis.
+
+ Parameters
+
+[No parameters]
+
+
+
+
+
+dbfunclist
+Generates a hyperlinked list of functions
+
+
+
+ dbfunclist
+
+
+Description
+
+Use the dbfunclist PI as the child of any
+ element (for example, refsynopsisdiv) containing multiple
+ funcsynopsis instances; a hyperlinked
+ navigational “function list” will be generated at the top of
+ output for that element, enabling users to quickly
+ jump to to each function synopsis.
+
+ Parameters
+
+[No parameters]
+
+
+
+
+
+dbhtml-include_href
+Copies an external well-formed HTML/XML file into current doc
+
+
+
+ dbhtml-include href="URI"
+
+
+Description
+
+Use the dbhtml-include href PI anywhere in a
+ document to cause the contents of the file referenced by the
+ href pseudo-attribute to be copied/inserted “as
+ is” into your HTML output at the point in document order
+ where the PI occurs in the source.
+
+
+
+The referenced file may contain plain text (as long as
+ it is “wrapped” in an html element — see the
+ note below) or markup in any arbitrary vocabulary,
+ including HTML — but it must conform to XML
+ well-formedness constraints (because the feature in XSLT
+ 1.0 for opening external files, the
+ document() function, can only handle
+ files that meet XML well-formedness constraints).
+
+
+Among other things, XML well-formedness constraints
+ require a document to have a single root
+ element. So if the content you want to
+ include is plain text or is markup that does
+ not have a single root element,
+ wrap the content in an
+ html element. The stylesheets will
+ strip out that surrounding html “wrapper” when
+ they find it, leaving just the content you want to
+ insert.
+
+
+ Parameters
+
+
+ href="URI"
+
+
+Specifies the URI for the file to include; the URI
+ can be, for example, a remote http:
+ URI, or a local filesystem file:
+ URI
+
+
+
+
+
+ Related Global Parameters
+
+textinsert.extension
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Inserting external HTML code,
+ External code files
+
+
+
+
+
+dbhh
+Sets topic name and topic id for context-sensitive HTML Help
+
+
+
+ dbhh topicname="name" topicid="id"
+
+
+Description
+
+Use the dbhh PI as a child of components
+ that should be used as targets for context-sensitive help requests.
+
+ Parameters
+
+
+ topicname="name"
+
+
+Specifies a unique string constant that identifies a help topic
+
+
+
+ topicid="id"
+
+
+Specifies a unique integer value for the topicname string
+
+
+
+
+
+ Related Information in DocBook XSL: The Complete Guide
+
+Context-sensitive help
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/html/pi.xsl b/doc/reference/lib/docbook-xsl-snapshot/html/pi.xsl
new file mode 100644
index 00000000..bb85e1b3
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/html/pi.xsl
@@ -0,0 +1,1263 @@
+
+
+
+
+
+HTML Processing Instruction Reference
+
+ $Id: pi.xsl 8097 2008-08-03 13:20:21Z mzjn $
+
+
+
+ Introduction
+ This is generated reference documentation for all
+ user-specifiable processing instructions (PIs) in the DocBook
+ XSL stylesheets for HTML output.
+
+ You add these PIs at particular points in a document to
+ cause specific “exceptions” to formatting/output behavior. To
+ make global changes in formatting/output behavior across an
+ entire document, it’s better to do it by setting an
+ appropriate stylesheet parameter (if there is one).
+
+
+
+
+
+
+
+
+ Sets background color for an image
+
+ Use the dbhtml background-color PI before or
+ after an image (graphic, inlinegraphic,
+ imagedata, or videodata element) as a
+ sibling to the element, to set a background color for the
+ image.
+
+
+ dbhtml background-color="color"
+
+
+
+ background-color="color"
+
+ An HTML color value
+
+
+
+
+
+ Background color
+
+
+
+
+
+
+
+
+
+
+
+ Sets background color on a CALS table row or table cell
+
+ Use the dbhtml bgcolor PI as child of a CALS table row
+ or cell to set a background color for that table row or cell.
+
+
+ dbhtml bgcolor="color"
+
+
+
+ bgcolor="color"
+
+ An HTML color value
+
+
+
+
+
+ Cell background color
+
+
+
+
+
+
+
+
+
+
+
+ Specifies cellpadding in CALS table or qandaset output
+
+ Use the dbhtml cellpadding PI as a child of a
+ CALS table or qandaset to specify the value
+ for the HTML cellpadding attribute in the
+ output HTML table.
+
+
+ dbhtml cellpadding="number"
+
+
+
+ cellpadding="number"
+
+ Specifies the cellpadding
+
+
+
+
+
+ html.cellpadding
+
+
+ Cell spacing and cell padding,
+ Q and A formatting
+
+
+
+
+
+
+
+
+
+
+
+ Specifies cellspacing in CALS table or qandaset output
+
+ Use the dbhtml cellspacing PI as a child of a
+ CALS table or qandaset to specify the value
+ for the HTML cellspacing attribute in the
+ output HTML table.
+
+
+ dbhtml cellspacing="number"
+
+
+
+ cellspacing="number"
+
+ Specifies the cellspacing
+
+
+
+
+
+ html.cellspacing
+
+
+ Cell spacing and cell padding,
+ Q and A formatting
+
+
+
+
+
+
+
+
+
+
+
+ Set value of the class attribute for a CALS table row
+
+ Use the dbhtml class PI as a child of a
+ row to specify a class
+ attribute and value in the HTML output for that row.
+
+
+ dbhtml class="name"
+
+
+
+ class="name"
+
+ Specifies the class name
+
+
+
+
+
+ Table styles in HTML output
+
+
+
+
+
+
+
+
+
+
+
+ Specifies a directory name in which to write files
+
+ When chunking output, use the dbhtml dir PI
+ as a child of a chunk source to cause the output of that
+ chunk to be written to the specified directory; also, use it
+ as a child of a mediaobject to specify a
+ directory into which any long-description files for that
+ mediaobject will be written.
+
+
+ dbhtml dir="path"
+
+
+
+ dir="path"
+
+ Specifies the pathname for the directory
+
+
+
+
+
+ base.dir
+
+
+ dbhtml dir processing instruction
+
+
+
+
+
+
+
+
+
+
+
+ Specifies a filename for a chunk
+
+ When chunking output, use the dbhtml filename
+ PI as a child of a chunk source to specify a filename for
+ the output file for that chunk.
+
+
+ dbhtml filename="filename"
+
+
+
+ filename="path"
+
+ Specifies the filename for the file
+
+
+
+
+
+ use.id.as.filename
+
+
+ dbhtml filenames
+
+
+
+
+
+
+
+
+
+
+
+ Specifies presentation style for a funcsynopsis
+
+ Use the dbhtml funcsynopsis-style PI as a child of
+ a funcsynopsis or anywhere within a funcsynopsis
+ to control the presentation style for output of all
+ funcprototype instances within that funcsynopsis.
+
+
+ dbhtml funcsynopsis-style="kr"|"ansi"
+
+
+
+ funcsynopsis-style="kr"
+
+ Displays funcprototype output in K&R style
+
+
+ funcsynopsis-style="ansi"
+
+ Displays funcprototype output in ANSI style
+
+
+
+
+
+ funcsynopsis.style
+
+
+
+
+
+
+
+
+
+
+
+ Specifies a path to the location of an image file
+
+ Use the dbhtml img.src.path PI before or
+ after an image (graphic,
+ inlinegraphic, imagedata, or
+ videodata element) as a sibling to the element,
+ to specify a path to the location of the image; in HTML
+ output, the value specified for the
+ img.src.path attribute is prepended to the
+ filename.
+
+
+ dbhtml img.src.path="path"
+
+
+
+ img.src.path="path"
+
+ Specifies the pathname to prepend to the name of the image file
+
+
+
+
+
+ img.src.path
+
+
+ Using fileref
+
+
+
+
+
+
+
+
+
+
+
+ Specifies the label width for a qandaset
+
+ Use the dbhtml label-width PI as a child of a
+ qandaset to specify the width of labels.
+
+
+ dbhtml label-width="width"
+
+
+
+ label-width="width"
+
+ Specifies the label width (including units)
+
+
+
+
+
+ Q and A formatting
+
+
+
+
+
+
+
+
+
+
+
+ Specifies interval for line numbers in verbatims
+
+ Use the dbhtml linenumbering.everyNth PI as a child
+ of a “verbatim” element – programlisting,
+ screen, synopsis — to specify
+ the interval at which lines are numbered.
+
+
+ dbhtml linenumbering.everyNth="N"
+
+
+
+ linenumbering.everyNth="N"
+
+ Specifies numbering interval; a number is output
+ before every Nth line
+
+
+
+
+
+ linenumbering.everyNth
+
+
+ Line numbering
+
+
+
+
+
+
+
+
+
+
+
+ Specifies separator text for line numbers in verbatims
+
+ Use the dbhtml linenumbering.separator PI as a child
+ of a “verbatim” element – programlisting,
+ screen, synopsis — to specify
+ the separator text output between the line numbers and content.
+
+
+ dbhtml linenumbering.separator="text"
+
+
+
+ linenumbering.separator="text"
+
+ Specifies the text (zero or more characters)
+
+
+
+
+
+ linenumbering.separator
+
+
+ Line numbering
+
+
+
+
+
+
+
+
+
+
+
+ Specifies width for line numbers in verbatims
+
+ Use the dbhtml linenumbering.width PI as a child
+ of a “verbatim” element – programlisting,
+ screen, synopsis — to specify
+ the width set aside for line numbers.
+
+
+ dbhtml linenumbering.width="width"
+
+
+
+ linenumbering.width="width"
+
+ Specifies the width (inluding units)
+
+
+
+
+
+ linenumbering.width
+
+
+ Line numbering
+
+
+
+
+
+
+
+
+
+
+
+ Specifies presentation style for a variablelist or
+ segmentedlist
+
+ Use the dbhtml list-presentation PI as a child of
+ a variablelist or segmentedlist to
+ control the presentation style for the list (to cause it, for
+ example, to be displayed as a table).
+
+
+ dbhtml list-presentation="list"|"table"
+
+
+
+ list-presentation="list"
+
+ Displays the list as a list
+
+
+ list-presentation="table"
+
+ Displays the list as a table
+
+
+
+
+
+
+
+ variablelist.as.table
+
+
+ segmentedlist.as.table
+
+
+
+
+ Variable list formatting in HTML
+
+
+
+
+
+
+
+
+
+
+
+ Specifies the width of a variablelist or simplelist
+
+ Use the dbhtml list-width PI as a child of a
+ variablelist or a simplelist presented
+ as a table, to specify the output width.
+
+
+ dbhtml list-width="width"
+
+
+
+ list-width="width"
+
+ Specifies the output width (including units)
+
+
+
+
+
+ Variable list formatting in HTML
+
+
+
+
+
+
+
+
+
+
+
+ Specifies the height for a CALS table row
+
+ Use the dbhtml row-height PI as a child of a
+ row to specify the height of the row.
+
+
+ dbhtml row-height="height"
+
+
+
+ row-height="height"
+
+ Specifies the label height (including units)
+
+
+
+
+
+ Row height
+
+
+
+
+
+
+
+
+
+
+
+ (obsolete) Sets the starting number on an ordered list
+
+ This PI is obsolete. The intent of
+ this PI was to provide a means for setting a specific starting
+ number for an ordered list. Instead of this PI, set a value
+ for the override attribute on the first
+ listitem in the list; that will have the same
+ effect as what this PI was intended for.
+
+
+ dbhtml start="character"
+
+
+
+ start="character"
+
+ Specifies the character to use as the starting
+ number; use 0-9, a-z, A-Z, or lowercase or uppercase
+ Roman numerals
+
+
+
+
+
+ List starting number
+
+
+
+
+
+
+
+
+
+
+
+ Do not chunk any descendants of this element.
+
+ When generating chunked HTML output, adding this PI as the child of an element that contains elements that would normally be generated on separate pages if generating chunked output causes chunking to stop at this point. No descendants of the current element will be split into new HTML pages:
+
+Configuring pencil
+
+
+...
+
+]]>
+
+
+
+ dbhtml stop-chunking
+
+
+ Chunking into multiple HTML files
+
+
+
+
+
+ Specifies summary for CALS table, variablelist, segmentedlist, or qandaset output
+
+ Use the dbhtml table-summary PI as a child of
+ a CALS table, variablelist,
+ segmentedlist, or qandaset to specify
+ the text for the HTML summary attribute
+ in the output HTML table.
+
+
+ dbhtml table-summary="text"
+
+
+
+ table-summary="text"
+
+ Specifies the summary text (zero or more characters)
+
+
+
+
+
+ Variable list formatting in HTML,
+ Table summary text
+
+
+
+
+
+
+
+
+
+
+
+ Specifies the width for a CALS table
+
+ Use the dbhtml table-width PI as a child of a
+ CALS table to specify the width of the table in
+ output.
+
+
+ dbhtml table-width="width"
+
+
+
+ table-width="width"
+
+ Specifies the table width (including units or as a percentage)
+
+
+
+
+
+ default.table.width
+
+
+ Table width
+
+
+
+
+
+
+
+
+
+
+
+ Sets character formatting for terms in a variablelist
+
+ Use the dbhtml term-presentation PI as a child
+ of a variablelist to set character formatting for
+ the term output of the list.
+
+
+ dbhtml term-presentation="bold"|"italic"|"bold-italic"
+
+
+
+ term-presentation="bold"
+
+ Specifies that terms are displayed in bold
+
+
+ term-presentation="italic"
+
+ Specifies that terms are displayed in italic
+
+
+ term-presentation="bold-italic"
+
+ Specifies that terms are displayed in bold-italic
+
+
+
+
+
+ Variable list formatting in HTML
+
+
+
+
+
+
+
+
+
+
+
+ Specifies separator text among terms in a varlistentry
+
+ Use the dbhtml term-separator PI as a child
+ of a variablelist to specify the separator text
+ among term instances.
+
+
+ dbhtml term-separator="text"
+
+
+
+ term-separator="text"
+
+ Specifies the text (zero or more characters)
+
+
+
+
+
+ variablelist.term.separator
+
+
+ Variable list formatting in HTML
+
+
+
+
+
+
+
+
+
+
+
+ Specifies the term width for a variablelist
+
+ Use the dbhtml term-width PI as a child of a
+ variablelist to specify the width for
+ term output.
+
+
+ dbhtml term-width="width"
+
+
+
+ term-width="width"
+
+ Specifies the term width (including units)
+
+
+
+
+
+ Variable list formatting in HTML
+
+
+
+
+
+
+
+
+
+
+
+ Specifies whether a TOC should be generated for a qandaset
+
+ Use the dbhtml toc PI as a child of a
+ qandaset to specify whether a table of contents
+ (TOC) is generated for the qandaset.
+
+
+ dbhtml toc="0"|"1"
+
+
+
+ toc="0"
+
+ If zero, no TOC is generated
+
+
+ toc="1"
+
+ If 1 (or any non-zero value),
+ a TOC is generated
+
+
+
+
+
+ Q and A list of questions,
+ Q and A formatting
+
+
+
+
+
+
+
+
+
+
+
+ Generates a hyperlinked list of commands
+
+ Use the dbcmdlist PI as the child of any
+ element (for example, refsynopsisdiv) containing multiple
+ cmdsynopsis instances; a hyperlinked navigational
+ “command list” will be generated at the top of output for that
+ element, enabling users to quickly jump
+ to each command synopsis.
+
+
+ dbcmdlist
+
+
+ [No parameters]
+
+
+
+
+
+ No cmdsynopsis elements matched dbcmdlist PI, perhaps it's nested too deep?
+
+
+
+
+
+
+
+
+
+
+ Generates a hyperlinked list of functions
+
+ Use the dbfunclist PI as the child of any
+ element (for example, refsynopsisdiv) containing multiple
+ funcsynopsis instances; a hyperlinked
+ navigational “function list” will be generated at the top of
+ output for that element, enabling users to quickly
+ jump to to each function synopsis.
+
+
+ dbfunclist
+
+
+ [No parameters]
+
+
+
+
+
+ No funcsynopsis elements matched dbfunclist PI, perhaps it's nested too deep?
+
+
+
+
+
+
+
+
+
+
+ Copies an external well-formed HTML/XML file into current doc
+
+ Use the dbhtml-include href PI anywhere in a
+ document to cause the contents of the file referenced by the
+ href pseudo-attribute to be copied/inserted “as
+ is” into your HTML output at the point in document order
+ where the PI occurs in the source.
+
+ The referenced file may contain plain text (as long as
+ it is “wrapped” in an html element — see the
+ note below) or markup in any arbitrary vocabulary,
+ including HTML — but it must conform to XML
+ well-formedness constraints (because the feature in XSLT
+ 1.0 for opening external files, the
+ document() function, can only handle
+ files that meet XML well-formedness constraints).
+ Among other things, XML well-formedness constraints
+ require a document to have a single root
+ element. So if the content you want to
+ include is plain text or is markup that does
+ not have a single root element,
+ wrap the content in an
+ html element. The stylesheets will
+ strip out that surrounding html “wrapper” when
+ they find it, leaving just the content you want to
+ insert.
+
+
+
+ dbhtml-include href="URI"
+
+
+
+ href="URI"
+
+ Specifies the URI for the file to include; the URI
+ can be, for example, a remote http:
+ URI, or a local filesystem file:
+ URI
+
+
+
+
+
+ textinsert.extension
+
+
+ Inserting external HTML code,
+ External code files
+
+
+
+
+
+
+ href
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ERROR: dbhtml-include processing instruction
+ href has no content.
+
+
+
+
+
+
+ ERROR: dbhtml-include processing instruction has
+ missing or empty href value.
+
+
+
+
+
+
+
+ Sets topic name and topic id for context-sensitive HTML Help
+
+ Use the dbhh PI as a child of components
+ that should be used as targets for context-sensitive help requests.
+
+
+ dbhh topicname="name" topicid="id"
+
+
+
+ topicname="name"
+
+ Specifies a unique string constant that identifies a help topic
+
+
+ topicid="id"
+
+ Specifies a unique integer value for the topicname string
+
+
+
+
+
+ Context-sensitive help
+
+
+
+
+
+
+
+
+
+ filename
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/htmlhelp/profile-htmlhelp.xsl b/doc/reference/lib/docbook-xsl-snapshot/htmlhelp/profile-htmlhelp.xsl
new file mode 100644
index 00000000..eddde3be
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/htmlhelp/profile-htmlhelp.xsl
@@ -0,0 +1,22 @@
+
+
+
+
+
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/htmlhelp/springnet.xsl b/doc/reference/lib/docbook-xsl-snapshot/htmlhelp/springnet.xsl
new file mode 100644
index 00000000..834cc136
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/htmlhelp/springnet.xsl
@@ -0,0 +1,22 @@
+
+
+
+
+
+
+
+ htmlhelp/
+ htmlhelp/
+
+
+
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/Thumbs.db b/doc/reference/lib/docbook-xsl-snapshot/images/Thumbs.db
new file mode 100644
index 00000000..eea1ecff
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/Thumbs.db differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/Thumbs.db b/doc/reference/lib/docbook-xsl-snapshot/images/admons/Thumbs.db
new file mode 100644
index 00000000..ebf567a9
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/Thumbs.db differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/annot-close.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/annot-close.png
new file mode 100644
index 00000000..b9e1a0d5
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/annot-close.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/annot-open.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/annot-open.png
new file mode 100644
index 00000000..71040ec8
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/annot-open.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/blank.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/blank.png
new file mode 100644
index 00000000..764bf4f0
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/blank.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.gif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.gif
new file mode 100644
index 00000000..d9f5e5b1
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.png
new file mode 100644
index 00000000..5b7809ca
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.svg b/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.svg
new file mode 100644
index 00000000..dd84f3fe
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.svg
@@ -0,0 +1,25 @@
+
+
+
+
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.tif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.tif
new file mode 100644
index 00000000..4a282948
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/caution.tif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/draft.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/draft.png
new file mode 100644
index 00000000..59673fe1
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/draft.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/home.gif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/home.gif
new file mode 100644
index 00000000..6784f5bb
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/home.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/home.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/home.png
new file mode 100644
index 00000000..cbb711de
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/home.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/home.svg b/doc/reference/lib/docbook-xsl-snapshot/images/admons/home.svg
new file mode 100644
index 00000000..e803a317
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/admons/home.svg
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.gif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.gif
new file mode 100644
index 00000000..6795d9a8
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.png
new file mode 100644
index 00000000..ad57f6f7
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.svg b/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.svg
new file mode 100644
index 00000000..dd84f3fe
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.svg
@@ -0,0 +1,25 @@
+
+
+
+
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.tif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.tif
new file mode 100644
index 00000000..184de637
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/important.tif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/next.gif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/next.gif
new file mode 100644
index 00000000..aa1516e6
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/next.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/next.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/next.png
new file mode 100644
index 00000000..45835bf8
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/next.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/next.svg b/doc/reference/lib/docbook-xsl-snapshot/images/admons/next.svg
new file mode 100644
index 00000000..75fa83ed
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/admons/next.svg
@@ -0,0 +1,19 @@
+
+
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.gif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.gif
new file mode 100644
index 00000000..f329d359
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.png
new file mode 100644
index 00000000..ad57f6f7
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.svg b/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.svg
new file mode 100644
index 00000000..648299d2
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.svg
@@ -0,0 +1,33 @@
+
+
+
+
+
+
+
+
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.tif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.tif
new file mode 100644
index 00000000..08644d6b
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/note.tif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/prev.gif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/prev.gif
new file mode 100644
index 00000000..64ca8f3c
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/prev.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/prev.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/prev.png
new file mode 100644
index 00000000..cf24654f
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/prev.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/prev.svg b/doc/reference/lib/docbook-xsl-snapshot/images/admons/prev.svg
new file mode 100644
index 00000000..6d88ffdd
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/admons/prev.svg
@@ -0,0 +1,19 @@
+
+
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.gif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.gif
new file mode 100644
index 00000000..823f2b41
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.png
new file mode 100644
index 00000000..ad57f6f7
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.svg b/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.svg
new file mode 100644
index 00000000..4a64a150
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.svg
@@ -0,0 +1,31 @@
+
+
+
+
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.tif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.tif
new file mode 100644
index 00000000..4a3d8c75
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/tip.tif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/toc-blank.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/toc-blank.png
new file mode 100644
index 00000000..6ffad17a
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/toc-blank.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/toc-minus.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/toc-minus.png
new file mode 100644
index 00000000..abbb020c
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/toc-minus.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/toc-plus.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/toc-plus.png
new file mode 100644
index 00000000..941312ce
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/toc-plus.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/up.gif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/up.gif
new file mode 100644
index 00000000..aabc2d01
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/up.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/up.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/up.png
new file mode 100644
index 00000000..07634de2
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/up.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/up.svg b/doc/reference/lib/docbook-xsl-snapshot/images/admons/up.svg
new file mode 100644
index 00000000..d31aa9c8
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/admons/up.svg
@@ -0,0 +1,19 @@
+
+
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.gif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.gif
new file mode 100644
index 00000000..3adf1912
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.png b/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.png
new file mode 100644
index 00000000..1c33db8f
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.svg b/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.svg
new file mode 100644
index 00000000..fc8d7484
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.svg
@@ -0,0 +1,23 @@
+
+
+
+
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.tif b/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.tif
new file mode 100644
index 00000000..7b6611ec
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/admons/warning.tif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/1.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/1.gif
new file mode 100644
index 00000000..9e7a87f7
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/1.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/1.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/1.png
new file mode 100644
index 00000000..7d473430
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/1.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/1.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/1.svg
new file mode 100644
index 00000000..e2e87dc5
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/1.svg
@@ -0,0 +1,15 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/10.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/10.gif
new file mode 100644
index 00000000..e80f7f8e
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/10.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/10.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/10.png
new file mode 100644
index 00000000..997bbc82
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/10.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/10.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/10.svg
new file mode 100644
index 00000000..4740f587
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/10.svg
@@ -0,0 +1,18 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/11.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/11.gif
new file mode 100644
index 00000000..67f91a23
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/11.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/11.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/11.png
new file mode 100644
index 00000000..ce47dac3
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/11.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/11.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/11.svg
new file mode 100644
index 00000000..09a0b2cf
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/11.svg
@@ -0,0 +1,16 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/12.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/12.gif
new file mode 100644
index 00000000..54c4b42f
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/12.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/12.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/12.png
new file mode 100644
index 00000000..31daf4e2
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/12.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/12.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/12.svg
new file mode 100644
index 00000000..9794044c
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/12.svg
@@ -0,0 +1,18 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/13.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/13.gif
new file mode 100644
index 00000000..dd5d7d9b
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/13.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/13.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/13.png
new file mode 100644
index 00000000..14021a89
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/13.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/13.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/13.svg
new file mode 100644
index 00000000..64268bb4
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/13.svg
@@ -0,0 +1,20 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/14.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/14.gif
new file mode 100644
index 00000000..3d7a952a
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/14.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/14.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/14.png
new file mode 100644
index 00000000..64014b75
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/14.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/14.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/14.svg
new file mode 100644
index 00000000..469aa974
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/14.svg
@@ -0,0 +1,17 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/15.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/15.gif
new file mode 100644
index 00000000..1c9183d5
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/15.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/15.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/15.png
new file mode 100644
index 00000000..0d65765f
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/15.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/15.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/15.svg
new file mode 100644
index 00000000..8202233e
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/15.svg
@@ -0,0 +1,19 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/16.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/16.svg
new file mode 100644
index 00000000..01d6bf81
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/16.svg
@@ -0,0 +1,20 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/17.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/17.svg
new file mode 100644
index 00000000..0a04c556
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/17.svg
@@ -0,0 +1,17 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/18.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/18.svg
new file mode 100644
index 00000000..1cb891b3
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/18.svg
@@ -0,0 +1,21 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/19.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/19.svg
new file mode 100644
index 00000000..e6fbb179
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/19.svg
@@ -0,0 +1,20 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/2.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/2.gif
new file mode 100644
index 00000000..94d42a30
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/2.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/2.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/2.png
new file mode 100644
index 00000000..5d09341b
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/2.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/2.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/2.svg
new file mode 100644
index 00000000..07d03395
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/2.svg
@@ -0,0 +1,17 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/20.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/20.svg
new file mode 100644
index 00000000..ccbfd403
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/20.svg
@@ -0,0 +1,20 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/21.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/21.svg
new file mode 100644
index 00000000..93ec53fd
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/21.svg
@@ -0,0 +1,18 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/22.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/22.svg
new file mode 100644
index 00000000..f48c5f3f
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/22.svg
@@ -0,0 +1,20 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/23.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/23.svg
new file mode 100644
index 00000000..66242129
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/23.svg
@@ -0,0 +1,22 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/24.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/24.svg
new file mode 100644
index 00000000..a3d55253
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/24.svg
@@ -0,0 +1,19 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/25.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/25.svg
new file mode 100644
index 00000000..56614a97
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/25.svg
@@ -0,0 +1,21 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/26.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/26.svg
new file mode 100644
index 00000000..56faeaca
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/26.svg
@@ -0,0 +1,22 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/27.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/27.svg
new file mode 100644
index 00000000..a75c8121
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/27.svg
@@ -0,0 +1,19 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/28.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/28.svg
new file mode 100644
index 00000000..7f8cf1a3
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/28.svg
@@ -0,0 +1,23 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/29.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/29.svg
new file mode 100644
index 00000000..cb63adf1
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/29.svg
@@ -0,0 +1,22 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/3.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/3.gif
new file mode 100644
index 00000000..dd3541a1
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/3.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/3.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/3.png
new file mode 100644
index 00000000..ef7b7004
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/3.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/3.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/3.svg
new file mode 100644
index 00000000..918be806
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/3.svg
@@ -0,0 +1,19 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/30.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/30.svg
new file mode 100644
index 00000000..dc43ba1e
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/30.svg
@@ -0,0 +1,22 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/4.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/4.gif
new file mode 100644
index 00000000..4bcbf7e3
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/4.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/4.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/4.png
new file mode 100644
index 00000000..adb8364e
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/4.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/4.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/4.svg
new file mode 100644
index 00000000..8eb6a53b
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/4.svg
@@ -0,0 +1,16 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/5.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/5.gif
new file mode 100644
index 00000000..1c62b4f9
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/5.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/5.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/5.png
new file mode 100644
index 00000000..4d7eb460
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/5.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/5.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/5.svg
new file mode 100644
index 00000000..ca7a9f22
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/5.svg
@@ -0,0 +1,18 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/6.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/6.gif
new file mode 100644
index 00000000..23bc5555
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/6.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/6.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/6.png
new file mode 100644
index 00000000..0ba694af
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/6.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/6.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/6.svg
new file mode 100644
index 00000000..783a0b9d
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/6.svg
@@ -0,0 +1,19 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/7.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/7.gif
new file mode 100644
index 00000000..e55ce895
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/7.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/7.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/7.png
new file mode 100644
index 00000000..472e96f8
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/7.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/7.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/7.svg
new file mode 100644
index 00000000..59b3714b
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/7.svg
@@ -0,0 +1,16 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/8.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/8.gif
new file mode 100644
index 00000000..49375e09
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/8.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/8.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/8.png
new file mode 100644
index 00000000..5e60973c
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/8.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/8.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/8.svg
new file mode 100644
index 00000000..c1803a3c
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/8.svg
@@ -0,0 +1,20 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/9.gif b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/9.gif
new file mode 100644
index 00000000..da12a4fe
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/9.gif differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/9.png b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/9.png
new file mode 100644
index 00000000..a0676d26
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/9.png differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/9.svg b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/9.svg
new file mode 100644
index 00000000..bc149d3c
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/9.svg
@@ -0,0 +1,19 @@
+
+
+
+
+]>
+
diff --git a/doc/reference/lib/docbook-xsl-snapshot/images/callouts/Thumbs.db b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/Thumbs.db
new file mode 100644
index 00000000..bd2a6e21
Binary files /dev/null and b/doc/reference/lib/docbook-xsl-snapshot/images/callouts/Thumbs.db differ
diff --git a/doc/reference/lib/docbook-xsl-snapshot/lib/lib.xsl b/doc/reference/lib/docbook-xsl-snapshot/lib/lib.xsl
new file mode 100644
index 00000000..ecd8dc21
--- /dev/null
+++ b/doc/reference/lib/docbook-xsl-snapshot/lib/lib.xsl
@@ -0,0 +1,481 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ http://...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Unrecognized unit of measure:
+
+ .
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Unrecognized unit of measure:
+
+ .
+
+
+
+
+
+
+ filename
+ 1
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ /
+
+
+
+
+
+
+
+
+
+
+
+ /
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/doc/reference/lib/fop-0.95/build/fop.jar b/doc/reference/lib/fop-0.95/build/fop.jar
new file mode 100644
index 00000000..24419bcf
Binary files /dev/null and b/doc/reference/lib/fop-0.95/build/fop.jar differ
diff --git a/doc/reference/lib/fop-0.95/fop.bat b/doc/reference/lib/fop-0.95/fop.bat
new file mode 100644
index 00000000..85a7fec0
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/fop.bat
@@ -0,0 +1,84 @@
+@ECHO OFF
+REM Licensed to the Apache Software Foundation (ASF) under one or more
+REM contributor license agreements. See the NOTICE file distributed with
+REM this work for additional information regarding copyright ownership.
+REM The ASF licenses this file to You under the Apache License, Version 2.0
+REM (the "License"); you may not use this file except in compliance with
+REM the License. You may obtain a copy of the License at
+REM
+REM http://www.apache.org/licenses/LICENSE-2.0
+REM
+REM Unless required by applicable law or agreed to in writing, software
+REM distributed under the License is distributed on an "AS IS" BASIS,
+REM WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+REM See the License for the specific language governing permissions and
+REM limitations under the License.
+
+rem %~dp0 is the expanded pathname of the current script under NT
+set LOCAL_FOP_HOME=
+if "%OS%"=="Windows_NT" set LOCAL_FOP_HOME=%~dp0
+
+rem Code from Apache Ant project
+rem Slurp the command line arguments. This loop allows for an unlimited number
+rem of arguments (up to the command line limit, anyway).
+rem Could also do a "shift" and "%*" for all params, but apparently doesn't work
+rem with Win9x.
+set FOP_CMD_LINE_ARGS=%1
+if ""%1""=="""" goto doneStart
+shift
+:setupArgs
+if ""%1""=="""" goto doneStart
+set FOP_CMD_LINE_ARGS=%FOP_CMD_LINE_ARGS% %1
+shift
+goto setupArgs
+rem This label provides a place for the argument list loop to break out
+rem and for NT handling to skip to.
+:doneStart
+
+set LOGCHOICE=
+rem The default commons logger for JDK1.4 is JDK1.4Logger.
+rem To use a different logger, uncomment the one desired below
+rem set LOGCHOICE=-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.NoOpLog
+rem set LOGCHOICE=-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
+rem set LOGCHOICE=-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
+
+set LOGLEVEL=
+rem Logging levels
+rem Below option is only if you are using SimpleLog instead of the default JDK1.4 Logger.
+rem To set logging levels for JDK 1.4 Logger, edit the %JAVA_HOME%\JRE\LIB\logging.properties
+rem file instead.
+rem Possible SimpleLog values: "trace", "debug", "info" (default), "warn", "error", or "fatal".
+rem set LOGLEVEL=-Dorg.apache.commons.logging.simplelog.defaultlog=INFO
+
+set LIBDIR=%LOCAL_FOP_HOME%lib
+
+set LOCALCLASSPATH=%LOCAL_FOP_HOME%build\fop.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LOCAL_FOP_HOME%build\fop-sandbox.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LOCAL_FOP_HOME%build\fop-hyph.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xml-apis-1.3.04.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xml-apis-ext-1.3.04.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xercesImpl-2.7.1.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xalan-2.7.0.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\serializer-2.7.0.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\batik-all-1.7.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\xmlgraphics-commons-1.3.1.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\avalon-framework-4.2.0.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\commons-io-1.3.1.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\commons-logging-1.0.4.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\jai_imageio.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%LIBDIR%\fop-hyph.jar
+set LOCALCLASSPATH=%LOCALCLASSPATH%;%FOP_HYPHENATION_PATH%
+
+set JAVAOPTS=-Denv.windir=%WINDIR% -Xmx256m
+
+if "%JAVA_HOME%" == "" goto noJavaHome
+if not exist "%JAVA_HOME%\bin\java.exe" goto noJavaHome
+if "%JAVACMD%" == "" set JAVACMD=%JAVA_HOME%\bin\java
+goto runFop
+
+:noJavaHome
+if "%JAVACMD%" == "" set JAVACMD=java
+
+:runFop
+rem ECHO "%JAVACMD%"
+"%JAVACMD%" %JAVAOPTS% %LOGCHOICE% %LOGLEVEL% -cp "%LOCALCLASSPATH%" org.apache.fop.cli.Main %FOP_CMD_LINE_ARGS%
\ No newline at end of file
diff --git a/doc/reference/lib/fop-0.95/lib/README.txt b/doc/reference/lib/fop-0.95/lib/README.txt
new file mode 100644
index 00000000..2f307b2c
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/README.txt
@@ -0,0 +1,193 @@
+
+Information on Apache FOP dependencies
+=========================================
+
+$Id$
+
+The Apache Licenses can also be found here:
+http://www.apache.org/licenses/
+
+
+Normal Dependencies
+----------------------
+
+- Apache Jakarta Commons IO
+
+ commons-io-*.jar
+ http://jakarta.apache.org/commons/io/
+ (I/O routines)
+
+ Apache License v2.0
+
+- Apache Jakarta Commons Logging
+
+ commons-logging-*.jar
+ http://jakarta.apache.org/commons/logging/
+ (Logging adapter for various logging backends like JDK 1.4 logging or Log4J)
+
+ Apache License v2.0
+
+- Apache Avalon Framework
+
+ avalon-framework-*.jar
+ http://excalibur.apache.org/framework/
+ (Avalon Framework, maintained by the Apache Excalibur project)
+
+ Apache License v2.0
+
+- Apache XML Graphics Commons
+
+ xmlgraphics-commons-*.jar
+ http://xmlgraphics.apache.org/
+ (Common Library for Apache Batik and Apache FOP)
+
+ Apache License v2.0
+
+- Apache Batik
+
+ batik-*.jar
+ http://xmlgraphics.apache.org/batik/
+ (SVG Implementation)
+
+ Apache License v2.0
+
+- Apache XML Commons Externals (JAXP API)
+
+ xml-apis.jar
+ http://xml.apache.org/commons/components/external/
+ (the JAXP API, plus SAX and various W3C DOM Java bindings,
+ maintained in XML Commons Externals)
+
+ Apache License v2.0 (applies to the distribution)
+ SAX is in the public domain
+ http://www.saxproject.org/copying.html
+ W3C Software Notice and License (applies to the various DOM Java bindings)
+ W3C Document License (applies to the DOM documentation)
+ http://www.w3.org/Consortium/Legal/copyright-software
+ http://www.w3.org/Consortium/Legal/copyright-documents
+ http://www.w3.org/Consortium/Legal/
+
+ xml-apis-ext-*.jar
+ http://xml.apache.org/commons/components/external/
+ (additional DOM APIs from W3C, like SVG, SMIL and Simple API for CSS)
+
+ Apache License v2.0 (applies to the distribution)
+ W3C Software Notice and License (applies to the various DOM Java bindings)
+ W3C Document License (applies to the DOM documentation)
+ http://www.w3.org/Consortium/Legal/copyright-software
+ http://www.w3.org/Consortium/Legal/copyright-documents
+ http://www.w3.org/Consortium/Legal/
+
+- Apache Xalan-J
+
+ xalan-*.jar and serializer-*.jar
+ http://xalan.apache.org
+ (JAXP-compliant XSLT and XPath implementation)
+
+ Apache License v2.0 (applies to Xalan-J)
+ Apache License v1.1 (applies to Apache BCEL and Apache REGEXP bundled in the JAR)
+ Historical Permission Notice and Disclaimer (applies to CUP Parser Generator)
+ http://www.opensource.org/licenses/historical.php
+ (see xalan.runtime.LICENSE.txt)
+
+
+Special Dependencies
+-----------------------
+
+- Apache Xerces-J
+
+ xercesImpl-*.jar
+ http://xerces.apache.org
+ (JAXP-compliant XML parser and DOM Level 3 implementation)
+
+ Apache License v2.0
+
+ Xerces-J is not directly referenced by FOP or any of its dependencies.
+
+
+A note on JAXP
+-----------------------
+
+Since Java 1.4, JAXP (Java API for XML Processing) is part of the
+JRE/JDK. Every JVM includes the APIs and an implementation. However,
+older JREs often contain implementations with bugs that are triggered
+by code in Apache FOP and therefore need to be overridden. Now, since
+JAXP is part of the class library, special precautions are necessary
+to replace the original implementations. This is not done by simply
+adding new JARs to the classpath as these classes would never be
+loaded (due to Java's class loader hierarchy).
+
+Replacing the default implementations involves understanding the
+"Endorsed Standards Override Mechanism".
+More information can be found here:
+http://java.sun.com/j2se/1.4.2/docs/guide/standards/index.html
+
+See also:
+http://xml.apache.org/xalan-j/faq.html#faq-N100EF
+
+Essentially, you have two different possibilities:
+- add the replacement JARs in the jre/lib/endorsed directory of your JRE.
+- Use the -Xbootclasspath/p: option when starting the JVM (may not be
+ available for every JVM).
+
+
+Optional Dependencies
+------------------------
+
+The following libraries are not bundled with FOP and must be installed manually.
+Please make sure you've read the license of each package.
+
+- JAI Image I/O Tools
+
+ https://jai-imageio.dev.java.net/
+ BSD license
+
+ Note: This is not the same as JAI! Only the ImageIO-compatible codecs
+ are packaged as "Image I/O Tools". The name may be misleading.
+
+ - JAI (Java Advanced Imaging API)
+
+ http://java.sun.com/products/java-media/jai
+ Java Research License and Java Distribution License (Check which one applies to you!)
+
+ Currently used for:
+ - Grayscale error diffusion dithering in the PCL Renderer
+
+- JEuclid (MathML implementation, for the MathML extension)
+
+ http://jeuclid.sourceforge.net/
+ http://sourceforge.net/projects/jeuclid
+ Apache License v1.1
+
+
+
+Additional development-time dependencies
+-------------------------------------------
+
+- Servlet API
+
+ servlet-*.jar
+ http://jakarta.apache.org/tomcat/
+ (Servlet API, javax.servlet)
+
+ Apache License v1.1
+
+- Apache Ant
+
+ (not bundled, requires pre-installation)
+ http://ant.apache.org
+ (XML-based build system
+
+ Apache License V2.0
+
+- JUnit
+
+ (not bundled, provided by Apache Ant or your IDE)
+ http://www.junit.org
+ Common Public License V1.0
+
+- XMLUnit (optional)
+
+ (not bundled, to be added to your Apache Ant installation)
+ http://xmlunit.sourceforge.net/
+ BSD style license
\ No newline at end of file
diff --git a/doc/reference/lib/fop-0.95/lib/avalon-framework-4.2.0.jar b/doc/reference/lib/fop-0.95/lib/avalon-framework-4.2.0.jar
new file mode 100644
index 00000000..22a7ab34
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/avalon-framework-4.2.0.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/avalon-framework.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/avalon-framework.LICENSE.txt
new file mode 100644
index 00000000..67db8588
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/avalon-framework.LICENSE.txt
@@ -0,0 +1,175 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
diff --git a/doc/reference/lib/fop-0.95/lib/avalon-framework.NOTICE.TXT b/doc/reference/lib/fop-0.95/lib/avalon-framework.NOTICE.TXT
new file mode 100644
index 00000000..416f7ba9
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/avalon-framework.NOTICE.TXT
@@ -0,0 +1,11 @@
+ =========================================================================
+ == NOTICE file corresponding to the section 4 d of ==
+ == the Apache License, Version 2.0, ==
+ =========================================================================
+
+ This product is developed by the Apache Avalon Project.
+ http://avalon.apache.org
+
+ The names "Avalon" and "Merlin" must not be used to endorse or promote
+ products derived from this software without prior written permission.
+ For written permission, please contact pmc@avalon.apache.org.
diff --git a/doc/reference/lib/fop-0.95/lib/batik-all-1.7.jar b/doc/reference/lib/fop-0.95/lib/batik-all-1.7.jar
new file mode 100644
index 00000000..58932858
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/batik-all-1.7.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/batik.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/batik.LICENSE.txt
new file mode 100644
index 00000000..3e4e3d00
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/batik.LICENSE.txt
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
\ No newline at end of file
diff --git a/doc/reference/lib/fop-0.95/lib/batik.NOTICE.txt b/doc/reference/lib/fop-0.95/lib/batik.NOTICE.txt
new file mode 100644
index 00000000..662188f3
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/batik.NOTICE.txt
@@ -0,0 +1,18 @@
+Apache Batik
+Copyright 1999-2007 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
+This software contains code from the World Wide Web Consortium (W3C) for the
+Document Object Model API (DOM API) and SVG Document Type Definition (DTD).
+
+This software contains code from the International Organisation for
+Standardization for the definition of character entities used in the software's
+documentation.
+
+This product includes images from the Tango Desktop Project
+(http://tango.freedesktop.org/).
+
+This product includes images from the Pasodoble Icon Theme
+(http://www.jesusda.com/projects/pasodoble).
diff --git a/doc/reference/lib/fop-0.95/lib/commons-io-1.3.1.jar b/doc/reference/lib/fop-0.95/lib/commons-io-1.3.1.jar
new file mode 100644
index 00000000..7affdefc
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/commons-io-1.3.1.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/commons-io.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/commons-io.LICENSE.txt
new file mode 100644
index 00000000..6b0b1270
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/commons-io.LICENSE.txt
@@ -0,0 +1,203 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
diff --git a/doc/reference/lib/fop-0.95/lib/commons-io.NOTICE.txt b/doc/reference/lib/fop-0.95/lib/commons-io.NOTICE.txt
new file mode 100644
index 00000000..ce3b94a0
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/commons-io.NOTICE.txt
@@ -0,0 +1,6 @@
+Apache Jakarta Commons IO
+Copyright 2001-2007 The Apache Software Foundation
+
+This product includes software developed by
+The Apache Software Foundation (http://www.apache.org/).
+
diff --git a/doc/reference/lib/fop-0.95/lib/commons-logging-1.0.4.jar b/doc/reference/lib/fop-0.95/lib/commons-logging-1.0.4.jar
new file mode 100644
index 00000000..b73a80fa
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/commons-logging-1.0.4.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/commons-logging.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/commons-logging.LICENSE.txt
new file mode 100644
index 00000000..d6456956
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/commons-logging.LICENSE.txt
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/doc/reference/lib/fop-0.95/lib/commons-logging.NOTICE.txt b/doc/reference/lib/fop-0.95/lib/commons-logging.NOTICE.txt
new file mode 100644
index 00000000..439eb83b
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/commons-logging.NOTICE.txt
@@ -0,0 +1,3 @@
+This product includes software developed by
+The Apache Software Foundation (http://www.apache.org/).
+
diff --git a/doc/reference/lib/fop-0.95/lib/serializer-2.7.0.jar b/doc/reference/lib/fop-0.95/lib/serializer-2.7.0.jar
new file mode 100644
index 00000000..7cd80696
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/serializer-2.7.0.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/serializer.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/serializer.LICENSE.txt
new file mode 100644
index 00000000..261eeb9e
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/serializer.LICENSE.txt
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/doc/reference/lib/fop-0.95/lib/serializer.NOTICE.txt b/doc/reference/lib/fop-0.95/lib/serializer.NOTICE.txt
new file mode 100644
index 00000000..f4cea120
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/serializer.NOTICE.txt
@@ -0,0 +1,15 @@
+ =========================================================================
+ == NOTICE file corresponding to section 4(d) of the Apache License, ==
+ == Version 2.0, in this case for the Apache Xalan serializer ==
+ == distribution. ==
+ =========================================================================
+
+ This product includes software developed by IBM Corporation (http://www.ibm.com)
+ and The Apache Software Foundation (http://www.apache.org/).
+
+ Portions of this software was originally based on the following:
+ - software copyright (c) 1999-2002, Lotus Development Corporation.,
+ http://www.lotus.com.
+ - software copyright (c) 2001-2002, Sun Microsystems.,
+ http://www.sun.com.
+ - software copyright (c) 2003, IBM Corporation., http://www.ibm.com.
diff --git a/doc/reference/lib/fop-0.95/lib/xalan-2.7.0.jar b/doc/reference/lib/fop-0.95/lib/xalan-2.7.0.jar
new file mode 100644
index 00000000..979ee761
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/xalan-2.7.0.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/xalan.BCEL.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/xalan.BCEL.LICENSE.txt
new file mode 100644
index 00000000..58940a04
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xalan.BCEL.LICENSE.txt
@@ -0,0 +1,52 @@
+Apache Software License, Version 1.1
+*
+* Copyright (c) 2001 The Apache Software Foundation. All rights
+* reserved.
+*
+* Redistribution and use in source and binary forms, with or without
+* modification, are permitted provided that the following conditions
+* are met:
+*
+* 1. Redistributions of source code must retain the above copyright
+* notice, this list of conditions and the following disclaimer.
+*
+* 2. Redistributions in binary form must reproduce the above copyright
+* notice, this list of conditions and the following disclaimer in
+* the documentation and/or other materials provided with the
+* distribution.
+*
+* 3. The end-user documentation included with the redistribution,
+* if any, must include the following acknowledgment:
+* "This product includes software developed by the
+* Apache Software Foundation (http://www.apache.org/)."
+* Alternately, this acknowledgment may appear in the software itself,
+* if and wherever such third-party acknowledgments normally appear.
+*
+* 4. The names "Apache" and "Apache Software Foundation" and
+* "Apache BCEL" must not be used to endorse or promote products
+* derived from this software without prior written permission. For
+* written permission, please contact apache@apache.org.
+*
+* 5. Products derived from this software may not be called "Apache",
+* "Apache BCEL", nor may "Apache" appear in their name, without
+* prior written permission of the Apache Software Foundation.
+*
+* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+* DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
+* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+* SUCH DAMAGE.
+* ====================================================================
+*
+* This software consists of voluntary contributions made by many
+* individuals on behalf of the Apache Software Foundation. For more
+* information on the Apache Software Foundation, please see
+* .
+*/
diff --git a/doc/reference/lib/fop-0.95/lib/xalan.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/xalan.LICENSE.txt
new file mode 100644
index 00000000..57bc88a1
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xalan.LICENSE.txt
@@ -0,0 +1,202 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+
diff --git a/doc/reference/lib/fop-0.95/lib/xalan.NOTICE.txt b/doc/reference/lib/fop-0.95/lib/xalan.NOTICE.txt
new file mode 100644
index 00000000..81ce7751
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xalan.NOTICE.txt
@@ -0,0 +1,44 @@
+ =========================================================================
+ == NOTICE file corresponding to section 4(d) of the Apache License, ==
+ == Version 2.0, in this case for the Apache Xalan distribution. ==
+ =========================================================================
+
+ This product includes software developed by
+ The Apache Software Foundation (http://www.apache.org/).
+
+ Portions of this software was originally based on the following:
+ - software copyright (c) 1999-2002, Lotus Development Corporation.,
+ http://www.lotus.com.
+ - software copyright (c) 2001-2002, Sun Microsystems.,
+ http://www.sun.com.
+ - software copyright (c) 2003, IBM Corporation., http://www.ibm.com.
+ - voluntary contributions made by Ovidiu Predescu on
+ behalf of the Apache Software Foundation that was originally developed
+ at Hewlett Packard Company.
+
+ The binary distribution package (ie. jars, samples and documentation) of
+ this product includes software developed by the following:
+
+ - The Apache Software Foundation
+ - Xerces Java - see xercesImpl.README.txt
+ - JAXP 1.3 APIs - see xml-apis.README.txt
+ - Bytecode Engineering Library - see BCEL.README.txt
+ - Regular Expression - see regexp.README.txt
+
+ - Scott Hudson, Frank Flannery, C. Scott Ananian
+ - CUP Parser Generator runtime (javacup\runtime) - see runtime.README.txt
+
+
+ The source distribution package (ie. all source and tools required to build
+ Xalan Java) of this product includes software developed by the following:
+
+ - The Apache Software Foundation
+ - Xerces Java - see xercesImpl.README.txt
+ - JAXP 1.3 APIs - see xml-apis.README.txt
+ - Bytecode Engineering Library - see BCEL.README.txt
+ - Regular Expression - see regexp.README.txt
+ - Ant - see ant.README.txt
+ - Stylebook doc tool - see stylebook-1.0-b3_xalan-2.README.txt
+
+ - Elliot Joel Berk and C. Scott Ananian
+ - Lexical Analyzer Generator (JLex) - see JLex.README.txt
diff --git a/doc/reference/lib/fop-0.95/lib/xalan.regexp.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/xalan.regexp.LICENSE.txt
new file mode 100644
index 00000000..58940a04
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xalan.regexp.LICENSE.txt
@@ -0,0 +1,52 @@
+Apache Software License, Version 1.1
+*
+* Copyright (c) 2001 The Apache Software Foundation. All rights
+* reserved.
+*
+* Redistribution and use in source and binary forms, with or without
+* modification, are permitted provided that the following conditions
+* are met:
+*
+* 1. Redistributions of source code must retain the above copyright
+* notice, this list of conditions and the following disclaimer.
+*
+* 2. Redistributions in binary form must reproduce the above copyright
+* notice, this list of conditions and the following disclaimer in
+* the documentation and/or other materials provided with the
+* distribution.
+*
+* 3. The end-user documentation included with the redistribution,
+* if any, must include the following acknowledgment:
+* "This product includes software developed by the
+* Apache Software Foundation (http://www.apache.org/)."
+* Alternately, this acknowledgment may appear in the software itself,
+* if and wherever such third-party acknowledgments normally appear.
+*
+* 4. The names "Apache" and "Apache Software Foundation" and
+* "Apache BCEL" must not be used to endorse or promote products
+* derived from this software without prior written permission. For
+* written permission, please contact apache@apache.org.
+*
+* 5. Products derived from this software may not be called "Apache",
+* "Apache BCEL", nor may "Apache" appear in their name, without
+* prior written permission of the Apache Software Foundation.
+*
+* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+* DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
+* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+* USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+* ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+* OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+* SUCH DAMAGE.
+* ====================================================================
+*
+* This software consists of voluntary contributions made by many
+* individuals on behalf of the Apache Software Foundation. For more
+* information on the Apache Software Foundation, please see
+* .
+*/
diff --git a/doc/reference/lib/fop-0.95/lib/xalan.runtime.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/xalan.runtime.LICENSE.txt
new file mode 100644
index 00000000..374d4984
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xalan.runtime.LICENSE.txt
@@ -0,0 +1,20 @@
+CUP Parser Generator Copyright Notice, License, and Disclaimer
+(runtime.jar component)
+
+Copyright 1996-1999 by Scott Hudson, Frank Flannery, C. Scott Ananian
+
+Permission to use, copy, modify, and distribute this software and its
+documentation for any purpose and without fee is hereby granted, provided
+that the above copyright notice appear in all copies and that both
+the copyright notice and this permission notice and warranty disclaimer
+appear in supporting documentation, and that the names of the authors
+or their employers not be used in advertising or publicity pertaining
+to distribution of the software without specific, written prior permission.
+
+The authors and their employers disclaim all warranties with regard to
+this software, including all implied warranties of merchantability
+and fitness. In no event shall the authors or their employers be liable
+for any special, indirect or consequential damages or any damages
+whatsoever resulting from loss of use, data or profits, whether in an action
+of contract, negligence or other tortious action, arising out of or
+in connection with the use or performance of this software.
diff --git a/doc/reference/lib/fop-0.95/lib/xerces.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/xerces.LICENSE.txt
new file mode 100644
index 00000000..b37087c5
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xerces.LICENSE.txt
@@ -0,0 +1,56 @@
+/*
+ * The Apache Software License, Version 1.1
+ *
+ *
+ * Copyright (c) 1999 The Apache Software Foundation. All rights
+ * reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer.
+ *
+ * 2. Redistributions in binary form must reproduce the above copyright
+ * notice, this list of conditions and the following disclaimer in
+ * the documentation and/or other materials provided with the
+ * distribution.
+ *
+ * 3. The end-user documentation included with the redistribution,
+ * if any, must include the following acknowledgment:
+ * "This product includes software developed by the
+ * Apache Software Foundation (http://www.apache.org/)."
+ * Alternately, this acknowledgment may appear in the software itself,
+ * if and wherever such third-party acknowledgments normally appear.
+ *
+ * 4. The names "Xerces" and "Apache Software Foundation" must
+ * not be used to endorse or promote products derived from this
+ * software without prior written permission. For written
+ * permission, please contact apache@apache.org.
+ *
+ * 5. Products derived from this software may not be called "Apache",
+ * nor may "Apache" appear in their name, without prior written
+ * permission of the Apache Software Foundation.
+ *
+ * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+ * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+ * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
+ * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
+ * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
+ * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ * ====================================================================
+ *
+ * This software consists of voluntary contributions made by many
+ * individuals on behalf of the Apache Software Foundation and was
+ * originally based on software copyright (c) 1999, International
+ * Business Machines, Inc., http://www.ibm.com. For more
+ * information on the Apache Software Foundation, please see
+ * .
+ */
diff --git a/doc/reference/lib/fop-0.95/lib/xercesImpl-2.7.1.jar b/doc/reference/lib/fop-0.95/lib/xercesImpl-2.7.1.jar
new file mode 100644
index 00000000..eac75ae8
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/xercesImpl-2.7.1.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/xercesImpl.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/xercesImpl.LICENSE.txt
new file mode 100644
index 00000000..261eeb9e
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xercesImpl.LICENSE.txt
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/doc/reference/lib/fop-0.95/lib/xercesImpl.NOTICE.txt b/doc/reference/lib/fop-0.95/lib/xercesImpl.NOTICE.txt
new file mode 100644
index 00000000..77dc14c6
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xercesImpl.NOTICE.txt
@@ -0,0 +1,14 @@
+ =========================================================================
+ == NOTICE file corresponding to section 4(d) of the Apache License, ==
+ == Version 2.0, in this case for the Apache Xerces distribution. ==
+ =========================================================================
+
+ This product includes software developed by
+ The Apache Software Foundation (http://www.apache.org/).
+
+ Portions of this software were originally based on the following:
+ - software copyright (c) 1999, IBM Corporation., http://www.ibm.com.
+ - software copyright (c) 1999, Sun Microsystems., http://www.sun.com.
+ - voluntary contributions made by Paul Eng on behalf of the
+ Apache Software Foundation that were originally developed at iClick, Inc.,
+ software copyright (c) 1999.
\ No newline at end of file
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis-1.3.04.jar b/doc/reference/lib/fop-0.95/lib/xml-apis-1.3.04.jar
new file mode 100644
index 00000000..d42c0ea6
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/xml-apis-1.3.04.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis-ext-1.3.04.jar b/doc/reference/lib/fop-0.95/lib/xml-apis-ext-1.3.04.jar
new file mode 100644
index 00000000..a7869d68
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/xml-apis-ext-1.3.04.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.dom-documentation.txt b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.dom-documentation.txt
new file mode 100644
index 00000000..3d84b5d6
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.dom-documentation.txt
@@ -0,0 +1,73 @@
+xml-commons/java/external/LICENSE.dom-documentation.txt $Id: LICENSE.dom-documentation.txt 226215 2005-06-03 22:49:13Z mrglavas $
+
+
+This license came from: http://www.w3.org/Consortium/Legal/copyright-documents-20021231
+
+
+W3C DOCUMENT LICENSE
+http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231
+
+Public documents on the W3C site are provided by the copyright holders under
+the following license. By using and/or copying this document, or the W3C
+document from which this statement is linked, you (the licensee) agree that
+you have read, understood, and will comply with the following terms and
+conditions:
+
+Permission to copy, and distribute the contents of this document, or the W3C
+document from which this statement is linked, in any medium for any purpose
+and without fee or royalty is hereby granted, provided that you include the
+following on ALL copies of the document, or portions thereof, that you use:
+
+ 1. A link or URL to the original W3C document.
+ 2. The pre-existing copyright notice of the original author, or if it
+ doesn't exist, a notice (hypertext is preferred, but a textual
+ representation is permitted) of the form: "Copyright [$date-of-document]
+ World Wide Web Consortium, (Massachusetts Institute of Technology,
+ European Research Consortium for Informatics and Mathematics, Keio
+ University). All Rights Reserved.
+ http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231"
+ 3. If it exists, the STATUS of the W3C document.
+
+When space permits, inclusion of the full text of this NOTICE should be
+provided. We request that authorship attribution be provided in any software,
+documents, or other items or products that you create pursuant to the
+implementation of the contents of this document, or any portion thereof.
+
+No right to create modifications or derivatives of W3C documents is granted
+pursuant to this license. However, if additional requirements (documented in
+the Copyright FAQ) are satisfied, the right to create modifications or
+derivatives is sometimes granted by the W3C to individuals complying with
+those requirements.
+
+THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
+REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT
+LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
+NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE
+FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT
+INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
+COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE
+PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
+
+The name and trademarks of copyright holders may NOT be used in advertising
+or publicity pertaining to this document or its contents without specific,
+written prior permission. Title to copyright in this document will at all
+times remain with copyright holders.
+
+----------------------------------------------------------------------------
+
+This formulation of W3C's notice and license became active on December 31 2002.
+This version removes the copyright ownership notice such that this license can
+be used with materials other than those owned by the W3C, moves information on
+style sheets, DTDs, and schemas to the Copyright FAQ, reflects that ERCIM is
+now a host of the W3C, includes references to this specific dated version of
+the license, and removes the ambiguous grant of "use". See the older
+formulation for the policy prior to this date. Please see our Copyright FAQ for
+common questions about using materials from our site, such as the translating
+or annotating specifications. Other questions about this notice can be directed
+to site-policy@w3.org.
+
+Joseph Reagle
+
+Last revised by Reagle $Date: 2005-06-03 18:49:13 -0400 (Fri, 03 Jun 2005) $
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.dom-software.txt b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.dom-software.txt
new file mode 100644
index 00000000..c5fe5a48
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.dom-software.txt
@@ -0,0 +1,61 @@
+xml-commons/java/external/LICENSE.dom-software.txt $Id: LICENSE.dom-software.txt 226215 2005-06-03 22:49:13Z mrglavas $
+
+
+This license came from: http://www.w3.org/Consortium/Legal/copyright-software-20021231
+
+
+W3C SOFTWARE NOTICE AND LICENSE
+http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
+
+This work (and included software, documentation such as READMEs, or other
+related items) is being provided by the copyright holders under the following
+license. By obtaining, using and/or copying this work, you (the licensee) agree
+that you have read, understood, and will comply with the following terms and
+conditions.
+
+Permission to copy, modify, and distribute this software and its documentation,
+with or without modification, for any purpose and without fee or royalty is
+hereby granted, provided that you include the following on ALL copies of the
+software and documentation or portions thereof, including modifications:
+
+ 1. The full text of this NOTICE in a location viewable to users of the
+ redistributed or derivative work.
+ 2. Any pre-existing intellectual property disclaimers, notices, or terms
+ and conditions. If none exist, the W3C Software Short Notice should be
+ included (hypertext is preferred, text is permitted) within the body
+ of any redistributed or derivative code.
+ 3. Notice of any changes or modifications to the files, including the date
+ changes were made. (We recommend you provide URIs to the location from
+ which the code is derived.)
+
+THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE
+NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
+TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT
+THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY
+PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
+COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
+
+The name and trademarks of copyright holders may NOT be used in advertising or
+publicity pertaining to the software without specific, written prior permission.
+Title to copyright in this software and any associated documentation will at
+all times remain with copyright holders.
+
+____________________________________
+
+This formulation of W3C's notice and license became active on December 31 2002.
+This version removes the copyright ownership notice such that this license can
+be used with materials other than those owned by the W3C, reflects that ERCIM
+is now a host of the W3C, includes references to this specific dated version of
+the license, and removes the ambiguous grant of "use". Otherwise, this version
+is the same as the previous version and is written so as to preserve the Free
+Software Foundation's assessment of GPL compatibility and OSI's certification
+under the Open Source Definition. Please see our Copyright FAQ for common
+questions about using materials from our site, including specific terms and
+conditions for packages like libwww, Amaya, and Jigsaw. Other questions about
+this notice can be directed to site-policy@w3.org.
+
+Joseph Reagle
+
+Last revised by Reagle $Date: 2005-06-03 18:49:13 -0400 (Fri, 03 Jun 2005) $
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.sac.html b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.sac.html
new file mode 100644
index 00000000..46abc5c6
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.sac.html
@@ -0,0 +1,75 @@
+
+
+
+
+
+ W3C IPR SOFTWARE NOTICE
+
+
+
+
+
+
W3C IPR SOFTWARE NOTICE
+
+
Copyright 2002 World Wide Web Consortium, (Massachusetts Institute of
+Technology, Institut National de Recherche en Informatique et en Automatique,
+Keio University). All Rights Reserved.
This W3C work (including software, documents, or other related items) is
+being provided by the copyright holders under the following license. By
+obtaining, using and/or copying this work, you (the licensee) agree that you
+have read, understood, and will comply with the following terms and
+conditions:
+
+
Permission to use, copy, and modify this software and its documentation,
+with or without modification, for any purpose and without fee or royalty is
+hereby granted, provided that you include the following on ALL copies of the
+software and documentation or portions thereof, including modifications, that
+you make:
+
+
The full text of this NOTICE in a location viewable to users of the
+ redistributed or derivative work.
Notice of any changes or modifications to the W3C files, including the
+ date changes were made. (We recommend you provide URIs to the location
+ from which the code is derived.)
+
+
+
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS
+MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
+LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR
+PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY
+THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
+
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR
+DOCUMENTATION.
+
+
The name and trademarks of copyright holders may NOT be used in advertising
+or publicity pertaining to the software without specific, written prior
+permission. Title to copyright in this software and any associated
+documentation will at all times remain with copyright holders.
+
+
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.txt
new file mode 100644
index 00000000..d6456956
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.LICENSE.txt
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis-ext.NOTICE.txt b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.NOTICE.txt
new file mode 100644
index 00000000..f6d34b5e
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.NOTICE.txt
@@ -0,0 +1,16 @@
+ =========================================================================
+ == NOTICE file corresponding to section 4(d) of the Apache License, ==
+ == Version 2.0, in this case for the Apache xml-commons xml-apis ==
+ == distribution. ==
+ =========================================================================
+
+ Apache XML Commons XML APIs
+ Copyright 2006 The Apache Software Foundation.
+
+ This product includes software developed at
+ The Apache Software Foundation (http://www.apache.org/).
+
+ Portions of this software were originally based on the following:
+ - software copyright (c) 1999, IBM Corporation., http://www.ibm.com.
+ - software copyright (c) 1999, Sun Microsystems., http://www.sun.com.
+ - software copyright (c) 2000 World Wide Web Consortium, http://www.w3.org
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis-ext.README.dom.txt b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.README.dom.txt
new file mode 100644
index 00000000..bde69449
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xml-apis-ext.README.dom.txt
@@ -0,0 +1,56 @@
+xml-commons/java/external/README.dom.txt $Id: README.dom.txt 477038 2006-11-20 04:40:36Z mrglavas $
+
+
+HEAR YE, HEAR YE!
+
+
+All of the .java software and associated documentation about
+the DOM in this repository are distributed under the license
+from the W3C, which is provided herein.
+
+
+LICENSE.dom-software.txt covers all software from the W3C
+including the following items in the xml-commons project:
+
+ xml-commons/java/external/src/org/w3c
+ and all subdirectories
+
+(Note: SAC (The Simple API for CSS) has been published under an older
+version of the W3C license. The original license file is LICENSE.sac.html.)
+
+LICENSE.dom-documentation.txt covers all documentation from the W3C
+including the following items in the xml-commons project:
+
+ xml-commons/java/external/xdocs/dom
+ and all subdirectories
+
+The actual DOM Java Language Binding classes in xml-commons came from:
+ http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/java-binding.html
+
+The specification of DOM Level 3's various parts is at:
+ http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/
+ http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/
+ http://www.w3.org/TR/2004/NOTE-DOM-Level-3-XPath-20040226/
+
+The specification of DOM Level 2's various parts is at:
+ http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/
+ http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113/
+ http://www.w3.org/TR/2000/REC-DOM-Level-2-Traversal-Range-20001113/
+ http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113/
+
+The specification of DOM Level 1's various parts is at:
+ http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/level-one-html.html
+
+Links to all available W3C DOM Java Bindings can be found at:
+ http://www.w3.org/DOM/DOMTR
+
+The actual classes of The Simple API for CSS (SAC) came from:
+ http://www.w3.org/Style/CSS/SAC/
+ http://www.w3.org/2002/06/sacjava-1.3.zip
+
+The actual DOM Java Language Binding classes for SMIL came from:
+ http://dev.w3.org/cvsweb/java/classes/org/w3c/dom/smil/
+ (both ElementTimeControl.java and TimeEvent.java were taken at revision 1.1)
+
+The actual DOM Java Language Binding classes for SVG 1.1 came from:
+ http://www.w3.org/TR/SVG11/java.html
\ No newline at end of file
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis.LICENSE-SAX.html b/doc/reference/lib/fop-0.95/lib/xml-apis.LICENSE-SAX.html
new file mode 100644
index 00000000..2b653f31
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xml-apis.LICENSE-SAX.html
@@ -0,0 +1,17 @@
+
+ SAX LICENSE
+
+
This license applies to all interfaces and classes in the
+ org/xml/sax hierarchy.
+
+
+
+ This module, both source code and documentation, is in the
+ Public Domain, and comes with NO WARRANTY.
+ See http://www.saxproject.org
+ for further information.
+
Public documents on the W3C site are provided by the copyright holders under
+the following license. By using and/or copying this document, or the W3C
+document from which this statement is linked, you (the licensee) agree that you
+have read, understood, and will comply with the following terms and
+conditions:
+
Permission to copy, and distribute the contents of this document, or the W3C
+document from which this statement is linked, in any medium for any purpose and
+without fee or royalty is hereby granted, provided that you include the
+following on ALL copies of the document, or portions thereof, that you
+use:
When space permits, inclusion of the full text of this NOTICE should
+be provided. We request that authorship attribution be provided in any software,
+documents, or other items or products that you create pursuant to the
+implementation of the contents of this document, or any portion thereof.
+
No right to create modifications or derivatives of W3C documents is granted
+pursuant to this license. However, if additional requirements (documented in the
+Copyright FAQ) are
+satisfied, the right to create modifications or derivatives is sometimes
+granted by the W3C to individuals complying with those requirements.
+
THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
+REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED
+TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
+NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR
+ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY
+THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE
+OR IMPLEMENTATION OF THE CONTENTS THEREOF.
+
The name and trademarks of copyright holders may NOT be used in advertising
+or publicity pertaining to this document or its contents without specific,
+written prior permission. Title to copyright in this document will at all times
+remain with copyright holders.
This formulation of W3C's notice and license became active on December 31
+2002. This version removes the copyright ownership notice such that this license
+can be used with materials other than those owned by the W3C, moves information
+on style sheets, DTDs, and schemas to the Copyright FAQ, reflects
+that ERCIM is now a host of the W3C, includes references to this specific dated
+version of the license, and removes the ambiguous grant of "use". See the older
+formulation for the policy prior to this date. Please see our Copyright FAQ for common
+questions about using materials from our site, such as the translating or
+annotating specifications. Other questions about this notice can be directed to
+site-policy@w3.org.
This work (and included software, documentation such as READMEs, or other
+related items) is being provided by the copyright holders under the following
+license. By obtaining, using and/or copying this work, you (the licensee) agree
+that you have read, understood, and will comply with the following terms and
+conditions.
+
Permission to copy, modify, and distribute this software and its
+documentation, with or without modification, for any purpose and without
+fee or royalty is hereby granted, provided that you include the following on ALL
+copies of the software and documentation or portions thereof, including
+modifications:
+
+
The full text of this NOTICE in a location viewable to users of the
+ redistributed or derivative work.
+
Any pre-existing intellectual property disclaimers, notices, or terms and
+ conditions. If none exist, the W3C
+ Software Short Notice should be included (hypertext is preferred, text is
+ permitted) within the body of any redistributed or derivative code.
+
Notice of any changes or modifications to the files, including the date
+ changes were made. (We recommend you provide URIs to the location from which
+ the code is derived.)
+
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS
+MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
+LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE
+OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD
+PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR
+DOCUMENTATION.
+
The name and trademarks of copyright holders may NOT be used in advertising
+or publicity pertaining to the software without specific, written prior
+permission. Title to copyright in this software and any associated documentation
+will at all times remain with copyright holders.
+
+
____________________________________
+
This formulation of W3C's notice and license became active on December 31
+2002. This version removes the copyright ownership notice such that this license
+can be used with materials other than those owned by the W3C, reflects that
+ERCIM is now a host of the W3C, includes references to this specific dated
+version of the license, and removes the ambiguous grant of "use". Otherwise,
+this version is the same as the previous
+version and is written so as to preserve the Free
+Software Foundation's assessment of GPL compatibility and OSI's certification under
+the Open Source
+Definition. Please see our Copyright FAQ for common
+questions about using materials from our site, including specific terms and
+conditions for packages like libwww, Amaya, and Jigsaw. Other questions about
+this notice can be directed to site-policy@w3.org.
Last revised by Reagle $Date: 2005/07/19 16:33:09 $
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/xml-apis.LICENSE.txt
new file mode 100644
index 00000000..261eeb9e
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xml-apis.LICENSE.txt
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/doc/reference/lib/fop-0.95/lib/xml-apis.NOTICE.txt b/doc/reference/lib/fop-0.95/lib/xml-apis.NOTICE.txt
new file mode 100644
index 00000000..50694e5e
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xml-apis.NOTICE.txt
@@ -0,0 +1,13 @@
+ =========================================================================
+ == NOTICE file corresponding to section 4(d) of the Apache License, ==
+ == Version 2.0, in this case for the Apache xml-commons xml-apis ==
+ == distribution. ==
+ =========================================================================
+
+ This product includes software developed by The Apache Software Foundation
+ (http://www.apache.org/).
+
+ Portions of this software were originally based on the following:
+ - software copyright (c) 1999, IBM Corporation., http://www.ibm.com.
+ - software copyright (c) 1999, Sun Microsystems., http://www.sun.com.
+ - software copyright (c) 2000 World Wide Web Consortium, http://www.w3.org
diff --git a/doc/reference/lib/fop-0.95/lib/xmlgraphics-commons-1.3.1.jar b/doc/reference/lib/fop-0.95/lib/xmlgraphics-commons-1.3.1.jar
new file mode 100644
index 00000000..81a485dc
Binary files /dev/null and b/doc/reference/lib/fop-0.95/lib/xmlgraphics-commons-1.3.1.jar differ
diff --git a/doc/reference/lib/fop-0.95/lib/xmlgraphics-commons.LICENSE.txt b/doc/reference/lib/fop-0.95/lib/xmlgraphics-commons.LICENSE.txt
new file mode 100644
index 00000000..d6456956
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xmlgraphics-commons.LICENSE.txt
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/doc/reference/lib/fop-0.95/lib/xmlgraphics-commons.NOTICE.txt b/doc/reference/lib/fop-0.95/lib/xmlgraphics-commons.NOTICE.txt
new file mode 100644
index 00000000..76171ea8
--- /dev/null
+++ b/doc/reference/lib/fop-0.95/lib/xmlgraphics-commons.NOTICE.txt
@@ -0,0 +1,5 @@
+Apache XML Graphics Commons
+Copyright 2006-2007 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
diff --git a/doc/reference/lib/saxon6-5-5/saxon.jar b/doc/reference/lib/saxon6-5-5/saxon.jar
new file mode 100644
index 00000000..15aa83a5
Binary files /dev/null and b/doc/reference/lib/saxon6-5-5/saxon.jar differ
diff --git a/doc/reference/lib/xslthl-2.0.0/xslthl-2.0.0.jar b/doc/reference/lib/xslthl-2.0.0/xslthl-2.0.0.jar
new file mode 100644
index 00000000..cb75ed85
Binary files /dev/null and b/doc/reference/lib/xslthl-2.0.0/xslthl-2.0.0.jar differ