From 140d836e9cd54fb67b969fd82ef7ed19ba574d40 Mon Sep 17 00:00:00 2001 From: Luca Falavigna Date: Sat, 26 Apr 2014 15:11:58 +0200 Subject: Imported Upstream version 2.3.1 --- .../docbook-xsl-1.76.1/params/generate.toc.xml | 108 +++++++++++++++++++++ 1 file changed, 108 insertions(+) create mode 100644 src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/generate.toc.xml (limited to 'src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/generate.toc.xml') diff --git a/src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/generate.toc.xml b/src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/generate.toc.xml new file mode 100644 index 0000000..d23c45e --- /dev/null +++ b/src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/generate.toc.xml @@ -0,0 +1,108 @@ + + +generate.toc +table + + +generate.toc +Control generation of ToCs and LoTs + + + + + +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 + + +/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 +reference toc,title +/sect1 toc +/sect2 toc +/sect3 toc +/sect4 toc +/sect5 toc +/section toc +set toc,title + + + + +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 +of chapter 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. + + -- cgit v1.2.3