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 --- .../params/process.empty.source.toc.xml | 39 ++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/process.empty.source.toc.xml (limited to 'src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/process.empty.source.toc.xml') diff --git a/src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/process.empty.source.toc.xml b/src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/process.empty.source.toc.xml new file mode 100644 index 0000000..772b456 --- /dev/null +++ b/src/engine/SCons/Tool/docbook/docbook-xsl-1.76.1/params/process.empty.source.toc.xml @@ -0,0 +1,39 @@ + + +process.empty.source.toc +boolean + + +process.empty.source.toc +Generate automated TOC if toc element occurs in a source document? + + + + + + +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. + + + + + -- cgit v1.2.3