After carefully looking at the problem you describe, we have found the
culprit.
In a nutshell, it's your use of DITA files containing multiple topics
(anyway, this is not recommended) and more importantly, the way you pull
these topics from the map.
In chapter1.ditamap:
---
<map xml:lang="de">
<topicref href="chapter1_topic1.dita">
<topicref href="chapter1_topic11.dita">
<topicref href="chapter1_topic11.dita#mysubtopic1" />
<topicref href="chapter1_topic11.dita#mysubtopic2" />
</topicref>
<topicref href="chapter1_topic12.dita" />
</topicref>
</map>
---
you need to replace:
---
<topicref href="chapter1_topic11.dita">
---
by:
---
<topicref href="chapter1_topic11.dita#chapter1_topic11">
---
because with ditac (unless you use the "chunk" attribute for screen
deliverables), <topicref href="chapter1_topic11.dita"> pulls *all* the
topics contained in chapter1_topic11.dita.
Once all the topics of chapter1_topic11.dita have been pulled, the
subsequent topicrefs:
---
<topicref href="chapter1_topic11.dita#mysubtopic1" />
<topicref href="chapter1_topic11.dita#mysubtopic2" />
---
have no effect on the deliverable. Hence no proper nesting for
mysubtopic1 and mysubtopic2.
--> This specificity is clearly documented here:
http://www.xmlmind.com/ditac/_distrib/doc/manual/limitations.html
Please take the time to read the first item of section "Other
limitations and specificities".
If you think that our current implementation does not comply with the
DITA 1.2 specification, then we'll be glad to change it.
However for this to happen, you need to point us to the corresponding
section of the DITA 1.2 specification.
I'm afraid that just saying that the DITA OT do it otherwise is not
sufficient for us to change our implementation.
On 03/12/2014 02:07 PM, Peter Jatzlauk wrote:
Thanks for your fast reply and sorry for not sending a usable bug report
first time. Here are the requested further details.
----------------------------------------
Problem Description:
I have one issue with generated PDFs using fop compared to DITA-OT.
DITA-OT produces the following toc:
Chapter 1
Topic 1
Topic 1.1
Topic 1.2
Topic 2
Chapter 2
...
DITAC creates a flat outline (wrong behavior):
Chapter 1
Topic 1
Topic 1.1
Topic 1.2
Topic 2
Chapter 2
...
Topic 1.1 and 1.2 shouldn't be on the same level like topic 1.
----------------------------------------
----------------------------------------
Version Information:
DITA Converter:
2.51
OS:
Windows 7 Professional
Java:
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
DITA-OT:
1.8.M2
----------------------------------------
----------------------------------------
ditac command-line:
bin\ditac -o testbook.options out\testbook.pdf
..\TEST\DITA\testbook.ditamap
----------------------------------------
----------------------------------------
Contents testbook.options:
-p pdf-outline 'yes'
----------------------------------------
----------------------------------------
Attached Files:
testbookditac.pdf DITAC-generated PDF
testbookditaot.pdf DITA-OT-generated PDF
*.ditamap and *.dita DITA files
----------------------------------------
Cordialement vôtre
Peter Jatzlauk
> Hussein Shafie <[email protected]> hat am 12. März 2014 um 12:54
geschrieben:
>
>
> As explained here:
>
> http://www.xmlmind.com/ditac/support_policy.html
>
> you need to send us a set of DITA files allowing us to reproduce the
> problem you describe.
>
> In your case, this is *absolutely* *needed* because, in principle, ditac
> has no such bug. See for example the DITA 1.2 specification converted to
> PDF by ditac/FOP:
>
> http://www.xmlmind.com/ditac/_dita_spec/dita-1.2-specification_fop.pdf
>
> Notice how subsections are correctly nested and correctly numbered in
> the TOC.
>
>
>
>
> On 03/12/2014 09:49 AM, Peter Jatzlauk wrote:
> > Bonjour Pixware,
> >
> > I have downloaded DITAC and ran some tests on different existing DITA
> > documents. Great piece of software, good documentation and easy to
> > handle! Thanks for it.
> >
> > I have one issue with generated PDFs using fop compared to DITA-OT.
> > DITA-OT produces the following toc:
> >
> > Chapter 1
> >
> > Topic 1
> >
> > Topic 1.1
> >
> > Topic 1.2
> >
> > Topic 2
> >
> > Chapter 2
> >
> > ...
> >
> > DITAC creates a flat outline (wrong behavior):
> >
> > Chapter 1
> >
> > Topic 1
> >
> > Topic 1.1
> >
> > Topic 1.2
> >
> > Topic 2
> >
> > Chapter 2
> >
> > ...
> >
> > Topic 1.1 and 1.2 shouldn't be on the same level like topic 1.
> >
> > Any ideas how to solve this issue?
> >
> > Merci!
> >
> > Cordialement vôtre
> >
> > Peter Jatzlauk
> >
--
XMLmind DITA Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/ditac-support
