Chris Papademetrious

@jelovirt - four navtitle-evaluation code paths can fail when `` or `` exist. For example, ``` ``` But then I realized that there are possibly places beyond navtitle evaluation that...

@jelovirt - sure, just let me know where you'd like the fix.

As soon as I get a final "go" from @jelovirt or @robander, I will modify the pull request to fix the issue in `topicpull` instead. (Would it make for a...

@jelovirt, @robander - I updated the fix to never apply `` to footnote cross-references in `topicpull`, and rely entirely on the transtype templates to apply any formatting. Given the following...

I've rebased the fix to `develop`, but I need some help testing the fix on all the transformation types. After running `gradlew dist`, only the following transformation types are known:...

@smitabh84 - there is no testcase and no information about what type of transformation you are running. If you feel this is a bug, please provide the smallest testcase that...

Unfortunately, this bug also affects `preprocess`. When `force-unique` is set to `true`, duplicate copies of _all topics in the submap_ are created. For example, if I add two subtopics to...

Also, some related discussion here: [DITA Users - "Does a key reference to a `` have any meaning?"](https://dita-users.groups.io/g/main/topic/90788101)

@SoonBoonChin - thank you for sharing your findings! I am always hesitant to change the default ordering of preprocessing steps for our production processing, but I think it's good information...

We would also like to see unresolved keys always be considered an `ERROR`. Missing content is unacceptable in production and should cause a build to fail so the issue can...