Hi All,
This may be common question about “TopicMerge". But it is needed for me to realize user requirement.
One of my user uses DITA-OT (1.7.5) and my plug-in to generated PDF for printing. They have a strict paging requirement to reduce page count as little as possible. To do this they requested me to control chapter level paging control like following.
<bookmap>
<mainbooktitle>PDF for printing</mainbookmap>
<chapter navtitle="Chapter 1" href="chapter-1.ditamap" format="ditamap"/>
<chapter navtitle="Chapter 2" href="chapter-2.ditamap" format="ditamap" outputclass="auto-even"/>
<chapter navtitle="Chapter 3" href="chapter-3.ditamap" format="ditamap" outputclass="auto-odd"/>
<chapter navtitle="Chapter 4" href="chapter-4.ditamap" format="ditamap" outputclass="auto"/>
<chapter navtitle="Chapter 5" href="chapter-5.ditamap" format="ditamap" outputclass="auto-odd"/>
<chapter navtitle="Chapter 6" href="chapter-6.ditamap" format="ditamap" outputclass="auto-even"/>
…
</bookmap>
In this case fo:page-sequence is generated per chapter element and @outputclass should be converted into fo:page-sequence/@initial-page-number by plug-in stylesheet. But if chapter/@href point to sub map, all of the chapter attribute is removed after “TopicMerge" (including @outputclass). Instead the referenced topicref attributes in the sub map are set in the merged middle file. This is not desired result for me because we want control pagination in bookmap level, not sub map level.
Are there any way to retain chapter/@outputclass or specialized chapter attributes in the result merged middle file?
Thanks,