Transcription wherein vestiges of characters remain, but they cannot be recognized (extent certain or nearly so)

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.

Traditional typographic representation <xref href="bibliography.xml#panciera">Panciera</xref>, p.17; <xref href="bibliography.xml#dohnicht">Dohnicht</xref>, p.3: +++ + 10 + + c.10 + + 4.2cm + <xref href="bibliography.xml#seg">SEG</xref> [...] <xref href="bibliography.xml#poxy">POxy</xref> … ..........
EpiDoc encodings gap reason="illegible" extent="3" unit="character"/ gap reason="illegible" extent="10" unit="character"/ gap id="gap24" reason="illegible" extent="10" unit="character"/certainty target="gap24" locus="extent" degree="low"/ gap id="gap25" reason="illegible" extent="4.2" unit="cm"/apprdg n="default"gap id="gap25" reason="illegible" extent="1" unit="character"//rdgrdgunclearE/unclear/rdgrdgunclearF/unclear/rdg/app
EpiDoc appearance with standard XSLT EF
Notes
Alternative readings

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.

Responsibility for this section authorTom Elliott authorGabriel Bodard
CVS Information

Revision number: $Revision: 1.6.2.2 $

Revision name (if any): $Name: sandstorm $

Revision date: $Date: 2006/03/23 12:01:22 $

Revision committed by: $Author: gabrielbodard $