dita — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Fwd: [dita] TractorX Example
Eliot, In this example, your point is quite relevant as they are outputting to HTML.
If I understand you correctly, in order to have new result instances for each set of keys the author would have to manually set a copy-to whenever the key definitions were different.
To avoid this manual effort, this proposal would need to suggest either
1) a blind treatment of all topics with a keyref to be treated as though @copy-to were specified or
2) a complicated analysis to determine if the keys result in differences so that only the different results are treated with an automated @copy-to.
Does one or the other of these options need to be explicitly included in this proposal?
If so which one is being suggested?
I would certainly favor the later for ease in authoring and more streamlined output, even recognizing the resulting processor overhead.
Best, Dawn
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]