Implementation of the guidance in this section is required for leiden conformance.
This section of the guidelines requires revision in concert with DTD changes to realize the solution reached in long, painful discussions on the markup and tei lists. What follows now is almost surely deprecated.
In cases where a letter trace is compatible with a range of characters and the context does not offer an unambiguous choice but the editor wishes to record the possibilities, the alternative interpretations may be offered in a series of <rdg> elements within an <app>. In addition, a <rdg> with the attribute n='default' should contain the <gap reason="illegible"> (see e.g. 5 above).
It is also envisaged that the possibility will exist to record the general shape of the surviving traces using embedded SVG or similar elements which could then be rendered as a drawing.
Where the editor wishes to indicate a preferred reading, see unclear.
Revision number: $Revision: 1.10 $
Revision name (if any): $Name: r-5 $
Revision date: $Date: 2006/10/30 12:05:36 $