On 21.2.2012 10:09, Hussein Shafie wrote: > In all the books (published by a variety of publishers) we have examined > before implementing ditac, we have found that it is *not* customary to > have preface or index entries appear in the TOC. That's why this feature > has not been not implemented.
I see, but there are so many designs that this should be definitively
under user or stylesheet control.
> Moreover, the DITA standard does not seem to indicate that such entries
> may be added to the TOC or how (i.e. which attribute? navtitle? toc?)
> such entries could be added to the TOC.
In my understanding toc attribute is suitable for this purpose.
>> I understand that in order to fix these issues changes in Java part of
>> ditac are needed.
>
> No. I don't think so. In principle, the ditac_lists.ditac_list file
> contains all the information needed to add the missing entries to the
> TOC. (Otherwise this would be a flaw in the design of the
> ditac_lists.ditac_list file.)
Of course I can inject ditac_lists.ditac_list file easiy by using XSLT,
but it would be easier (no need to orchestrate my transformations with
ditac) and cleaner to have such additional entries added directly inside
ditac:toc as ditac:tocEntry elements by preprocessor.
However I'm little bit list in Java code for preprocessor.
> After you modify xsl/fo/ditac_figureList.xsl and
> xsl/fo/ditac_indexList.xsl in order to give *fixed* ids to these
> components (e.g. id="__LOF", id="__LOT", id="__IDX" -- this is
> implemented like that in xsl/xhtml/*.xsl), then you'll have everything
> you need to add the corresponding entries to the TOC and to the PDF
> outline.
I thought that having additional ditac:tocEntry inside
ditac_lists.ditac_list is the correct way to implement this feature.
> No. Please understand that we are a small company, that all our software
> engineers are very, very busy and that we definitely cannot distract
> them from their current tasks.
I see, thanks for your email assistence.
> Here's what I suggest: [1] feel free to patch ditac v2.1.0_01 as you
> want [2] send us a copy of the patched sources [3] we'll make sure that
> the next release of ditac is *functionally* superior or equal to the
> patched version you sent us. However, we cannot guarantee that the next
> release of ditac will be 100% compatible with yours in terms of
> command-line options, XSLT stylesheet parameters, etc.
Indeed, that's reasonable approach. I understand that my changes can't
be applied without changes for various reasons. After all it is your
product :-)
Thanks and have a nice day,
Jirka
--
------------------------------------------------------------------
Jirka Kosek e-mail: [email protected] http://xmlguru.cz
------------------------------------------------------------------
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------
signature.asc
Description: OpenPGP digital signature
-- XMLmind DITA Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/ditac-support
