Other than the xref issue discussed in another thread, the map to ditabook functions not badly. Except, as also mentioned in yet another thread, all the fm-ditabook and fm-ditafile elements being red, so invalid, which doesn't really seem to inhibit book making.
However, my book map has, as chapters, other ditamaps. The top chapter topic comes in and is formatted properly by my edd/template. Sub-topicrefs, those within the chapter topicref, however, come in wrapped in their own fm-ditafile element, at the same level as the parent topic, and end up promoted. That is, whereas I'd intended them to be Heading2 entries, they are shown as Heading1.
Currently, I'm handling this my hand rearranging those contained fm-ditafile elements to fall under the parent topic. If I do that, I can also unwrap them, since the wrapper element now does nothing.
To those with more experience, is that a normal way of working?
I've not tried this, but it occurs to me that I might be able to edit the edd/topic files to accommodate fm-ditafile, to recognize it as a context to consider in deciding what style to apply. Would this be a better way to go? Can I even do it, given that the application regards these elements as invalid?
This whole area could use considerably more documentation than I'm seeing.
Presumably, the Leximation solution makes it all good, but I'm not looking forward to asking for even another $185 from my company atm.
Thanks
Bruce
However, my book map has, as chapters, other ditamaps. The top chapter topic comes in and is formatted properly by my edd/template. Sub-topicrefs, those within the chapter topicref, however, come in wrapped in their own fm-ditafile element, at the same level as the parent topic, and end up promoted. That is, whereas I'd intended them to be Heading2 entries, they are shown as Heading1.
Currently, I'm handling this my hand rearranging those contained fm-ditafile elements to fall under the parent topic. If I do that, I can also unwrap them, since the wrapper element now does nothing.
To those with more experience, is that a normal way of working?
I've not tried this, but it occurs to me that I might be able to edit the edd/topic files to accommodate fm-ditafile, to recognize it as a context to consider in deciding what style to apply. Would this be a better way to go? Can I even do it, given that the application regards these elements as invalid?
This whole area could use considerably more documentation than I'm seeing.
Presumably, the Leximation solution makes it all good, but I'm not looking forward to asking for even another $185 from my company atm.
Thanks
Bruce