On 12/30/2017 11:00 PM, Leif Halvard Silli wrote:
See the ditamap file, with a bookmark element, and its 3 dita files that
are attached to this message.
When converting this ditamap to an output format (XHTML, PDF etc), the
following can be observed:
1. To /exclude/ a chapter from the ToC by setting toc="no" on a chapter
element, this works fine.
2. But to /include/ the preface or the figure list - by setting
toc="yes" on the corresponding preface element and the figurelist
element, this does *not* work.
3. The document does not demonstrate the following issue, however, to
set toc="yes" on the veru toc element also does not have any effect.
In fact, sofar, I have not been able to make toc="yes" to work on
element.
And, related: According to the DITA spec,[1] the @toc can be applied to
the map (or bookmap) element. If you set it to <bookmap toc="yes">, then
all the child elements for which the toc attributes applies, will behave
behave as if they had their own @toc set to toc="yes". However, while
<bookmap toc="no"> /does work/, <bookmap toc="yes"> does *not* work.
[1]
http://docs.oasis-open.org/dita/dita/v1.3/os/part2-tech-content/archSpec/base/cascading-in-a-ditamap.html#cascading-in-a-ditamap
To our knowledge, cascading of attributes, including @toc, is
implemented correctly by XMLmind DITA Converter.
However the fact that a topicref has or "inherits" toc="yes" does not
mean that this topicref will necessarily appear in the generated TOC.
Our implementation have limitations and specificities related to the
generation of the TOC:
1) The default is toc="yes" for all topicrefs pointing to "book sections".
2) If you want a booklist (which obviously do not point to a "book
section") to appear in the TOC, you'll have to pass XXE/ditac XSLT
stylesheet parameter
extended-toc="both"
See
http://www.xmlmind.com/ditac/_distrib/doc/manual/webhelp2/xsltParams.html#xsltParams__extended-toc
3) There is no way to get the TOC appear in the TOC. That is, (2) works
for all booklists but <toc>.
I'm sorry but even if our implementation is not fully conforming to the
DITA spec regarding the generation of the TOC, we do not plan to change
our implementation in the near future.
---------------------------------------------------------------------
If full conformance to the DITA spec is very important to you, please
consider switching to the DITA Open Toolkit:
- The DITA Open Toolkit is the de-facto reference implementation of the
DITA spec.
- The DITA Open Toolkit is used by all DITA tool vendors in the world,
but XMLmind.
- The DITA Open Toolkit has a very reactive support list (even if the
title of the mailing list suggests that it is about DITA, and not about
the DITA Open Toolkit):
dita-us...@yahoogroups.com
https://groups.yahoo.com/neo/groups/dita-users/info
If you use it, you'll get answers to your questions by the greatest DITA
experts in the world. However, for that, you really need to use the DITA
Open Toolkit and not XMLmind DITA Converter.
---------------------------------------------------------------------
References:
- XMLmind DITA Converter Manual, Appendix B. Limitations and
implementation specificities
http://www.xmlmind.com/ditac/_distrib/doc/manual/limitations.html#limitations
- DITA Open Toolkit
http://www.dita-ot.org/
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
