From ce4a32fe52ef09d8f5ff1dd22c001110902b60a2 Mon Sep 17 00:00:00 2001 From: toma Date: Wed, 25 Nov 2009 17:56:58 +0000 Subject: Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdelibs@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- .../xsl/params/process.empty.source.toc.xml | 33 ++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 kdoctools/docbook/xsl/params/process.empty.source.toc.xml (limited to 'kdoctools/docbook/xsl/params/process.empty.source.toc.xml') diff --git a/kdoctools/docbook/xsl/params/process.empty.source.toc.xml b/kdoctools/docbook/xsl/params/process.empty.source.toc.xml new file mode 100644 index 000000000..933d14560 --- /dev/null +++ b/kdoctools/docbook/xsl/params/process.empty.source.toc.xml @@ -0,0 +1,33 @@ + + +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. + + 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