Lou Burnard wrote:
[...] The Guidelines say quite explicitly that if that's what you want to do, you should use <text> not
Well, if only the decision would be that easy. As I said, most problems arise when you are already 98% satisfied with the solutions of the documentary markup. And you wouldn't want to exchange your dimensioning and positioning of surfaces, zones and lines for a couple of <lb/> or <pb/> elements. There are plenty good reasons for using <sourceDoc> and it's children. But then you just need (or think you need) some extra information like nominal references ...
I perfectly understand the intention to keep it straight and simple. Just like in most areas of life. But I'm still waiting for things (and people, for that matter) to comply to this healthy wish.
The XSLT solution (using <text> and then automatically generate my <sourceDoc>) may be worth considering, though.