On 06/10/2016 11:20 AM, Martti Poutanen wrote:
Thanks for rapid response. 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.
In principle, there is no need to specify the class attribute by hand.
If your DITA file references a schema of any kind: DTD or W3C XML Schema
(even RELAX NG as of ditac v2.6.0), the class attribute is automatically
given its default value, this default value being specified in the schema.
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 ..;)
No. I made some tests using version 2.6.0 and it did not work as
expected. May be it's a regression.
Please allow me a couple of days to investigate on this and I'll get
back to you after doing this.
We have pretty complicated metadata model to control various things in the
application. One little issue has been to detect reliably whether we make
pdf from map or from single topic in Ditac. Could we use this metadata
reconcile ( 2 vs 1 prolog/metadata nodes in .ditac ) to differentiate
between map pdf vs topic pdf.
Yes. Something like this in the map could work too.
<topicref ...
<topicmeta>
<data name="from-map" value="yes"/>
</topicmeta>
Or something from lists file?
No, there is nothing which could help you in the ditac_lists.ditac_list
file.
Reference: "Chapter 11. Extensive customization"
http://www.xmlmind.com/ditac/_distrib/doc/manual/howItWorks.html
--
XMLmind DITA Converter Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/ditac-support
