An entire line completely lost (extent certain or uncertain)

xml version || id: lostline|| traditional typographic representation | regular expression test | epidoc appearance with standard xslt | notes | responsibility for this section | cvs information || post a comment

Traditional typographic representation

Regular Expression Test

EpiDoc Encoding

  1. <gap reason="lost" extent="1" unit="line" />
  2. <gap id="gap23" reason="lost" unit="line" /> <certainty target="gap23" locus="extent" degree="low" />

EpiDoc appearance with standard XSLT

  1. [ - - - - - - - - - - - - - - - ]
  2.  - - - - - - - - - - - - - - - 

Notes

  1. The first example indicates complete certainty that a single, entire line of text has been lost.
  2. The second example indicates complete certainty that some unknown number of entire lines of text have been lost.
  3. For indications of uncertainty about whether lines of text have been lost or not, see Possibility that letters have been completely lost.
  4. 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

CVS Information

Revision number: $Revision: 1.12 $

Revision name (if any): $Name: r-4-beta-1 $

Revision date: $Date: 2006/04/18 21:19:01 $

Revision committed by: $Author: paregorios $