Re: How can I treat a <mapref> as a level of TOC hierarchy?
toggle quoted messageShow quoted text
I don't work with bookmarks but use map so I'm not sure of all the title derails. Sub maps do not interject structure and then don't introduce their own titles, they disappear as you have seen. The OT strip the map elements and chains them together during processing.
You had the right solution with the topic head, just make that the first element in your bookmap (if allowed). Put a simple title on the bookmap itself and make the text of your topchead contain the conditions to make the correct title.
Sent from my Verizon, Samsung Galaxy smartphone
Hi fellow DITA users,
-------- Original message --------
From: Chris Papademetrious <chrispitude@...>
Date: 6/19/21 7:41 AM (GMT-08:00)
Subject: [dita-users] How can I treat a as a level of TOC hierarchy?
We are exploring Oxygen's WebHelp Responsive transformation, so I am exploring DITA-OT chunking to understand how to control the help structure.
I have multiple <bookmap> files referenced from a top-level <map>:
When I publish this (as WebHelp or as plain html5), the <bookmap> levels evaporate and I get a flat TOC of all book chapters:
But what I need is for each book to provide its own navigation level derived from its book title:
Wrapping each <mapref> in a <topichead> creates a level, but that approach doesn't inherit the book title. (Our books are conditional and often have conditional text, references to variables *within* the book scope, etc.).
I looked at the @chunk attribute documentation and experimented, and:
Books are big, important things. Hopefully there's a way to do this!