I'm working with a critical edition that uses the <app><rdg>...</rdg></app>
strategy to deal with alterations in a single manuscript. (The reason
for not simply relying on <del>, <add>, etc. has partly to do with the
editorial theory behind the edition, one which in effect sees
composition as a sequential series of "witnesses" all of whom are the
same author at different moments. If that makes sense.)
Anyway, in working on an XSLT stylesheet for rendering things, I've
realized that there's a problem in that the content of an <rdg> element
is variously a single word, multiple words, or a part of a word. This
leads to whitespace problems in rendering, for example if
I saw th<app><rdg varSeq="1">is</rdg><rdg varSeq="2">e</rdg></app> man
gets changed to
I saw th
The latter is much more human-readable, but when processed it may yield
something like "I saw th is e man". Using xsl:strip-space will prevent
this, but will also squash together things that should in fact be
I see two strategies for dealing with this:
1. Treat <app> strictly as a mixed-content-containing element and allow
linebreaks within it only where they correspond to word boundaries.
Be very careful not to reformat the source XML.
2. Use the "type" attribute on <rdg> to distinguish between whole- and
partial-word readings, and break lines with wild abandon.
Thoughts on which is better practice?
David Sewell, Editorial and Technical Manager
Electronic Imprint, The University of Virginia Press
PO Box 400318, Charlottesville, VA 22904-4318 USA
Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903
Email: [log in to unmask] Tel: +1 434 924 9973