🚀 go-pugleaf

Thanks, Scott. I'll look at the Lex stuff today or tomorrow. (Alas, my company has a history of not understanding the kind of higher math you suggest. ;) But I will make the appeal if I decide to go that way.)

I think I correctly understand the relations of ditamaps and hierarchy, but could always be mistaken in my beliefs. I did, however, just test my understanding against how dita-ot generates html from the same ditamap, and the hierarchy produced is as I expected. So, I expect it's an issue with FM's ditabook generator. So far so good.

A little more graphic detail, for the record. The top ditamap has:

map
 ..topicref
 ....[fm-topicreflabel]Collections.ditamap

collection.ditamap has:

map
 ..topicref
 ....[fm-topicreflabel]Collections.xml
 ....topicref
 ......[fm-topicreflabel]CollectionClass.xml
 ....topicref
 ......[fm-topicreflabel]CollectionCreate.xml
 etc.

HTML output is as expected, with the topic from Collections.xml as H1, and the topics from CollectionClass.xml and CollectionCreate.xml as H2.

The structure in the ditafile becomes:

[fm-ditafile] href=Collections.ditamap
 ..[fm-ditafile] href=Collections.xml
 ....[topic] Collections
 ....[fm-ditafile] href=CollectionClasses.xml
 ......[topic] Collection Classes
 ....[fm-ditafile] CollectionCreate.xml
 ......[topic] Creating a Class
etc.

The structure appears ok, and one might think that the heading levels would be appropriate. But, the top level headings of all three files are being formatted as the equivalent of H1.

I see two possibilities.

One is that the second and third fm-ditafile elements should *not* be at the same level as the topic, but nested under it. If that's true, then FM is at fault, and editing of the appropriate xslt file is necessary (or, continue with my current hand-edit process).

The other is that this structure is correct, and I really should accommodate it by editing the edd to treat the fm-ditafile elements as contexts for applying styles. (Assuming the illegitimate (red) elements are accepted at all as contexts, which I've not tried.)

I could go either way. My real issue is that I don't have enough information on how Adobe intends these fm-ditafile elements to function in order to determine the better course. There's something wrong somewhere in what Adobe provides, but I don't know if this particular effect is their error or mine.

Bruce