ResolvedValues log file? was Allow variables to be referenced from @scope="peer" maps
Hi Eliot,toggle quoted messageShow quoted text
The DITA-OT obviously has to resolve all the reuse mechanisms, and related content.
How feasible would it be to tap into this process, and for the DITA-OT to produce a log file of all the resolved content? Maybe as part of a build, or as its own build.
map id: topic id: element name: scope or branch: keys or ditaval: resolved content
This is an example of where a local, targeted solution is relatively easy (just a bit of preprocessing or relying on knowledge of cases that won't occur in your content) but the general solution would be hard (because it has to handle all cases, perform well, be extensible, report exception conditions clearly, etc.).