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.
Thank you for your comprehensive bug report!
The problem comes from this kind of topicref:
---
<chapter href="chapter1.ditamap" format="ditamap" />
---
In this specific case,
* Either, ditac does not implement the DITA specification like the DITA-OT;
* Or more simply, it's a bug in our implementation.
Hence, the problem you report.
In either case, we'll have to carefully re-read the DITA specification
in order to learn exactly what to do.
For your use case:
---
<chapter href="chapter1.ditamap" format="ditamap" />
---
where:
"chapter1.ditamap" is:
---
<map>
<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>
---
what to do seems obvious.
But what if the referenced map contained *several* topmost topcirefs?
What if some of the topmost topcirefs were *parts* or *appendices*? What
if the referenced map also contained *reltables*?
---
PS: The public identifier of a bookmap is:
"-//OASIS//DTD DITA BookMap//EN"
and not:
"-//OASIS//DTD DITA Bookmap//EN"
You should fix this in your bookmaps, as this prevents XML catalogs from
doing their job.
--
XMLmind DITA Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/ditac-support
