Expected behavior of map-level <othermeta>?

[Alan Houser]

Colleagues,

I'm developing a customization of PDF2 (DITA-OT 3.4) in which I'm stuffing some cover content into <othermeta> name/content attribute value pairs in the bookmap (DITA 1.3).

In stage1.xml, the bookmap <bookmeta>/<othermeta> appears to be copied into each resolved <topicref> and into the prolog of each resolved topic. (I'm seeing this result from the base PDF2 plugin).

Is this expected behavior? It's causing some unwanted side-effects in my customization.

TIA!

-Alan

[Radu Coravu]

Hi Alan,

The DITA specs seems to state for each metadata element if it is added inside of the referenced topic or not:

https://www.oxygenxml.com/dita/1.3/specs/archSpec/base/reconciling-topic-and-map-metadata.html

Regards,

Radu

--
You received this message because you are subscribed to the Google Groups "DITA-OT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dita-ot-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/dita-ot-users/CALRZhmyX6pLMTgxHFNWCoTZPgrjZ0yQ94JtA_KhikqghvMC2Dg%40mail.gmail.com.

[n7...@earthlink.net]

This is a bug. The spec page Radu links says <othermeta> should not cascade down. This was fixed in 3.5:

https://www.dita-ot.org/3.5/release-notes/index.html#v3.5__bugs

I had the same problem.

Mark G

[Alan Houser]

Thanks to Mark and Radu for your (always!) helpful replies!

-Alan