Good day all,
I'm hoping one of you experts might be able to shed some light on the implications of setting the preprocess.chunk.skip parameter?
To give some background, one of our customers reported an issue with duplicated glossary data as follows:
We notice strange behavior when publishing
a ditamap with the audience values stored in the dita topics
(instead of the ditamap).
I attached a ZIP file with 2 glossary test
maps:
- _glossary_map_filtering.ditamap:
this ditamap has the filtering values stored in the ditamap.
This works fine when publishing to Miramo PDF.
- _glossary_topic_filtering.ditamap:
this ditamap has no filtering values stored in the ditamap.
The audience attributes are stored in the individual
ditafiles. Publishing this map to Miramo PDF results in duplicated glossary entries
The intermediate topicmerged DITA produced as part of the MiramoPDF DITA-OT plugin included a lot of duplicate glossary information, which duly found its way into the final PDF.
After some digging I found that setting the 'preprocess.chunk.skip' parameter to 'true' prevents the duplication of data.
My question is, is it safe to always set the parameter to 'true' or might that have repercussions? I notice the supplied glossary_topic_filtering.ditamap contains this @chunk attribute:
<topicref chunk="to-content" href="to_glossary.dita" id="id-26d4c46f-cefb-4f21-868a-b9ffaf037d4f">
TBH I don't understand 'chunking' so any feedback would be gratefully received!
Many thanks in advance