Implementation of the guidance in this section is required for leiden conformance.
Traditional typographic representation
- Panciera, p.18; Dohnicht, p.4:
- [ - - - - - - - - - - - - - - - - - - ] /
- not addressed
- - - - - - - - - - - - - - - - - -
- not addressed
EpiDoc Encoding
- <gap reason="lost" extent="1" unit="line" />
- <gap reason="lost" unit="line" extent="unknown" />
- <gap reason="lost" unit="line" extent="unknown" dim="top" />
- <gap reason="lost" unit="line" extent="unknown" dim="bottom" />
EpiDoc appearance with standard XSLT
- [ - - - - - - - - - - - - - - - ]
- [ - - - - - - - - - - - - - - - ]
- [ - - - - - - - - - - - - - - - ]
- [ - - - - - - - - - - - - - - - ]
Notes
- The first example indicates complete certainty that a single, entire line of text has been lost.
- The second example indicates complete certainty that some unknown number of entire lines of text have been lost.
- The third and fourth examples indicate that some number of lines have been lost from the top or bottom of the text respectively (Krummrey-Panciera do not distinguist between these two cases, although some transcription schemes do). These cases were previously grouped under a separate heading ("One or more lines completely lost at the beginning or end of a text or fragment (extent uncertain)") in an older version of the Guidelines.
- For indications of uncertainty about whether lines of text have been lost or not, see Possibility that letters have been completely lost.
- NB: values of extent greater than 1, when combined with unit="line" are unsupported by the standard xslts; therefore, each separate lost line should be encoded as a separate <gap>, with appropriate line breaks (vel sim.) separating them.
Responsibility for this section
- author: Gabriel Bodard
- author: Tom Elliott
CVS Information
Revision number: $Revision: 1.15 $
Revision name (if any): $Name: r-5 $
Revision date: $Date: 2007/06/06 16:45:54 $
Revision committed by: $Author: gabrielbodard $