Happy new year!

On 31 Dec 2017, at 9:41, Hussein Shafie wrote:
On 12/30/2017 11:00 PM, Leif Halvard Silli wrote:
   [ ... snip ... ]
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.
   [ ... snip ... ]

[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:

Just curios: Are the limitations and specifities related to the generation of the TOC permitted by the DITA specs?

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"

Thanks. (And adding that paramenter is - in XMLmind XML editor - very simple to do.)

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>.

While that would be welcome, I mentioned the lacking inclusion of <toc> in the generated Table of Contents mostly for completeness. My primary concern was about inclusion of <preface>. And it is also great to be able to include the various other book lists (except 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.
  [ ... snip ...]
If full conformance to the DITA spec is very important to you, please consider switching to the DITA Open Toolkit:

Thanks. But at the time being, ability to include the <toc> in the Table of Contents is not enough for me to wanto going through the work of learning the DITA Open Toolkit.
--
leif halvard silli

--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to