Hi Scott,
The "DITATopicCustomRuleMatcher" java class is where the magic happens :)
It's quite hard to identify a DITA topic or map, it could use the base
public IDs or it could refer to specialization DTDs, it could have
various root element names, but the "DITATopicCustomRuleMatcher" Java
c
Thanks, Radu!
That's sorta what I was assuming, but wanted to make sue there wasn't
some special reason that entry was needed for "all" DITA-based
frameworks. Yes, after removing the "DITATopicCustomRuleMatcher" java
class entry, the matching seems to work as expected. Nice. Simple is
good.
