On 06/10/2016 11:20 AM, Martti Poutanen wrote:
The problematic map I had, contained a slight bug
that I didn't notice earlier, @class for map's topicmeta was empty instead
of being '- map/topicmeta ' . Fixing that made both maps behave correctly.
You say that map/topicmeta does not propagate across nested topicrefs, I
have tested now with versions 2.5.1 and 2.5.6 (haven't yet downloaded the
latest), both propagate now the map metadata correctly to topics. Did I
misunderstood something in your response ..;)
What I said in my previous email was not 100% correct. There is indeed a
bug but the exact description of this bug is:
metadata is not correctly copied from topicref's topicmeta to topic's
prolog. It is copied only in the case of topicrefs having an @href,
whether nested or not.
I'm talking here about "Reconciling topic and map metadata",
docs.oasis-open.org/dita/v1.2/os/spec/archSpec/reconciling-topic-and-map-metadata.html.
It's not a regression compared to v2.5.x.
Example:
<map>
<topicref href="t1.dita">
<topicmeta><data name="key1" value="value1"/><topicmeta>
</topicref>
<topichead navtitle="My Title">
<topicref href="t2.dita">
<topicmeta><data name="key2" value="value2"/><topicmeta>
</topicref>
</topichead>
</map>
t1.ditac (preprocessed t1.dita) ended up with a prolog containing <data
name="key1" value="value1"/>, which is correct.
t2.ditac (preprocessed t2.dita), being referenced in the map using a
nested topicref, did not end up with a prolog containing <data
name="key2" value="value2"/>, which is incorrect.
This bug is fixed in ditac v2.6.1 to be released in a couple of weeks.
--
XMLmind DITA Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/ditac-support
