toggle quoted messageShow quoted text
Easy. You can extend the dita normalization plugin but skip certain modules in processing by initializing build parameters based on the steps you don’t want to perform.
Sent from mobile
On May 22, 2021, at 8:44 AM, Alan Houser <firstname.lastname@example.org> wrote:
A follow-up to this question, about which I acknowledge that I've done zero research ...
What's the level of difficulty of writing a plugin that does "just filtering", or "just conref resolution"; producing clean DITA source files that mimic the originals (modulo filtering and/or conref resolution)? Use case would be to hand off DITA source to a partner or to another processing chain.
On 5/20/21 12:27 PM, Alan Houser wrote:--
I'm trying to figure out whether behavior I'm seeing from the DITA-OT normalization plugin is by design.
I have a parent map, with maprefs to other maps. The referenced maps include map-level metadata in <topicmeta>.
After DITA-OT normalization, the maprefs are resolved, and the parent map references all resolved topics directly (as expected). But since the parent map no longer references the child maps, the map-level metadata on the child maps is essentially unavailable for further processing. (The child maps are also normalized and copied to the output folder, but there's no longer a relationship between the original "parent" and child maps).
Of course, I need the map-level metadata on the child maps. And I don't see a normalization option for "don't resolve maprefs".
If I'm missing an option, approach, or explanation, I would be grateful to hear it.
Group Wellesley, Inc.
Consultant and Trainer, Technical Publishing
arh on Twitter