<!-- $Id: p2ph.odd,v 1.17 1998/02/05 17:14:35 tei Exp $ -->
<!--*
    **
    * $Log: p2ph.odd,v $
    * Revision 1.17  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.16  98/02/01  16:52:05  tei
    * change system identifiers to public identifiers
    * fix log keyword
    * normalize SGML
    *
    * Revision 1.15  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.14  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    *
    * Revision 1.13  1994/04/07  16:59:05  msmcq
    * Typo correction
    *
    * Revision 1.12  1994/04/01  16:31:57  msmcq
    * changes during validation of DTDs
    *
    * Revision 1.11  1994/03/28  17:52:51  msmcq
    * correct dtdref error
    *
    * Revision 1.10  1994/03/28  15:07:51  lou
    * fix ident tags
    *
    * Revision 1.9  1994/03/27  16:31:02  lou
    * se,mifnal techal
    *
    * Revision 1.5  1994/03/08  03:42:49  msmcq
    * validation fixes
    *
    * Revision 1.3  1994/02/11  23:04:12  msmcq
    * add RCS id, log keywords
    * -->
<!-- Revisions:                                               -->
<!-- 14 jan 98 : LB : more typos in egs -->
<!-- 7 jan 98 : LB : typos from MSM; also, revise discussion of HAND -->
<!-- 4 Jan 98 : LB : correct erroneous eg of damage -->
<!-- 94-04-07 : MSM : spell Voluspa correctly (NOT an umlaut!) -->
<!-- 94-03-30 : MSM : suppress ornamentation again (as per lb) -->
<!-- 94-03-29 : MSM : refer to space and ornament dtdfrags    -->
<!--                  from main fragment                      -->
<!-- 94-03-29 : MSM : add section on ornaments                -->
<!-- 94-03-29 : MSM : add handlist to dtdfrag                 -->
<!-- 94-03-07 : MSM : supply TYPE on adlist                   -->
<!-- 94-03-07 : MSM : changes as per CH                       -->
<!-- 94-03-07 : MSM : CH changes                              -->
<!-- 94-03-07 : MSM : partway through Claus's changes         -->
<!-- 94-03-04 : MSM : change edit class reference to editph   -->
<!-- 94-03-03 : MSM : changes, corrections from RC            -->
<!-- 94-03-03 : MSM : Robin Cover's fixes                     -->
<!-- 94-02-11 : MSM : Added RCS id                            -->
<!-- 94-02-04 : MSM : revisions (msm,pr)                      -->
<!-- 94-02-03 : MSM : move use-of-app section to TC           -->
<!-- 94-01-27 : MSM : fix idref problems, hack edit class (temp) -->
<!-- 94-01-27 : MSM : fix tagging problems                    -->
<!-- 94-01-27 : MSM : reached end.  Still need exx for skel   -->
<!-- 94-01-26 : MSM : begin first pass for P3                 -->
<!--                  rename omit as gap (as agreed w/LB)     -->
<!--                  correct underscores in ent names        -->
<!-- 93-06-03 : MSM : add editorial note                      -->
<!-- 27 May : LB fixed tagging; changed refs to PHce to PHhr  -->
<!-- 93-05-23 : PR: following Eynsham Hall meeting, ch..      -->
<!--                  split into two.  Fixes (editorial,      -->
<!--                  typos etc).  Cert and resp treatment    -->
<!--                  updated, subvariation added             -->
<!-- 93-04-12 : MSM : SGML corrections after validating.      -->
<!-- 93-04-12 : MSM : Addtl. SGML Changes                     -->
<!-- 93-04-12 : MSM : Addtl SGML changes                      -->
<!-- 93-04-09 : wp : More SGML corrections, mostly taglists. -->
<!-- 93-04-09 : wp : Various SGML corr. ( < / > and < / eg >. -->
<!-- 93-04-08 : MSM : strip mail header                       -->
<!--                  fix many, many SGML problems            -->
<!-- 31 MAR 93 : PR : minor changes, following suggestions    -->
<!--                  by Robin Cover etc, to second part      -->
<!--                  tidying up of first part                -->
<!-- 31 MAR 93 : PR : minor changes, following suggestions    -->
<!--                  by Claus Huitfeldt, to first part       -->
<!-- 27 MAR 93 : PR : incorporate examples, make changes      -->
<!--                  and additions re rdg/wit, restore, supplied -->
<!--                  transcription part given more substance to  -->
<!--                  incorporate mss group materials         -->
<!-- 93-03-01 : MSM : change N values on divs                 -->
<!-- 93-03-01 : MSM : change abbrev tag to abbr               -->
<!-- Chapter on Textual Criticism for P2                      -->
<!--                                                          -->
<!-- 27 Feb 93 : MSM : complete additions, light revision     -->
<!--                   to line 800                            -->
<!-- 21 Feb 93 : MSM : add tagdocs, revise very lightly       -->
<!--    Sep 92 : MSM : remove CO tags, add P2X tagging        -->
<!--  7 Sep 92 : MSM : received in Chicago                    -->
<!-- 12 Jun 92 : PR : revised following Chicago meeting.      -->
<!--                  Xrefs indicated by formula (xref xxx),  -->
<!--                  except for the one to feature           -->
<!--                  structures, indicated < xref            -->
<!--                  target = p2.44 >                        -->
<!--                  This document not oddified, despite my  -->
<!--                  good intentions.  Sorry, I quailed.     -->
<!-- 10 May 92 : PR : revised following discussions with MSMQ -->
<!--    Nov 91 : PR : draft, circulate to TR2                 -->
<!>
<!>

<div1 id="PH" n="18"><head>Transcription of Primary Sources</head>

<p>This chapter defines an optional additional tag set intended for use
in the transcription of primary sources, in particular manuscripts,
and describes how some
elements defined in the core tag set should be used for this work.  It
is expected that this tag set will be especially useful in the
preparation of critical editions, but the tag set defined here is
distinct from that defined in chapter <ptr target="TC">, and may be used
independently of it.

<!-- <note place=foot>Responsibility for this chapter was borne -->
<!-- by work groups TR 2 (Textual Criticism), headed by Peter -->
<!-- Robinson, and TR 9 (Manuscripts and Codicology), headed by -->
<!-- Claus Huitfeldt; the full membership of the work groups is -->
<!-- given in the front matter.  The draft was prepared by Peter -->
<!-- Robinson and Claus Huitfeldt, with extensive assistance from -->
<!-- Robin Cover.</note> --></p>

<p>Scholars may wish to record information concerning individual
readings of letters, words or larger units, both within transcriptions
and within editions.  They may also wish to include other editorial
material within transcriptions, such as comments on the status or
possible origin of particular readings, corrections, or text supplied to
fill lacunae, etc.  Further, it is customary in transcriptions to
register certain features of the source, such as ornamentation,
underlining, deletion, areas of damage and lacunae.  This chapter
indicates means to record such information:

<list type="bullets">

<item>first, the problem of recording editorial or other alterations to
the text, such as expansion of abbreviations, corrections, conjectures,
etc. (section <ptr target="PHch">)</item>

<item>then, methods of describing important extra-linguistic phenomena
in the source: unusual spaces, lines, page and line breaks, change of
manuscript hand, etc. (section <ptr target="PHph">)</item>

<item>finally, a method of recording material such as running heads,
catch-words, and the like (section <ptr target="PHsk">)</item>

</list></p>

<p>These recommendations are not intended to meet every
transcriptional circumstance likely to be faced by any scholar.
Rather, they should be regarded as a base which can be elaborated if
necessary by different scholars in different disciplines, with
distinct scholarly domains eventually developing their own document
types.  In time, the feature structure notation developed in chapter
<ptr target="FS">, may also permit scholars to tailor the encoding of
complex transcriptional information in ways not here anticipated.  In
particular, this chapter focuses in its current state primarily upon
problems associated with the transcription of manuscript materials;
problems of codicology and problems peculiar to early printed
materials are not treated.  Many of the recommendations presented here
may --- mutatis mutandis --- apply to printed matter, but a great deal
of work remains to done in these areas, and the encoder will need to
take even more individual responsibility than usual in applying the
recommendations of this chapter in these contexts.</p>

<p>Many of the descriptions below use terms like
<socalled>scribe</socalled>, <socalled>author</socalled>,
<socalled>editor</socalled>,
<socalled>annotator</socalled>,
<socalled>corrector</socalled>,
<socalled>transcriber</socalled>,
and <socalled>encoder</socalled>, to make
clear how they apply in cases where these roles are distinct.  To the
extent that these roles are not distinct (for example, in authorial
manuscripts where the author and the scribe are the same person) the
interpretation of the markup should be adjusted appropriately.
Many of the elements defined here apply (within limits) also in
cases of printed materials, so <socalled>compositor</socalled>, etc.,
may also be understood as applying where appropriate.</p>

<p>As a rule, all elements which may be used in the course of a
transcription of a single witness may also be used in a critical
apparatus, i.e. within the elements proposed in chapter <ptr
target="TC">.
This can generally be achieved by nesting a
particular reading containing tagged elements from a particular witness
within the <gi>rdg</gi> element in an <gi>app</gi> structure.

<!-- sentence omitted, since I don't understand what is       -->
<!-- meant and don't think we make good on this claim.        -->
<!-- (msm)                                                    -->
<!-- In certain cases, indicated below, such nesting will     -->
<!-- not be possible, and other means are suggested.          --></p>

<p>Just as a critical apparatus may contain transcriptional elements
within its record of variant readings in various witnesses, one may
record variant readings in an individual witness by use of the apparatus
mechanisms <gi>app</gi> and <gi>rdg</gi>.  This is discussed in section
<ptr target="TCtr">.
<!-- suggested addition by CH, with additional addition by    -->
<!-- MSM.  suppressed by MSM                                  -->
<!-- Applications of considerable sophistication may be       -->
<!-- needed to make full use of all the information which     -->
<!-- can be recorded using the tag set defined here.  In      -->
<!-- the absence of such applications, some scholars may      -->
<!-- feel that the present cost of more informative           -->
<!-- encoding outweighs the potential future benefits:  in    -->
<!-- such cases it may be preferred to record only the        -->
<!-- relatively simple information which can be captured      -->
<!-- with the suggestion applications of the core tag set     -->
<!-- described below.  It should also be kept in mind,        -->
<!-- however, that the capabilities of current software       -->
<!-- will often be wholly irrelevant when projects begun      -->
<!-- today are completed some years hence.                    --></p>

<p>The tag set defined in this chapter may be selected using the
mechanisms described in section <ptr target="STin">; in a document using
this tag set, the document-type-declaration subset should contain the
following declaration of the parameter
entity <ident type="pe">TEI.transcr</ident>, or the
equivalent:

<eg>
<![ CDATA [
<!ENTITY % TEI.transcr 'INCLUDE' >
]]>
</eg>

In a document using this tag set together with that for textual
criticism and the base tag set for verse, the entire document type
declaration might resemble the following:

<eg>
<![ CDATA [
<!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                       "tei2.dtd" [
   <!ENTITY % TEI.prose 'INCLUDE' >
   <!ENTITY % TEI.transcr 'INCLUDE' >
   <!ENTITY % TEI.textcrit 'INCLUDE' >
]>
]]>
</eg></p>

<p>The overall structure of the tag set defined by this chapter is as
follows:

<eg id=dph>
<![ CDATA [
<!-- 18:  Transcription of Primary Sources                    -->
<!-- Text Encoding Initiative: Guidelines for Electronic      -->
<!-- Text Encoding and Interchange. Document TEI P3, 1994.    -->

<!-- Copyright (c) 1994 ACH, ACL, ALLC. Permission to copy    -->
<!-- in any form is granted, provided this notice is          -->
<!-- included in all copies.                                  -->

<!-- These materials may not be altered; modifications to     -->
<!-- these DTDs should be performed as specified in the       -->
<!-- Guidelines in chapter "Modifying the TEI DTD."           -->

<!-- These materials subject to revision. Current versions    -->
<!-- are available from the Text Encoding Initiative.         -->
<!-- ... declarations from section 18.1.4                     -->
<!--     (Added and Deleted Spans)                            -->
<!--     go here ...                                          -->
<!-- ... declarations from section 18.1.6                     -->
<!--     (Cancelled Deletions)                                -->
<!--     go here ...                                          -->
<!-- ... declarations from section 18.1.7                     -->
<!--     (Supplied Text)                                      -->
<!--     go here ...                                          -->
<!-- ... declarations from section 18.2.1                     -->
<!--     (Hand Shifts)                                        -->
<!--     go here ...                                          -->
<!-- ... declarations from section 18.2.3                     -->
<!--     (Damage and Illegiblity)                             -->
<!--     go here ...                                          -->
<!-- ... declarations from section 18.2.5                     -->
<!--     (Spaces in the source)                               -->
<!--     go here ...                                          -->
<!-- ... declarations from section 18.3                       -->
<!--     (Headers and footers)                                -->
<!--     go here ...                                          -->
]]>
</eg>

<!-- <dtdRef dtdFrag=dPHorn>                                  --></p>

<p>This tag set modifies the element class
<ident type="class">edit</ident> by declaring two extra attributes
for members of the class:

<eg id=dphent>
<![ CDATA [
<!-- 18:  Attributes for Transcription of Primary
Sources    -->
<!-- Text Encoding Initiative: Guidelines for Electronic      -->
<!-- Text Encoding and Interchange. Document TEI P3, 1994.    -->

<!-- Copyright (c) 1994 ACH, ACL, ALLC. Permission to copy    -->
<!-- in any form is granted, provided this notice is          -->
<!-- included in all copies.                                  -->

<!-- These materials may not be altered; modifications to     -->
<!-- these DTDs should be performed as specified in the       -->
<!-- Guidelines in chapter "Modifying the TEI DTD."           -->

<!-- These materials subject to revision. Current versions    -->
<!-- are available from the Text Encoding Initiative.         -->
<!ENTITY % a.edit '
          cert               CDATA               #IMPLIED
          resp               IDREF               %INHERITED'    >
]]>
</eg>
</p>

<div2 id="PHch"><head>Altered, Corrected, and Erroneous Texts</head>

<p>In the detailed transcription of any source, it may prove necessary
to record various types of actual or potential alteration of the text:
expansion of abbreviations, correction of the text (by the author, by a
scribe, by a later hand, or by the encoder), addition, deletion, or
substitution of material, and the like.  The sections below describe how
such phenomena may be encoded using either elements defined in the core
tag set (defined in chapter <ptr target="CO">) or specialized elements
available only when the additional tag set described in this chapter is
available.</p>

<div3 id="PHco"><head>Use of Core Tags for Transcriptional Work</head>

<p>In transcribing individual sources (editions, manuscripts, witnesses
of any type), encoders may record their corrections, normalizations,
expansions of abbreviations, additions, and omissions
using the elements described in section <ptr target="COed">.  Those particularly relevant to this chapter include:

<list type=gloss>
<label><gi>abbr</gi></label>
<item>contains an abbreviation of any sort.</item>
<label><gi>expan</gi></label>
<item>contains the expansion of an abbreviation.</item>
<label><gi>sic</gi></label>
<item>contains text reproduced although apparently incorrect or

inaccurate.</item>
<label><gi>corr</gi></label>
<item>contains the correct form of a passage apparently erroneous 
in
the
copy text.</item>
<label><gi>add</gi></label>
<item>contains letters, words, or phrases inserted in the text by 
an
author, scribe, annotator or corrector.</item>
<label><gi>del</gi></label>
<item>contains a letter, word or passage deleted, marked as 
deleted,
or otherwise indicated as superfluous or spurious 
in the copy text by an
author, scribe, annotator or 
corrector.</item>
<label><gi>hi</gi></label>
<item>marks a word or phrase as graphically distinct from the

surrounding text, for reasons concerning which no claim is 
made. </item>
<label><gi>gap</gi></label>
<item>indicates a point where material has been omitted in a

transcription, whether for editorial reasons described in 
the TEI
header, as part of sampling practice, or because 
the material is
illegible or inaudible.</item>
</list>


<!-- 93-04-12 : PR : Removed refs to reg orig etc 27/3/93     -->
<!-- 93-04-12 :       added add, del, hi, omit tags to list   --></p>

<p>When the additional tag set for transcription of primary sources
is selected,
these elements all gain two specialized attributes for specifying who is
responsible for certain aspects of the interpretation and markup, and
the certainty attributed to the interpretation:

<list type=gloss>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to some specific 
aspect of the markup: the identification of the hand of an 
addition or deletion, the correctness of the expansion of 
an abbreviation, the correction of an error, or the 
regularization of a non-standard form; or the correctness 
of the transcription of unclear material.</item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for the 
salient information conveyed by a particular tag: the hand 
of an addition or deletion, the expansion of an 
abbreviation, the correction of an apparent error, the 
regularization of a non-standard form, the transcription of 
unclear material, or the decision not to transcribe some 
portion of the text.</item>
</list>

The specific aspect of the markup described by these attributes differs
on different elements; for further discussion, see the relevant sections
below, especially section <ptr target="PHhr">.</p>

<p>The following sections describe how the core elements just named may
be used in the transcription of primary source materials.  Examples of
more complex application in scholarly transcriptions of these core
elements are given, and of their extension by linkage with the
<gi>note</gi>, <gi>respons</gi>, and <gi>certainty</gi> elements.  Where the
core elements do not satisfy the needs of scholarly transcription,
additional elements are defined.</p></div3>

<div3 id="PHab"><head>Abbreviation and Expansion</head>

<p>The writing of manuscripts by hand lends itself to the use of
abbreviation to shorten scribal labour.  Commonly occurring letters,
groups of letters, words or even whole phrases, may be represented by
significant marks.  This phenomenon of manuscript abbreviation is so
widespread and so various that no taxonomy of it is here attempted.
Instead, methods are shown which allow abbreviations to be encoded using
the core elements mentioned above.</p>

<p>A manuscript abbreviation may be viewed in two ways.  One may
transcribe it as a particular sequence of letters or marks upon the
page: thus, a <q>p with a bar through the descender</q>, a
<q>superscript hook</q>, a <q>macron</q>.  One may also interpret the
abbreviation in terms of the letter or letters it is seen as standing
for: thus, <q>per</q>, <q>re</q>, <q>n</q>.  Both of these views are
supported by these Guidelines.  The entity reference system allows the
encoder to declare whatever entities are needed, using entity names
like <ident type="ent">p-underbar</ident>, <ident type="ent">sup-hook</ident>, or <ident type="ent">macron</ident>.
Furthermore, each entity reference may be linked to an image of the
abbreviation itself, so that the reader might see a rendering of the
text's appearance.  Alternatively, the encoder may transcribe the
letter or letters he or she believes the abbreviation stands for, as
the content of an <gi>expan</gi> element: thus
<tag>expan</tag>per<tag>/</tag>, <tag>expan</tag>re<tag>/</tag>,
<tag>expan</tag>n<tag>/</tag>.</p>

<p>These two methods of coding abbreviation may also be combined.  An
encoder may record, for any abbreviation, both
the sequence of letters or marks which constitutes it, and
its sense, that is, the letter or letters for
which it is believed to stand.  For example, the
abbreviations of <mentioned>euery persone</mentioned> in the following fragment
<note place="foot">From <q>The Manere of Good Lyuynge</q>, fol 126v of
Bodleian MS Laud Misc. 517, plate 8(ii) in <title>English Cursive Book
Hands 1250-1500</title> by M. B. Parkes (Clarendon Press:  Oxford,
1969).</note>
may be transcribed as follows, using the <gi>expan</gi> element, with
the <att>abbr</att> attribute to hold an  entity reference for the
brevigraph indicating the abbreviation in the manuscript:

<eg>
<![ CDATA [
eu<expan abbr="&er;" resp="MP">er</>y
<expan abbr="&p-underbar">per</>sone that
loketh after heuen hath a place in this ladder
]]>
</eg>

Alternatively, the abbreviations may be encoded using the <gi>abbr</gi>
element.

<eg>
<![ CDATA [
eu<abbr expan="er" resp=MP>&er;</>y
<abbr expan="per">&p-underbar</>sone that
loketh after heuen hath a place in this ladder
]]>
</eg></p>

<p>The choice between the <gi>expan</gi> and <gi>abbr</gi>
elements is left to the encoder.  As a rule, the <gi>abbr</gi> element
should be preferred where it is wished to signify that the content of
the element is an abbreviation, without necessarily indicating what the
abbreviation may stand for.  The <gi>expan</gi> element should be used
where it is wished to signify that the content of the element is an
expanded text, without necessarily indicating the abbreviation used in
the original.  The decision as to which (<gi>abbr</gi> or
<gi>expan</gi>) to use may vary from abbreviation to abbreviation; there
is no requirement that the one system be used throughout a
transcription.  However, processing may be simplified if one only of
these is used throughout a transcription.  The choice is likely to be a
matter of editorial policy, which might be applied consistently
throughout.  If the highest priority is to transcribe the text
literatim, while indicating the presence of abbreviations, the choice
<!-- "litteratim" is an adverb! -->
will be to use <gi>abbr</gi> throughout.  If the highest priority is to
present a reading transcription, while indicating that some letters or
words are expansions of abbreviations, the choice will be to use
<gi>expan</gi> throughout.</p>

<p>Further information may be attached to instances of these elements by
the <gi>note</gi> element, on which see section <ptr target="COno">, and
by use of the <att>resp</att> and <att>cert</att> attributes.  In this
instance from the English <title>Brut</title>,<note place="foot">On fol
65v of Bodleian MS. Rawlinson Poetry 32; in Parkes 12(ii).</note>
a note is attached to an editorial expansion of the tail on the final d
of <mentioned>good</mentioned> to <mentioned>goode</mentioned>:

<eg>
<![ CDATA [
For alle the while that I had
good<expan id=exp01 abbr="&tail;">e</>
I was welbeloued
]]>
</eg>

Then the note:

<eg>
<![ CDATA [
<note target=exp01>The stroke added to the final d could
signify the plural ending (-es, -is, -ys>) but the
singular <hi rend=it>good</> was used with the meaning
<q>property</q>, <q>wealth</q>, at this time (v. examples
quoted in OED, sb. Good, C. 7, b, c, d and 8 spec.)</note>
]]>
</eg>

The editor might declare a degree of certainty for this expansion, based
on the OED examples, and state the responsibility for the expansion:

<eg>
<![ CDATA [
For alle the while that I had
good<expan abbr="&tail;"
           cert=90
           resp="MP">e</>
I was welbeloued
]]>
</eg>

Observe that the <att>cert</att> and <att>resp</att> attributes may be
used with the <gi>expan</gi> element only to indicate respectively
confidence in the content of the element, (i.e., the expansion) and the
responsibility for suggesting this expansion.  In the case of the use of
these attributes with the <gi>abbr</gi>, the <att>cert</att> and
<att>resp</att> attributes are defined as indicating respectively
confidence in the expansion held in the <att>expan</att> attribute and
the responsibility for suggesting this expansion.  The above example
could be encoded using the <gi>abbr</gi> element as follows:

<eg>
<![ CDATA [
For alle the while that I had
good<abbr expan="e"
          cert=90
          resp="MP">&tail;</>
I was welbeloued
]]>
</eg>

If it is desired to express aspects of certainty and responsibility for
some other aspect of the use of these elements, then the mechanisms
discussed in chapter <ptr target="CE"> should be used.  See also <ptr
target="PHhr"> for discussion of the issues of certainty and
responsibility in the context of transcription.</p>

<p>If more than one expansion for the same abbreviation is to be
recorded, it is recommended that the markup for critical apparatus be
used; an example is given in section <ptr target="TCtr">.</p></div3>


<div3 id="PHcc"><head>Correction and Conjecture</head>

<p>The <gi>sic</gi> and <gi>corr</gi> elements, defined in the core tag
set, may be used to register authorial or scribal corrections within a
witness.  For example, in the manuscript of William James's <title>A
Pluralistic Universe</title>, edited by Fredson Bowers (Cambridge:
Harvard University Press, 1977) a sentence first written

<q rend="display">
One must have lived longer with this system,
to appreciate its advantages.
</q>

has been modified by James to begin <q>But one must ...</q>, without the
inital capital O having been reduced to lowercase.  This non-standard
orthography could be recorded and corrected thus:

<eg>
<![ CDATA [
But <sic corr="one">One</> must have lived ...
]]>
</eg>

The same information could be conveyed by the <gi>corr</gi> element:

<eg>
<![ CDATA [
But <corr sic="One">one</> must have lived ...
]]>
</eg>

In this example from Albertus Magnus,<note place="foot"><title>De
Nutrimento et Nutribili, Tractatus 1</title>, fol 217r col b of Merton
College Oxford MS O.2.1, (Parkes pl. 16).</note>
both the manuscript error <mentioned>angues</mentioned> and its correction
<mentioned>augens</mentioned> are registered by the <gi>sic</gi> element:

<eg>
<![ CDATA [
Nos autem iam ostendimus quod nutrimentum
et <sic corr=augens>angues</>.
]]>
</eg>

The same information could be conveyed by the <gi>corr</gi> element:

<eg>
<![ CDATA [
Nos autem iam ostendimus quod nutrimentum
et <corr sic="angues">augens</>.
]]>
</eg>

In this example, from George Moore's draft of additional materials for
<q>Memoirs of My Dead Life</q><note place="foot">In Pierpont Morgan MA
  3421, from <title>British Literary Manuscripts/Series II:  from 1800
  to 1914</title>, by V. Klinkenborg, H.Cahoon and C. Ryskamp (New York:
  Pierpont Morgan Library, 1981).</note>
the transcriber supplies the word <mentioned>we</mentioned> omitted by the author:

<eg>
<![ CDATA [
You see that I avoid the word create for we
create nothing <sic corr="we"></> develope.
]]>
</eg>

Or with reverse use of the <gi>corr</gi> element:

<eg>
<![ CDATA [
You see that I avoid the word create for we
create nothing <corr sic="">we</> develope.
]]>
</eg>

(N.B. when the additional tag set defined in this chapter is selected,
the <gi>supplied</gi> element should normally be used in preference
to <gi>sic</gi> or <gi>corr</gi> for such supplied text.)</p>

<p>As with the choice between <gi>expan</gi> and <gi>abbr</gi>, the
choice between the synonymous <gi>sic</gi> and <gi>corr</gi> elements is
left to the encoder.  As a rule, the <gi>sic</gi> element allows the
encoding to retain the original text as the content of the element,
while simultaneously signifying that the contents of the element require
correction, but without necessarily indicating what the correction may
be.  The <gi>corr</gi> element allows the text to be corrected, possibly
without recording the details of the faulty source, while still marking
explicitly the fact that the contents of the element have been
corrected.  The choice is likely to be a matter of editorial policy,
which might be applied consistently throughout or decided case by case.
If the highest priority is to present an uncorrected transcription while
noting perceived errors in the original, the choice will typically
be to use <gi>sic</gi> throughout.  If the highest priority is to
present a reading transcription, while indicating that perceived errors
in the original have been corrected, the choice will be to use
<gi>corr</gi> throughout.</p>

<p>Further information may be attached to instances of these elements by
the <gi>note</gi> element and <att>resp</att> and <att>cert</att>
attributes.  Here, two separate corrections in Dudo of S. Quentin<note
place="foot"><title>De moribus et actis primorum Normannie ducum</title>,
in fol 4v of British Library MS Harley 3742, Parkes pl 6(i).</note>
are assigned the same note.  First the corrections, held in the
attribute value of the <gi>sic</gi> elements:

<eg>
<![ CDATA [
quamuis <sic corr=iners id=sic01>mens</> que nutu dei
gesta sunt ... unde esset uiriliter
<sic corr=uegetata id=sic02>negata</>
]]>
</eg>

then the note, linked to the <att>id</att> of the <gi>sic</gi> element
for each of the two corrections:

<eg>
<![ CDATA [
<note target="sic01 sic02">Substitution of a more
familiar word which resembles graphically what the
scribe should be copying but which
does not make sense in the context.</>
]]>
</eg></p>

<p>The <att>cert</att> attribute may also be used with the <gi>corr</gi>
element to signify the conjectural status of a particular editorial
reading, with the <att>resp</att> attribute used to identify the scholar
responsible for the conjecture.  In this example, editorial confidence
in E. Talbot Donaldson's emendation of the Hengwrt manuscript reading
<mentioned>wight</mentioned> to <mentioned>wright</mentioned> in line 117 of Chaucer's
<title>The Wife of Bath's Prologue</title> may be marked as follows:

<eg>
<![ CDATA [
Telle me also, to what conclusioun
Were membres maad, of generacioun
And of so parfit wis a <corr sic="wight" resp=ETD cert=70
id="c117">wright</> ywroght?
]]>
</eg>

The editor might also conveniently add a note referring to Donaldson's
discussion of this passage:

<eg>
<![ CDATA [
<note target=c117>This emendation of the Hengwrt copy text,
based on a Latin source and on the reading of three late
and usually unauthoritative manuscripts, was proposed
by E. Talbot Donaldson in <title>Speculum</title> 40 (1965)
626-33.</note>
]]>
</eg></p>

<p>Alternative corrections within a transcription of a single witness
may be held within an <gi>app</gi> structure, in the same way that
alternative expansions are so grouped in the example given in section
<ptr target="TCtr">.  Here, Donaldson's conjectured emendation of the
Hengwrt manuscript may be recorded not only alongside the editorial
transcription but also alongside another conjecture:

<eg>
<![ CDATA [
And of so parfit wis a
<app>
   <rdg wit=Hg>wight</rdg>
   <rdg resp=ETD wit="Ln Ry2 Ld"><corr>wright</></rdg>
   <rdg resp=PR wit="Gg"><corr>wyf</></rdg>
</app>
]]>
</eg></p>

<p>Observe that no <att>resp</att> attribute is necessary for the base
transcription:  by default, responsibility is assigned to the scholar(s)
responsible for the transcription, as identified in the TEI header.  The
conjectures are held within <gi>corr</gi> elements, contained within the
<gi>rdg</gi> elements.  The <att>resp</att> attribute identifying
responsibility for each correction is attached to the outer
<gi>rdg</gi>, and inherited by the inner <gi>corr</gi> element.  Note
too that the support for these conjectures in other manuscripts can be
noted in the <att>wit</att> attribute in the <gi>rdg</gi> element.</p>

<p>The <att>cert</att> and <att>resp</att> attributes may be used with
the <gi>corr</gi> element only to indicate respectively confidence in
the content of the element, (i.e., the correction) and the
responsibility for suggesting this correction or conjecture.  In the
case of the use of these attributes with the <gi>sic</gi> element, the
<att>cert</att> and <att>resp</att> attributes are defined as indicating
respectively confidence in the conjecture held in the <att>corr</att>
attribute and the responsibility for suggesting this conjecture.  The
above example could be encoded using the <gi>sic</gi> element as
follows:

<eg>
<![ CDATA [
And of so parfit wis a
<sic corr="wright" cert=70 resp=ETD>wight</>
ywroght?
]]>
</eg>

If it is desired to express aspects of certainty and responsibility for
some other aspect of the use of these elements, then the mechanisms
discussed in chapter <ptr target="CE"> should be used.  See also <ptr
target="PHhr"> for discussion of the issues of certainty and
responsibility in the context of transcription.</p></div3>

<div3 id="PHad"><head>Additions and Deletions</head>

<p>Additions and deletions to a text may be described using the
following elements:

<list type=gloss>
<label><gi>add</gi></label>
<item>contains letters, words, or phrases inserted in the text by 
an
author, scribe, annotator or corrector.</item>
<label><gi>addSpan</gi></label>
<item>marks the beginning of a longer sequence of text added by 
an
author, scribe, annotator or corrector (see also

<gi>add</gi>).
Attributes include:
<list type=gloss>
<label><att>place</att></label>
<item>indicates where the addition is made.
Suggested values include:
<list type=gloss>
<label><term>inline</term></label>
<item>addition is made in a space left in the witness by an 
earlier scribe.</item>
<label><term>infralinear</term></label>
<item>addition is made below the line.</item>
<label><term>margintop</term></label>
<item>addition is made in top margin.</item>
<label><term>marginbot</term></label>
<item>addition is made in bottom margin.</item>
<label><term>supralinear</term></label>
<item>addition is made above the line.</item>
<label><term>overleaf</term></label>
<item>addition is made on the other side of the leaf.</item>
<label><term>marginright</term></label>
<item>addition is made in right margin.</item>
<label><term>marginleft</term></label>
<item>addition is made in left margin.</item>
</list></item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
identifying the hand of the addition.</item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the 
identification of the hand of the addition.</item>
<label><att>hand</att></label>
<item>signifies the hand of the agent which made the addition.</item>
<label><att>to</att></label>
<item>identifies the endpoint of the added passage, by giving the 
ID of an <gi>anchor</gi> or other empty element placed 
there.</item>
</list>
</item>
<label><gi>del</gi></label>
<item>contains a letter, word or passage deleted, marked as 
deleted,
or otherwise indicated as superfluous or spurious 
in the copy text by an
author, scribe, annotator or 
corrector.</item>
<label><gi>delSpan</gi></label>
<item>marks the beginning of a longer sequence of text deleted,

marked as deleted, or otherwise signaled as superfluous or 
spurious by an
author, scribe, annotator, or corrector.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the deletion, using any convenient typology.
Sample values include:
<list type=gloss>
<label><term>erasure</term></label>
<item>deletion indicated by erasure of the text.</item>
<label><term>bracketed</term></label>
<item>deletion indicated by brackets in the text or 
margin.</item>
<label><term>overstrike</term></label>
<item>deletion indicated by line crossing out the text.</item>
<label><term>subpunction</term></label>
<item>deletion indicated by dots beneath the letters 
deleted.</item>
</list></item>
<label><att>status</att></label>
<item>indicates whether the deletion is faulty, e.g. by including 
too much or too little text.
Sample values include:
<list type=gloss>
<label><term>unremarkable</term></label>
<item>the deletion is not faulty.</item>
<label><term>excess start</term></label>
<item>some text at the beginning of the deletion is marked as 
deleted even though it clearly should not be 
deleted.</item>
<label><term>short start</term></label>
<item>some text at the beginning of the deletion is not marked as 
deleted even though it clearly should be.</item>
<label><term>excess end</term></label>
<item>some text at the end of the deletion is marked as deleted 
even though it clearly should not be deleted.</item>
<label><term>short end</term></label>
<item>some text at the end of the deletion is not marked as 
deleted even though it clearly should be.</item>
</list></item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
identifying the hand of the deletion.</item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the 
identification of the hand of the deletion.</item>
<label><att>hand</att></label>
<item>signifies the hand of the agent which made the deletion.</item>
<label><att>to</att></label>
<item>identifies the endpoint of the deleted passage, by giving 
the ID of an <gi>anchor</gi> or other element placed there.</item>
</list>
</item>
</list>


Of these, <gi>add</gi> and <gi>del</gi> are included in the core tag
set, while <gi>addSpan</gi> and <gi>delSpan</gi> are available only when
using the additional tag set defined in this chapter.</p>

<p>As described in section <ptr target="COed">, the <gi>add</gi> element
indicating material added may be used to signify manuscript additions or
insertions, be they authorial or scribal.  In the autograph manuscript
of Max Beerbohm's <title>The Golden Drugget</title>,<note place="foot">In
    Pierpont Morgan MA 3391 (Klinkenborg 123).</note>
the author's addition of "do ever" may be recorded as follows, with the
<att>hand</att> attribute indicating that the addition was Beerbohm's:

<eg>
<![ CDATA [
Some things are best at first sight.  Others -- and
here is one of them -- <add hand='MB'>do ever</add>
improve by recognition
]]>
</eg>

Similarly, the <gi>del</gi> element indicating material deleted may be
used to signify manuscript deletions.  In the autograph manuscript of D.
H. Lawrence's <title>Eloi, Eloi, lama sabachthani</title> (Pierpont
Morgan MA 1892, Klinkenborg 129), the author's deletion of
<mentioned>my</mentioned> may be recorded as follows.  As well as the
<att>hand</att> attribute indicating that the deletion was Lawrence's,
the <att>rend</att> attribute indicates that the deletion was by
strike-through:

<eg>
<![ CDATA [
For I hate this
<del hand='DHL' rend='strike-through'>my</del> body,
which is so dear to me
]]>
</eg>

If deletions are classified systematically, the <att>type</att>
attribute should normally
be used to indicate the classification; when they
are classified by the manner in which they were effected, or by their
appearance, however,
this will lead to a certain arbitrariness in deciding
whether to use the <att>type</att> or the <att>rend</att> attribute
to hold the information.  In general, it is recommended that the
<att>rend</att> attribute be used for description of the appearance
or method of deletion, and that the <att>type</att> attribute be
reserved for higher level or more abstract classifications.</p>

<p>Further characteristics of the addition and deletion, e.g. the date,
or ink, may be needed for detailed transcription of manuscripts.  Such
characteristics may conveniently be recorded as attributes of the
<gi>add</gi> or <gi>del</gi> element.  The specific attributes required
may be added to the formal declaration of these elements by using the
techniques described in chapter <ptr target="MD">.</p>

<p>The <gi>add</gi> and <gi>del</gi> elements defined in the core tag
set available in all TEI documents will suffice for describing typically
brief additions and deletions in the text being transcribed.  On
occasion, it will be necessary to record an addition or deletion which
crosses a structural boundary in the text being encoded, for example the
addition or deletion from a manuscript of a section containing several
distinct structural subdivisions, such as poems or prose items.  These
are most conveniently encoded using the <gi>addSpan</gi> and
<gi>delSpan</gi> elements, available in the additional tag set defined
in this chapter.  In this example of the use of <gi>addSpan</gi>, the
insertion of a gathering containing four neo-Eddic poems into
Landsb&oacute;kasafn (Reykjav&iacute;k, 1562 quarto) by Helgi
&Oacute;lafsson is recorded as follows.
<!-- added clarificatory sentence -->
A <gi>hand</gi> element is
first declared, within the header of the document, to associate
the identifier <ident>HEOL</ident> with Helgi. In the body of the
text, an <gi>addSpan</gi> element
is placed to mark the beginning of the span of added text.  The
<att>hand</att> attribute ascribes the responsibility for the addition
to the manuscript to Helgi, and the <att>to</att> attribute declares the
identifier for the anchor which marks the end of the added text:

<eg>
<![ CDATA [

<hand id=HEOL n="Helgi &Oacute;lafsson">

<!-- text of the original material ... -->

<addSpan type="added gathering"
         hand="HEOL"
         to=p025>
<!-- text of the four neo-Eddic poems added... -->
<anchor id=p025>

<!-- text of the original material continues... -->
]]>
</eg></p>

<p>In this example of the use of the <gi>delSpan</gi> element, a full
two lines of Thomas Moore's autograph of the second version of
<title>Lalla Rookh</title><note place="foot">In Pierpont Morgan MA 310,
(Klinkenborg 23).</note> are marked for omission by vertical
strike-through.  The two lines cross the structural line division marked
<tag>l n=2</tag>, so it would not be possible to use a single
<gi>del</gi> element, since it would have to span the <gi>l</gi> marker.
The lines also themselves include a further deletion and addition.  The
<gi>delSpan</gi> element indicates the begining of the span marked for
deletion, with the <att>to</att> attribute giving the identifier
(delend01) for an <gi>anchor</gi> element which marks the end of the span of text so
marked:

<eg>
<![ CDATA [
<l n=1>
<delSpan type='vertical strike' to=delend01>
Tis moonlight <del>upon</><add>over</> Oman's sky
<l n=2> Her isles of pearl look lovelily
<anchor id=delend01>
</l>
]]>
</eg></p>

<p>The text deleted must be at least partially legible, in order for the
encoder to be able to transcribe it.  If it is not legible at all, the
<gi>gap</gi> element should be used to signal that the text was not
(because it could not be) transcribed; the <att>reason</att> attribute
can give the cause of the omission from the transcription as
<q>deletion, illegible</q>.  The <gi>gap</gi> element may optionally be
enclosed by a <gi>del</gi> element, if it is thought useful to record
the deletion explicitly using this element.  If the deleted text is
partially legible, the <gi>unclear</gi> element described in section
<ptr target="PHda"> should be used to signal the areas of text which
cannot be read with confidence; it too may be enclosed within a
<gi>del</gi> element.  See further section <ptr target="PHom"> and
section <ptr target="PHda">.</p>

<p>The elements <gi>add</gi>, <gi>del</gi>, and <gi>gap</gi> are defined
in the core tag set and are available in all TEI documents.  The
elements <gi>addSpan</gi> and <gi>delSpan</gi> have the following formal
declarations:

<eg id=dtcad>
<![ CDATA [
<!-- 18.1.4:  Added and Deleted Spans                         -->
<!ELEMENT addSpan       - O  EMPTY                              >
<!ATTLIST addSpan            %a.global;
          cert               CDATA               #IMPLIED
          to                 IDREF               #REQUIRED
          place              CDATA               #IMPLIED
          resp               IDREF               %INHERITED
          hand               IDREF               %INHERITED
          type               CDATA               #IMPLIED       >
<!ELEMENT delSpan       - O  EMPTY                              >
<!ATTLIST delSpan            %a.global;
          cert               CDATA               #IMPLIED
          to                 IDREF               #REQUIRED
          resp               IDREF               %INHERITED
          hand               IDREF               %INHERITED
          status             CDATA               'unremarkable'
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 18                         -->
]]>
</eg>
</p></div3>


<div3 id="PHsu"><head>Substitutions</head>

<p>Substitution of one word or phrase for another is
perhaps the most common of all phenomena requiring special treatment
in transcription of primary textual sources.
It may be simply one word overwriting another, or
deletion of one word and its replacement by another written above it by
the same hand at the one time; the deletion and replacement may be done
by different hands at different times; there may be a long chain of
substitutions on the one stretch of text, with uncertainty as to the
order of substitution and as to the final reading.</p>

<p>Three different methods may be used to express substitution of one
stretch of text by another:

<list type="bullets">

<item>the <gi>sic</gi> and <gi>corr</gi> elements, either individually
to encode a single substitution or nested to encode a sequence of
substitutions;</item>

<item>the <gi>del</gi> and <gi>add</gi> elements, used in sequence to
show that text was first deleted then other text inserted;</item>

<item>the <gi>del</gi> and <gi>add</gi> elements, used within an
<gi>app</gi> structure (as defined in chapter <ptr target="TC">) to
indicate that the deleted and added text within the individual reading
elements making up the <gi>app</gi> structure are variants of one
another.</item>

</list>

The use of all three of these is illustrated in the following encodings
of the second line of <title>Eloi, Eloi, lama sabachthani</title> from
the Lawrence manuscript mentioned above.  Lawrence first wrote <q>How it
galls me, what a galling shadow</q>.  Subsequently, he deleted
<mentioned>galls</mentioned> and wrote <mentioned>dogs</mentioned> above the deletion.</p>

<p>This substitution could be registered using the first method outlined
above, as a correction using the <gi>sic</gi> or <gi>corr</gi> elements.
Note the use of the <att>resp</att> attribute on the <gi>corr</gi>
element to assign the correction to Lawrence.  (For further information
on the <att>hand</att> and <att>resp</att> attributes, see section
<ptr target="PHhr">.)

<eg>
<![ CDATA [
How it <corr resp='DHL' sic='galls'>dogs</corr>
me, what a galling shadow
]]>
</eg>

This substitution could be registered using the second method outlined
above, using the <gi>del</gi> and <gi>add</gi> elements in sequence to
reflect the fact that text was first deleted then other text inserted:

<eg>
<![ CDATA [
How it <del type=overstrike hand='DHL'>galls</del>
<add place=supralinear hand='DHL'>dogs</add>
me, what a galling shadow
]]>
</eg>

This substitution could be registered using the third method outlined
above, using the <gi>del</gi> and <gi>add</gi> elements within an
<gi>app</gi> structure to indicate that the deleted and added texts are
variants of one another.  Note that within the <gi>app</gi> structure
the <att>hand</att> attribute is moved from the inner <gi>del</gi> and
<gi>add</gi> elements to the outer <gi>rdg</gi> element:

<eg>
<![ CDATA [
How it
  <app>
     <rdg hand='DHL'><del type=overstrike> galls</del></rdg>
     <rdg hand='DHL'><add place=supralinear> dogs</add> </rdg>
  </app>
me, what a galling shadow
]]>
</eg>

Each of these three methods has its particular advantages and
disadvantages.  The first method (use of <gi>sic</gi> or <gi>corr</gi>)
is compact and indicates clearly that one text is a substitute for
another.  However, it provides no clear means of stating how the
substitution is effected:  whether by deletion through strike-out, or
underdotting, or erasure, followed by interlinear insertion, or marginal
insertion.  (The global <att>rend</att> attribute might conceivably be
used, but this may not be thought an obvious place to put such
information.)  In a transcription where this information is not felt to
be important, however, this method will suffice to indicate simple cases
of direct substitution of one text for another.</p>

<p>The second method (use of a <gi>del</gi> and <gi>add</gi> sequence)
is also compact and provides means for exact declaration of how the
deletion and insertion are effected.  However, it does not indicate
explicitly that one text is a substitute for another.  It is left for
the reader or the application to infer from the <gi>del</gi> and
<gi>add</gi> sequence that the insertion is to be taken as a
substitution for the deletion.  In many transcriptions, the inference
may be safely drawn for simple cases of direct substitution of one text
for another.  In other transcriptions, for example of complex authorial
manuscripts, this inference may prove fragile; those who desire
to express clearly that an adjacent addition and deletion are not
independent but constitute a single act of substitution will therefore
wish to avoid this method.  Others, of course, may prefer it for
precisely the same reason, namely that it avoids prejudging the issue of
whether adjacent deletions and additions are independent or joined.</p>

<p>The third method (use of the <gi>del</gi> and <gi>add</gi> elements
within an <gi>app</gi> structure) provides means both for exact
declaration of how the deletion and insertion are effected and for
explicit indication that one text is a substitute for another.  Further,
the exact sequence of readings may also be declared by use of the
<att>varSeq</att> attribute on the <gi>rdg</gi> element, as follows:

<eg>
<![ CDATA [
How it
  <app>
     <rdg hand='DHL' varSeq=1><del>galls</del></rdg>
     <rdg hand='DHL' varSeq=2><add>dogs</add> </rdg>
  </app>
me, what a galling shadow
]]>
</eg>

Here, the combination of the <att>hand</att> and <att>varSeq</att>
attributes suffices to inform the reader of the authorial substitution
of <mentioned>dogs</mentioned> for <mentioned>galls</mentioned>.</p>

<p>Similarly, the <att>varSeq</att> attribute might be used in a
transcription of the manuscripts of James Joyce's <title>Ulysses</title>
to indicate the sequence of Joyce's corrections which is implicit in
Hans Walther Gabler's reconstruction of the <q>overlay</q> levels of
Joyce's transcriptions.  This third method is the most powerful and
unambiguous of the three methods and enables the widest range of
processing possibilities.  However, it does suffer an apparent
disadvantage.  It introduces more markup into the text, which
can prove a burden to those working without SGML-aware editors.  The
volume of markup may be reduced by markup minimization, as in the
following recoding of the Lawrence example, but some overhead will
remain nevertheless:

<eg>
<![ CDATA [
How it
  <app>
     <rdg><del>galls</></>
     <rdg><add>dogs</></>
  </app>
me, what a galling shadow
]]>
</eg>

A second disadvantage is that applications of considerable
sophistication may be needed to make full use of all the information
that may be held within an <gi>app</gi> structure.  In the absence of
such applications, scholars may feel that the present cost of the more
informative coding using <gi>app</gi> structures outweighs the future
benefits.  In making such decisions, it should however be kept in mind
that the capabilities of software at the time a project begins will often
be wholly irrelevant when the project is completed some years later.</p>

<p>The Lawrence example above shows the three methods used for encoding
a single substitution of one reading for another.  The same three
methods may also be used to encode longer sequences of substitutions.
In the example from William James, first written out by James as <q>One
must have lived longer with this system, to appreciate its
advantages</q> the word <mentioned>this</mentioned> is first replaced by
<mentioned>such a</mentioned> and this is then replaced by <mentioned>a</mentioned>.
<note place="foot">The manuscript contains several other substitutions,
ignored here for the sake of clarity.</note> This may be encoded using
the first method, with the sequence of substitutions shown by the
nesting of <gi>corr</gi> elements:

<eg>
<![ CDATA [
One must have lived longer with
<corr sic='this'><corr sic='such a'>a</corr></corr>
system, to appreciate its advantages.
]]>
</eg></p>

<p>It may be encoded using the second method, with the two changes being
treated as a sequence of additions and deletions:

<eg>
<![ CDATA [
One must have lived longer with
<del>this</del>
<del><add>such a</add></del>
<add>a</add> system,
to appreciate its advantages.
]]>
</eg>

Note the nesting of an <gi>add</gi> element within a <gi>del</gi> to
record text first added, then deleted in the source.</p>

<p>It may be encoded using the third method, with each reading in the
series contained in a <gi>rdg</gi> element within an <gi>app</gi>
structure:

<eg>
<![ CDATA [
One must have lived longer with
  <app>
     <rdg varSeq=1><del>this</del>
     <rdg varSeq=2><del><add>such a</add></del>
     <rdg varSeq=3><add>a</add>
  </app>
system, to appreciate its advantages.
]]>
</eg>

The three encodings of this slightly more complex example illustrate the
general truth that the more information involving substitutions there is
to be encoded, the clearer become the advantages of the use of the
<gi>app</gi> method over the other two methods.  As a rule, it is
recommended that the <gi>app</gi> method be used for encoding
substitutions of any complexity.  It is also desirable that the one
method be used throughout any one transcription.  Accordingly, the
<gi>app</gi> method is recommended for text critical transcription of
primary textual materials requiring encoding of instances of other than
straightforward substitution.</p></div3>

<div3 id="PHcd"><head>Cancellation of Deletions and Other Markings</head>

<p>An author or scribe may mark a word or phrase in some way, and then
on reflection decide to cancel the marking.  For example, text may be
marked for deletion and the deletion then cancelled, thus restoring the
deleted text.  Such cancellation may be indicated by the
<gi>restore</gi> element:

<list type=gloss>
<label><gi>restore</gi></label>
<item>indicates restoration of text to an earlier state by

cancellation of an editorial or authorial marking or 
instruction.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the action cancelled by the restoration.</item>
<label><att>desc</att></label>
<item>gives a prose description of the means of restoration.</item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
identifying the hand of the restoration.</item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the 
identification of the hand of the restoration.</item>
<label><att>hand</att></label>
<item>signifies the hand of the agent which made the restoration.</item>
</list>
</item>
</list>
</p>

<p>Presume that Lawrence decided to restore <mentioned>my</mentioned> to the
phrase of <title>Eloi, Eloi, lama sabachthani</title> first written
<q>For I hate this my body</q>, with the <mentioned>my</mentioned> first deleted
then restored by writing <q>stet</q> in the margin.  This may be
encoded:

<eg>
<![ CDATA [
For I hate this
<restore hand='DHL' desc='marginal "stet"'><del>my</del></restore>
body
]]>
</eg></p>

<p>The <gi>restore</gi> element is defined as follows:

<eg id=dphcd>
<![ CDATA [
<!-- 18.1.6:  Cancelled Deletions                             -->
<!ELEMENT restore       - O  (%phrase.seq;)                     >
<!ATTLIST restore            %a.global;
          wit                CDATA               #IMPLIED
          cause              CDATA               #IMPLIED
          varSeq             NUMBER              #IMPLIED
          cert               CDATA               #IMPLIED
          desc               CDATA               #IMPLIED
          resp               IDREF               %INHERITED
          hand               IDREF               %INHERITED
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 18                         -->
]]>
</eg>


<!-- Q. What do we do when someone wants to transcribe the    -->
<!-- word 'stet' as being a word written by Lawrence?  A.     -->
<!-- (msm).  Tell them to tag the deletion and restoration    -->
<!-- as shown (which does not, ex hypothesi, involve any      -->
<!-- mechanically recoverable indication that Lawrence wrote  -->
<!-- 'stet'.  Then add <note place=margin type='authorial     -->
<!-- instruction' resp=dhl>stet</note>.                       --></p></div3>

<div3 id="PHom"><head>Text Omitted from or Supplied in the Transcription</head>

<p>Where text is not transcribed, whether because of damage to the
original, or because it is illegible, or because of editorial policy,
the <gi>gap</gi> core element should be used to register the omission;
where text not present in the source is supplied (whether
conjecturally or from other witnesses) to fill an apparent gap in the
text, it should be marked using the <gi>supplied</gi> element provided
by the tag set defined in this chapter.

<list type=gloss>
<label><gi>gap</gi></label>
<item>indicates a point where material has been omitted in a

transcription, whether for editorial reasons described in 
the TEI
header, as part of sampling practice, or because 
the material is
illegible or inaudible.
Attributes include:
<list type=gloss>
<label><att>desc</att></label>
<item>gives a description of the omitted text.</item>
<label><att>reason</att></label>
<item>gives the reason for omission. Sample values include 
<q>sampling</q>, <q>illegible</q>, <q>inaudible</q>, 
<q>irrelevant</q>, <q>canceled</q>, <q>canceled and 
illegible</q>.</item>
<label><att>extent</att></label>
<item>indicates approximately how much text has been omitted from 
the transcription, in letters, minims, inches, or any 
appropriate unit, either because of editorial policy or 
because a deletion, damage or other cause has rendered 
transcription impossible.</item>
<label><att>resp</att></label>
<item>indicates the editor, transcriber or encoder responsible 
for the decision not to provide any transcription of the 
text and hence the application of the <gi>gap</gi> tag.</item>
<label><att>hand</att></label>
<item>In the case of text omitted from the transcription because 
of deliberate deletion by an identifiable hand, signifies 
the hand which made the deletion.</item>
<label><att>agent</att></label>
<item>In the case of text omitted from the transcription because 
of damage or other phenomenon resulting from an 
identifiable cause, signifies the causative agent.</item>
</list>
</item>
<label><gi>supplied</gi></label>
<item>signifies text supplied by the transcriber or editor in 
place
of text which cannot be read, either because of 
physical damage or
loss in the original or because it is 
illegible for any
reason.
Attributes include:
<list type=gloss>
<label><att>reason</att></label>
<item>indicates why the text has had to be supplied.</item>
<label><att>resp</att></label>
<item>indicates the individual responsible for supplying the 
letter, word or passage contained within the 
<gi>supplied</gi> element.</item>
<label><att>hand</att></label>
<item>Where the presumed loss of text leading to the supplying of 
text arises from action (partial deletion, etc.) assignable 
to an identifiable hand, signifies the hand responsible for 
the action.</item>
<label><att>agent</att></label>
<item>where the presumed loss of text leading to the supplying of 
text arises from an identifiable cause, signifies the 
causative agent.</item>
<label><att>source</att></label>
<item>states the source of the supplied text.</item>
</list>
</item>
</list>
</p>

<p>By its nature, the <gi>gap</gi> element must have no content.  It
should be used wherever an authorial or scribal erasure is so
successful, or the text is so illegible, that nothing can be read.  In
the Beerbohm manuscript of <title>The Golden Drugget</title> cited
above, for example, the author has erased several passages by inking
them over completely:

<eg>
<![ CDATA [
Others <gap reason='cancelled' hand='MB' extent='10cm'>--and
here is one of them...
]]>
</eg></p>

<p>In an autograph letter of Sydney Smith in the Pierpont Morgan library
(Klinkenborg 11), three words in the signature are quite illegible:

<eg>
<![ CDATA [
I am dr Sr yr <gap reason='illegible'
                   hand='SS'
                   extent='3 words'>Sydney Smith
]]>
</eg>

It is possible, but not always necessary, to provide measurements
precise to the millimeter or even to the printer's point.  The degree of
precision attempted will vary with the purpose of the encoding and the
nature of the material.</p>

<p>In cases where there is damage, or a degree of illegibility, but the
text is nevertheless legible and is transcribed, the <gi>gap</gi>
element should not be used.  Instead, the passage should be marked using
one or more of the elements <gi>damage</gi> and <gi>unclear</gi>, which
are described in section <ptr target="PHda">.</p>

<p>If the source text is completely illegible or missing, and new text
is supplied to fill the gap, it should be marked as <gi>supplied</gi>.
If another (imaginary) copy of the letter above preserved the signature
as reading <q>I am dear Sir your very humble Servt Sydney Smith</q>, the
text illegible in the autograph might be supplied in the transcription:

<eg>
<![ CDATA [
I am dr Sr yr
<supplied reason='illegible'
          resp='RW'
          source='amanuensis copy'>very humble Servt</>
Sydney Smith
]]>
</eg>

Both <gi>gap</gi> and <gi>supplied</gi> may be used in combination with
<gi>unclear</gi>, <gi>damage</gi>, and other elements; for
discussion, see section <ptr target="PHcomb">.</p>

<p>As noted, <gi>gap</gi> is defined in the core tag set.  The
<gi>supplied</gi> element is declared thus:

<eg id=dphom>
<![ CDATA [
<!-- 18.1.7:  Supplied Text                                   -->
<!ELEMENT supplied      - O  (%paraContent;)                    >
<!ATTLIST supplied           %a.global;
          source             CDATA               #IMPLIED
          resp               CDATA               %INHERITED
          hand               IDREF               %INHERITED
          reason             CDATA               #IMPLIED
          agent              CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 18                         -->
]]>
</eg>
</p></div3></div2>

<div2 id="PHph"><head>Non-Linguistic Phenomena in the Source</head>

<p>This section describes methods for recording a number of
non-linguistic characteristics of the source text which are often of
particular interest in the transcription of primary sources:  points at
which one scribe takes over from another, or at which ink, pen, or other
characteristics of the writing change; points at which the source is
damaged or imperfectly legible; and unusual spaces or lines in the
source.  A discussion of the usage of the <att>hand</att>,
<att>resp</att>, and <att>cert</att> attributes is also included.
Methods for recording page breaks, column breaks, and line breaks in the
source are described in section <ptr target="COxr">.</p>

<div3 id="PHdh"><head>Document Hands</head>

<p>For many text-critical purposes it is important to signal the person
responsible (the <q>hand</q>) for the writing of a whole document, a
stretch of text within a document, or a particular feature within the
document.  The hand may be of a known and named scribe or author, as
<q>DHL</q>, or may be described by an anonymous formula, as <q>hand
one</q>.  Where the hand is associated with a particular feature tagged
within a document, this may be indicated by the value of the
<att>hand</att> attribute on that feature.  The examples given above of
the use of the <att>hand</att> attribute with coding of additions and
deletions illustrate this.</p>

<p>In other cases, it may be necessary to identify a document hand
without there being any association of that hand with any specific
tagged document feature.  The <gi>handList</gi> and <gi>hand</gi>
elements are used in the TEI header (in the <gi>profileDesc</gi>
element) to define each unique hand or scribe distinguished by the
encoder in the document.  One such element must appear within the header
for each hand distinguished in the text.  Each location where a change
of hands occurs may then be marked in the text by the empty
<gi>handShift</gi> element.

<list type=gloss>
<label><gi>hand</gi></label>
<item>used in the header to define each distinct scribe or

handwriting style.
Attributes include:
<list type=gloss>
<label><att>id</att></label>
<item>identifier, either numeric or alphanumeric, used thereafter 
in the document to refer to this scribe or handwriting 
style.</item>
<label><att>scribe</att></label>
<item>gives the name of, or other identifier for, the scribe.</item>
<label><att>style</att></label>
<item>indicates recognized writing styles.</item>
<label><att>lang</att></label>
<item>indicates dominant language of hand.</item>
<label><att>ink</att></label>
<item>describes tint or type of ink, e.g. 'brown'. May also be 
used to indicate the writing medium, e.g. 'pencil',</item>
<label><att>character</att></label>
<item>describes other characteristics of the hand, particularly 
those related to the quality of the writing.</item>
<label><att>first</att></label>
<item>indicates the first scribe in the document.</item>
<label><att>resp</att></label>
<item>indicates the editor or transcriber responsible for 
identifying the hand.</item>
</list>
</item>
<label><gi>handList</gi></label>
<item>contains a series of <gi>hand</gi> elements listing the

different hands of the source.</item>
<label><gi>handShift</gi></label>
<item>marks the beginning of a sequence of text written in a new

hand, or of a change in the scribe, writing style, ink or 
character
of the document hand.
Attributes include:
<list type=gloss>
<label><att>new</att></label>
<item>identifies the new hand.</item>
<label><att>old</att></label>
<item>identifies the old hand.</item>
<label><att>style</att></label>
<item>indicates recognised writing styles</item>
<label><att>ink</att></label>
<item>describes colour of ink, e.g. 'brown'. May also be used to 
indicate the writing medium, e.g. 'pencil'</item>
<label><att>character</att></label>
<item>used to describe other characteristics of the hand, 
particularly those related to the quality of the writing.</item>
<label><att>resp</att></label>
<item>signifies the editor or transcriber responsible for 
identifying the change of hand.</item>
</list>
</item>
</list>
</p>

<p>The attributes <att>old</att> and <att>new</att> on the
<gi>handShift</gi> element refer to the order of the text in the
transcription:  <q>old</q> is the material before the
<gi>handShift</gi>, <q>new</q> the material following.  This will
ordinarily, but not necessarily, be the order in which the material was
originally written.  Neither attribute is required but both are
recommended where there is a new hand, as opposed to a new writing style
in the one hand.  The <att>character</att> attribute will be most often
used to encode descriptive shifts which the transcriber perceives within
a manuscript and which may or may not be associated with or denote
changes in scribe or content.  The particular values encoded will depend
upon the needs of the transcriber.  Where many values are to be encoded,
feature structures provide an alternative means of encoding these.</p>

<p>A single hand may employ different writing styles and inks within a
document, or may change character.  For example, the writing style might
shift from <q>anglicana</q> to <q>secretary</q>, or the ink from blue to
brown, or the character of the hand may change.  Any such changes should
be indicated by assigning a new value to the appropriate attribute
within the <gi>handShift</gi> element.  The one hand may employ
different renditions within the one writing style, for example medieval
scribes indicating a structural division by emboldening all the words
within a line.  These should be indicated by use of the <att>rend</att>
attribute on an element, in the same manner as underlining, emboldening,
font shifts, etc., in transcription of a printed text, rather than by
introducing a new <gi>handShift</gi> element.</p>

<p>In this example<note place="foot">From the Wiltshire Record Office,
Dean of Sarum Churchwardens' presentments, 1731, Hurst; the
transcription was provided by Donald A. Spaeth.</note> first the
document hands are declared in the header:

<eg>
<![ CDATA [
<!--
<teiHeader>
 ...
<profileDesc>
    ... -->
   <handList>
      <hand id=h1 style='copperplate'
                  ink='brown'
                  character='regular'
                  first='yes'
                  resp='das'>
      <hand id=h2 style='print'
                  ink='brown'
                  character='unschooled'
                  resp='das'>
   </handList>
   <!--
</profileDesc>
</teiHeader> ... -->
]]>
</eg>

<!-- teiheader def will need to be modified PR   --></p>
<p>Then the change of hand is indicated in the text:

<eg>
<![ CDATA [
<!-- ... -->
and that good Order Decency and regular worship
may be once more introduced and Established in this
Parish according to the Rules and Ceremonies of the
Church of England and as under a good Consciencious
and sober Curate there would and ought to be
<handShift new='h2' old='h1' resp='das'>
and for that purpose the parishioners pray
]]>
</eg></p>

<p>In this example<note place="foot">From folio 52 recto of the Holkham
manuscript of Chaucer's <title>Canterbury Tales</title>.</note> there is
a change of ink within the one hand.  This is indicated by a new value
for the <att>ink</att> attribute on the <gi>handShift</gi> element:

<eg>
<![ CDATA [
<l>When wolde the cat dwelle in his ynne</l>
<handShift ink=black>
<l>And if the cattes skynne be slyk and gaye</l>
]]>
</eg></p>

<p>These elements are declared as follows:

<eg id=dphhd>
<![ CDATA [
<!-- 18.2.1:  Hand Shifts                                     -->
<!ELEMENT hand          - O  EMPTY                              >
<!ATTLIST hand               %a.analysis;
                             %a.linking;
                             %a.terminology;
          rend               CDATA               #IMPLIED
          n                  CDATA               #IMPLIED
          first              CDATA               #IMPLIED
          scribe             CDATA               #IMPLIED
          id                 ID                  #REQUIRED
          style              CDATA               #IMPLIED
          lang               CDATA               #IMPLIED
          hand               CDATA               #IMPLIED
          character          CDATA               #IMPLIED
          resp               CDATA               %INHERITED
          ink                CDATA               #IMPLIED       >
<!ELEMENT handShift     - O  EMPTY                              >
<!ATTLIST handShift          %a.global;
          style              CDATA               #IMPLIED
          new                IDREF               #IMPLIED
          old                IDREF               #IMPLIED
          character          CDATA               #IMPLIED
          resp               IDREF               %INHERITED
          ink                CDATA               #IMPLIED       >
<!ELEMENT handList      - O  (hand*)                            >
<!ATTLIST handList           %a.global;                         >
<!-- This fragment is used in sec. 18                         -->
]]>
</eg>
</p></div3>

<div3 id="PHhr"><head>Hand, Responsibility, and Certainty Attributes</head>

<p>The <att>hand</att> and <att>resp</att> attributes have similar, but
not identical, meanings.  Observe their distinctive uses in the
following encoding of the William James passage mentioned above in
section <ptr target="PHcc">.  In this example, the <mentioned>But</mentioned>
inserted by James is tagged as an <gi>add</gi>, and the consequent
editorial correction of <mentioned>One</mentioned> to <mentioned>one</mentioned> treated
separately:

<eg>
<![ CDATA [
<add place='supralinear' resp=FB hand=WJ>But</add>
<corr sic='One' resp=FB>one</> must have lived ...
]]>
</eg>

As in this example, <att>hand</att> should be reserved for indicating
the hand of any form of marking---here, addition but also deletion,
correction, annotation, underlining, etc.---within the primary text
being transcribed.  The scribal or authorial responsibility for this
marking may be inferred from the value of the <att>hand</att> attribute.
The value of the <att>hand</att> attribute should be one of the hand
identifiers declared in the document header (see section <ptr
target="PHdh">).</p>

<p>As in this example, the <att>resp</att> on a particular element
should be used only to indicate the particular aspect of responsibility
defined in these <title>Guidelines</title> as appropriate to the
<att>resp</att> attribute for that element.  In the case of the
<gi>add</gi> element, the <att>resp</att> attribute is defined as
signifying the responsibility for identifying the hand of the
addition:  here, Bowers' identification of the hand as that of William
James.  In the case of the <gi>corr</gi> element, the <att>resp</att>
attribute is defined as signifying the responsibility for supplying the
intellectual content of the correction reported in the transcription:
here, Bowers' correction of <q>One</q> to <q>one</q>.</p>

<p>As these examples show, the field of application of the
<att>resp</att> attributes varies from element to element.  In some
cases, it applies to the content of the element (<gi>corr</gi> and
<gi>expan</gi>); in others it applies to the value of a particular
attribute (<gi>sic</gi>, <gi>abbr</gi>, <gi>del</gi>, etc.).  In all
cases where both the <att>cert</att> and <att>resp</att> attributes are
defined for a particular element, the two attributes refer to the same
aspect of the markup.  The one indicates who is intellectually
responsible for some item of information, the other indicates the degree
of confidence in the information.  Thus, for a
correction, the <att>resp</att> attribute signifies the person
responsible for supplying the correction, while the <att>cert</att>
attribute signifies the degree of editorial confidence felt in that
correction.  For the expansion of an abbreviation, the
<att>resp</att> attribute signifies the person responsible for supplying
the expansion and the <att>cert</att> attribute signifies the degree of
editorial confidence felt in the expansion.</p>

<p>This close definition of the use of the <att>resp</att> and
<att>cert</att> attributes with each element is intended to provide for
the most frequent circumstances in which encoders might wish to make
unambiguous statements regarding the responsibility for and certainty of
aspects of their encoding.  The <att>resp</att> and <att>cert</att>
attributes, as so defined, give a convenient mechanism for this.
However, there will be cases where it is desired to state responsibility
for and certainty concerning other aspects of the encoding.  For
example, one may wish in the case of an apparent addition to state the
responsibility for the use of the <gi>add</gi> element, rather than the
responsibility for identifying the hand of the addition.  It may also be
that one editor may make an electronic transcription of another editor's
printed transcription of a manuscript text --- here, one will wish to
assign layers of responsibility, so as to allow the reader to determine
exactly what in the final machine-readable transcription was the
responsibility of each editor.  In these complex cases of divided
editorial responsibility for and certainty concerning the content,
attributes and application of a particular element, the more general
mechanisms for representing certainty and responsibility described in
chapter <ptr target="CE"> should be used.</p>

<p>The fields of reference of the <att>resp</att> and <att>cert</att>
attributes for each element have been chosen to enable what are felt as
the most frequent likely statements an encoder may wish to make
concerning the areas of responsibility and certainty related to that
element.  It is open to each local transcription scheme to vary the use
of the <att>resp</att> and <att>cert</att> attributes on particular
elements where it is felt convenient.  This practice should be
documented in the <gi>encodingDesc</gi> element in the file header.
Further, it is recommended that before interchange any such local usage
of these attributes be converted to conformancy with the definitions of
the <att>resp</att> and <att>cert</att> attributes given in these
<title>Guidelines</title>.  Use of the <att>resp</att> and
<att>cert</att> in interchange documents in ways not here defined may
lead to unpredictable results.</p>


<p>It should be noted that the certainty and responsibility mechanisms
described in chapter <ptr target="CE"> replicate all the functions of the
<att>resp</att> and <att>cert</att> attributes on particular elements.
For example, the encoding of Donaldson's conjectured emendation of
<mentioned>wight</mentioned> to <mentioned>wright</mentioned> in line 117 of Chaucer's
<title>Wife of Bath's Prologue</title>, (see <ptr target="PHcc">) may be
encoded as follows using the <att>resp</att> and <att>cert</att>
attributes on the <gi>corr</gi> element:

<eg>
<![ CDATA [
<corr sic="wight" resp=ETD cert=70>wright</>
]]>
</eg>

Exactly the same information could be conveyed using the certainty
and responsibility mechanisms, as follows:

<eg>
<![ CDATA [
<corr sic="wight" id=c117>wright</>

<!-- ... certainty and responsibility elements may be elsewhere -->
<certainty target=c117 locus='#gicontent' degree=70>
<respons   target=c117 locus='#gicontent' resp=ETD>
]]>
</eg>

The choice of which mechanism to use is left to the encoder.  In
transcriptions where only such statements of responsibility and
certainty are made as can be accommodated within the <att>resp</att> and
<att>cert</att> attributes of particular elements, it will be economical
to use the <att>resp</att> and <att>cert</att> attributes of those
elements.  Where many statements of responsibility and certainty are
made which cannot be so accommodated, it may be economical to use the
<gi>respons</gi> and <gi>certainty</gi> elements throughout.</p>

<p>The above discussion supposes that in each case an encoder is able to
specify exactly what it is that one wishes to state responsibility for
and certainty about.  Situations may arise when an encoder wishes to
make a statement concerning certainty or responsibility but is unable or
unwilling to specify so precisely the domain of the certainty or
responsibility.  In these cases, the <gi>note</gi> element may be used
with the <att>type</att> attribute set to <q>cert</q> or <q>resp</q>
and the content of the note giving a prose description of the state of
affairs.</p></div3>


<div3 id="PHda"><head>Damage, Illegibility, and Supplied Text</head>

<p>The <gi>gap</gi> and <gi>supplied</gi> elements described above
(section <ptr target="PHom">) should be used with appropriate attributes
where the degree of damage or illegibility in a text is such that
nothing can be read and the text must be either omitted or supplied
either conjecturally or from other sources.  In many cases, however,
despite damage or illegibility, the text may yet be read with reasonable
confidence.  In these cases, the following elements should be used:

<list type=gloss>
<label><gi>damage</gi></label>
<item>contains an area of damage to the text witness.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>classifies the damage according to any convenient typology.</item>
<label><att>resp</att></label>
<item>indicates the individual responsible for identifying the 
area of damage.</item>
<label><att>hand</att></label>
<item>In the case of damage (deliberate defacement, etc.) 
assignable to an identifiable hand, signifies the hand 
responsible for the damage.</item>
<label><att>agent</att></label>
<item>In the case of damage resulting from an identifiable cause, 
signifies the causative agent.</item>
<label><att>degree</att></label>
<item>Signifies the degree of damage according to a convenient 
scale. The <gi>damage</gi> tag with the <att>degree</att> 
attribute should only be used where the text may be read 
with some confidence; text supplied from other sources 
should be tagged as <gi>supplied</gi>.</item>
<label><att>extent</att></label>
<item>indicates approximately how much text is in the damaged 
area, in letters, minims, inches, or any appropriate unit, 
where this cannot be deduced from the contents of the tag. 
For example, the damage may span structural divisions in 
the text so that the tag must then be empty of content.</item>
</list>
</item>
<label><gi>unclear</gi></label>
<item>contains a word, phrase, or passage which cannot be 
transcribed
with certainty because it is illegible or 
inaudible in the source.
Attributes include:
<list type=gloss>
<label><att>reason</att></label>
<item>indicates why the material is hard to transcribe.</item>
<label><att>resp</att></label>
<item>indicates the individual responsible for the transcription 
of the letter, word or passage contained with the 
<gi>unclear</gi> element.</item>
<label><att>cert</att></label>
<item>signifies the degree of certainty ascribed to the 
transcription of the text contained within the 
<gi>unclear</gi> element.</item>
<label><att>hand</att></label>
<item>Where the difficulty in transcription arises from action 
(partial deletion, etc.) assignable to an identifiable 
hand, signifies the hand responsible for the action.</item>
<label><att>agent</att></label>
<item>Where the difficulty in transcription arises from an 
identifiable cause, signifies the causative agent.</item>
</list>
</item>
</list>
</p>

<p>The following examples refer to the recto of folio 5 of the unique
manuscript of the Elder Edda.<note place="foot">Codex Regius, ed.  L. F.
A. Wimmer and F. J&oacute;nsson (Copenhagen 1891).</note> Here, the
manuscript of <title>V&ohook;lusp&aacute;</title> has been damaged
through irregular rubbing so that letters in various places are obscured
and in some cases cannot be read at all.  The existence of the damage
may be registered in general for this leaf by use of the <gi>damage</gi>
element.

<eg>
<![ CDATA [
<damage agent='rubbing at edges' extent='whole leaf'> ... </>
]]>
</eg>

However, in fact the damage crosses structural divisions, so the
<gi>damage</gi> element does not nest properly within the containing
<gi>div</gi> elements.  The simplest method to solve this problem is to
split the element into two fragments, one within each structural
division:

<eg>
<![ CDATA [
<div>
  <!-- beginning of division ... -->
  <!-- page break, beginning of damage -->
  <pb n='5r'>
  <damage agent='rubbing at edges' extent='whole leaf'>
  <!-- text continues -->
  </damage>
</div>
<div>
  <damage agent='rubbing at edges, continued' extent='whole leaf'>
  <!-- beginning of new text division ... -->
  <!-- page break, end of this damaged section -->
  </damage>
  <pb n='5v'>
  <!-- text continues ... -->
</div>
]]>
</eg>

For other techniques of handling non-nesting information, see chapter
<ptr target="NH">.</p>

<p>In the first line of this leaf, the transcriber may believe that the
last three letters of <mentioned>daga</mentioned> can be read clearly despite
the damage:

<eg>
<![ CDATA [
um aldr d<damage>aga</> yndisniota
]]>
</eg></p>

<p>Alternatively, the letters in question may be only imperfectly
legible on account of the damage; this state of affairs may be indicated
by nesting an <gi>unclear</gi> element within the <gi>damage</gi>
element.

<eg>
<![ CDATA [
um aldr d<damage><unclear>aga</></> yndisniota
]]>
</eg></p>

<p>Alternatively, the transcriber may not feel able to read the last
three letters of <mentioned>daga</mentioned> but may wish to supply them by
conjecture.  Note the use of the <att>source</att> attribute to assign
the conjecture to Finnur J&oacute;nsson:

<eg>
<![ CDATA [
um aldr d<supplied reason='rubbing'
                   source=FJ>aga</supplied>
yndisniota
]]>
</eg>

The <gi>supplied</gi> element may if desired be enclosed within a
<gi>damage</gi> element:

<eg>
<![ CDATA [
um aldr d<damage agent='rubbing'>
<supplied source=FJ>aga</supplied></damage>
yndisniota
]]>
</eg></p>

<p>Contrast the use of <gi>gap</gi> in the next line, where the
transcriber believes that four letters cannot be read at all because
of the damage:

<eg>
<![ CDATA [
&Thorn;ar k&hook-o;mr inn dimmi dreki fliugandi
na&thorn;r frann ne&thorn;an
<gap reason='rubbing' extent='4'>
]]>
</eg>

As with <gi>supplied</gi>, this <gi>gap</gi> might be enclosed by a
<gi>damage</gi> element.</p>

<p>In these examples, various phenomena of illegibility and conjecture
all result from the one cause, an area of damage to the text --- rubbing
at various points --- which is not continuous in the text, affecting it
at irregular points.  In these cases, the <gi>join</gi> element may be
used to indicate which tagged features are part of the same physical
phenomenon.  (See chapter <ptr target="SA"> for more details.)</p>

<p>The above examples record imperfect legibility due to damage.  When
imperfect legibility is due to some other reason (typically because the
handwriting is ill-formed), the <gi>unclear</gi> element should be used
without any enclosing <gi>damage</gi> element.  In Robert Southey's
autograph of <title>The Life of Cowper</title>,<note place="foot">In
Pierpont Morgan MA 412, (Klinkenborg 15).</note> the final six letters
of <mentioned>attention</mentioned> are difficult to read because of the haste
of the writing, though reasonably certain from the context.

<eg>
<![ CDATA [
and from time to time invited in like manner his
att<unclear>ention</unclear>
]]>
</eg>

The <att>cert</att> attribute on the <gi>unclear</gi> element may be
used to indicate the level of editorial confidence in the reading
contained within it.</p>

<p>The <gi>damage</gi> element is defined formally as follows:

<eg id=dphda>
<![ CDATA [
<!-- 18.2.3:  Damage and Illegiblity                          -->
<!ELEMENT damage        - O  (%paraContent;)                    >
<!ATTLIST damage             %a.global;
          extent             CDATA               #IMPLIED
          resp               IDREF               %INHERITED
          hand               IDREF               %INHERITED
          type               CDATA               #IMPLIED
          agent              CDATA               #IMPLIED
          degree             CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 18                         -->
]]>
</eg>


The <gi>unclear</gi> element is defined in section <ptr target="COed">.</p></div3>

<div3 id="Phcomb"><head>The Use of the Gap, Del, Damage, Unclear and Supplied Tags in Combination</head>

<p>The <gi>gap</gi>, <gi>damage</gi>, <gi>unclear</gi>,
<gi>supplied</gi> and <gi>del</gi> elements may be closely allied in
their use.  For example, an area of damage in a primary source might
be encoded with any one of the first four of these elements, depending on
how far the damage has affected the readability of the text.
Further, certain of the elements may nest within one another. The
examples given in the last sections illustrate something of how these
elements are to be distinguished in use.  This may be formulated as
follows:

<list type="bullets">

<item>where the text has been rendered completely illegible by
deletion or damage and no text is supplied by the editor in place of
what is lost: place an empty <gi>gap</gi> element at the point of
deletion or damage.  Use the <att>reason</att> attribute to state the
cause (damage, deletion, etc.) of the loss of text.</item>

<item>where the text has been rendered completely illegible by
deletion or damage and text is supplied by the editor in place of
what is lost: surround the text supplied at the point of deletion or
damage with the <gi>supplied</gi> element.  Use the <att>reason</att>
attribute to state the cause (damage, deletion, etc.) of the loss of
text leading to the need to supply the text.</item>

<item>where the text has been rendered partly illegible by deletion
or damage so that the text can be read but without perfect
confidence: transcribe the text and surround it with the
<gi>unclear</gi> element.  Use the <att>reason</att> attribute to state
the cause (damage, deletion, etc.) of the uncertainty in transcription
and the <att>cert</att> attribute to indicate the confidence in the
transcription.</item>

<item>where there is deletion or damage but the text can be read with
perfect confidence: transcribe the text and surround it with the
<gi>del</gi> element (for deletion) or the <gi>damage</gi> element (for
damage).  Use appropriate attribute values to indicate the cause and
type of deletion or damage.  Observe that the <att>degree</att>
attribute on the <gi>damage</gi> element permits the encoding to show
that a letter, word or phrase is not perfectly preserved, though it
may be read with confidence.</item>

<item>where there is an area of deletion or damage and parts of the
text within that area can be read with perfect confidence, other
parts with less confidence, other parts not at all: in transcription,
surround the whole area  with the <gi>del</gi> element (for deletion; or
the <gi>delSpan</gi> element where it crosses a structural boundary); or
the <gi>damage</gi> element (for damage).  Text within the damaged area
which can be read with perfect confidence needs no further tagging.
Text within the damaged area which can not be read with perfect
confidence may be surrounded with the <gi>unclear</gi> element.  Places
within the damaged area where the text has been rendered completedly
illegible and no text is supplied by the editor may be marked with
the <gi>gap</gi> element. For each element, one may use appropriate
attribute values to indicate the cause and type of deletion or damage
and the certainty of the reading.</item>
</list></p>

<p>The rules for combinations of the <gi>add</gi> and <gi>del</gi>
elements, and for the interpretation of such combinations, are
similar:

<list type="bullets">

<item>when one addition (<tag>add id=a1</tag>) includes another
(<tag>add id=a2</tag>), it indicates that an addition (a1) was first
made to the text, and later a second addition (a2) was made to the text
already added:

<eg>
<![ CDATA [
This is the text
<add id=a1>with some added
   <add id=a2>(interlinear!)</add>
material</add>
as written.
]]>
</eg></item>

<item>when one deletion (<tag>del id=d1</tag>) nests within another
(<tag>del id=d2</tag>), it indicates that the author wrote a passage,
deleted part of it (d1), and then later deleted the entire passage (d2).

<eg>
<![ CDATA [
<del id=d2>This sentence contains
some <del id=d1>redundant</del> unnecessary
verbiage.</del>
]]>
</eg></item>

<item>when an addition nests within a deletion, the normal
interpretation will be that an addition was made within a passage later
deleted in its entirety.</item>

<item>when a deletion nests within an addition, it indicates that a
deletion was made within a passage earlier added.</item>

</list></p></div3>

<div3 id="PHsp"><head>Space</head>

<p>The presence of significant space in the text being transcribed may
be indicated by the <gi>space</gi> element.  The author or scribe may
have left space for a word, or for an initial capital, and for some
reason the word or capital was never supplied and the space left empty.
This element should not be used to mark normal inter-word space or the
like.

<list type=gloss>
<label><gi>space</gi></label>
<item>indicates the location of a significant space in the copy 
text.
Attributes include:
<list type=gloss>
<label><att>dim</att></label>
<item>indicates whether the space is horizontal or vertical.
Legal values are:
<list type=gloss>
<label><term>horizontal</term></label>
<item>the space is horizontal.</item>
<label><term>vertical</term></label>
<item>the space is vertical.</item>
</list></item>
<label><att>extent</att></label>
<item>indicates approximately how large the space is, in letters, 
minims, inches, or other appropriate unit.</item>
<label><att>resp</att></label>
<item>indicates the individual responsible for identifying and 
measuring the space.</item>
</list>
</item>
</list>
</p>

<p>In line 694 of Chaucer's <title>Wife of Bath's Prologue</title> in
the Holkham manuscript the scribe has left a space for a word where
other manuscripts read <mentioned>preestes</mentioned>:

<eg>
<![ CDATA [
By god if wommen had writen storyes
As <space extent='7'> han within her oratoryes
]]>
</eg>

The <gi>supplied</gi> element discussed in the previous section may be
used to supply the text presumed missing:

<eg>
<![ CDATA [
By god if wommen had writen storyes
As <supplied reason='space' resp='ES' source='Hg'>
preestes</supplied> han within her oratoryes
]]>
</eg>

Here, the fact of the space within the manuscript is indicated by the
value of the <att>reason</att> attribute.  The source of the supplied
text is shown by the value of the <att>source</att> attribute as the
Hengwrt manuscript; the transcriber responsible for supplying the text
is ES.

The <gi>space</gi> element is formally defined thus:

<eg id=dphsp>
<![ CDATA [
<!-- 18.2.5:  Spaces in the source                            -->
<!ELEMENT space         - O  EMPTY                              >
<!ATTLIST space              %a.global;
          extent             CDATA               #IMPLIED
          dim                (horizontal | vertical) 
                                                 #IMPLIED
          resp               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 18                         -->
]]>
</eg>


<!-- <div3 id=PHorn><head>Ornaments</head>                    -->

<!-- <p>Printers' ornaments in the source may be encoded      -->
<!-- using the <gi>ornament</gi> element:                     -->

<!-- <tagList>                                                -->
<!-- <tagDesc tagDoc=ornament atts="desc">                    -->
<!-- </taglist>                                               -->

<!-- <p>On the title page of Randle Cotgrave's                -->
<!-- <title>Dictionarie of the French and English             -->
<!-- Tongues</title> (London, 1611; rpt. Colubmia:            -->
<!-- University of South Carolina Press, 1950), there         -->
<!-- appears (among many other things) an elaborate fleur     -->
<!-- de lys between the title and the imprint, which          -->
<!-- contains the inscription <q>IN DOMINO CONFIDO</q>.       -->
<!-- This might be transcribed thus:                          -->

<!-- <eg>                                                     -->
<!-- <![ CDATA [                                              -->
<!-- <titlePage>                                              -->
<!-- <docTitle>                                               -->
<!-- <titlePart>A Dictionarie</>                              -->
<!-- <titlePart>of the French                                 -->
<!-- and English Tongves.</>                                  -->
<!-- </docTitle>                                              -->
<!-- <docAuthor>                                              -->
<!-- compiled by <name rend=sc>Randle                         -->
<!-- Cotgrave.</name>                                         -->
<!-- </docAuthor>                                             -->
<!-- <ornament desc='fleur de lys'>                           -->
<!-- <s rend=sc>in domino confido</s>                         -->
<!-- </ornament>                                              -->
<!-- <docImprint>                                             -->
<!-- <pubPlace>London</pubPlace>                              -->
<!-- <publisher>Printed by Adam I&s;lip</publisher>           -->
<!-- <docDate>Anno 1611.</docDate>                            -->
<!-- </docImprint>                                            -->
<!-- </titlePage>                                             -->
<!-- ]]>                                                      -->
<!-- </eg>                                                    -->

<!-- <figure rend=float desc='title page of Cotgrave'>        -->
<!-- <figdesc>The title page of Randle Cotgrave's             -->
<!-- <title>Dictionarie of the French and English             -->
<!-- Tongues</title> (London, 1611).  </figure>               -->


<!-- The <gi>ornament</gi> element is formally defined        -->
<!-- thus:                                                    -->

<!-- <dtdfrag id=dPHorn n='Ornaments in the source'>          -->
<!-- <tagdecl tagdoc=ornament>                                -->
<!-- </dtdfrag>                                               --></p></div3>


<div3 id="PHln"><head>Lines</head>

<p>The most common form of marking of text in manuscripts is by lines
written under, beside or through the text.  The lines themselves may be
of various types:  they may be solid, dashed, or dotted, doubled or
tripled, wavy or straight, or a combination of these and other
renderings.  The line may be used for emphasis, or to mark a foreign or
technical term, or to signal a quotation or a title, etc.:  the elements
<gi>emph</gi>, <gi>foreign</gi>, <gi>term</gi>, <gi>mentioned</gi>,
<gi>title</gi> may be used for these.  Frequently, a scholar may judge
that a line is used to delete text:  the <gi>del</gi> element is
available to indicate this.  In all these cases, the <att>rend</att>
attribute may be used on these or other elements to indicate that the
text is marked by a line and the style of the line.  Thus, Lawrence's
deletion by strike-through of <mentioned>my</mentioned> in the autograph of
<title>Eloi, Eloi, lama sabachthani</title> is noted:

<eg>
<![ CDATA [
For I hate this
<del hand='DHL' rend='strikethrough'>my</del> body,
which is so dear to me
]]>
</eg></p>

<p>There will be instances, however, where a scholar wishes only to
register the occurrence of lines in the text, without making any
judgement as to what the lines signify.  In these the <gi>hi</gi>
element may be used, with the <att>rend</att> attribute to mark the
style of line.  In the manuscript of a letter by Robert Browning to
George Moulton-Barrett (Pierpont Morgan MA 310, Klinkenborg 23), the
underlining of the phrase <q>had obtained all the letters to Mr Boyd</q>
may be marked:

<eg>
<![ CDATA [
I have once,--by declaring I would prosecute
by law--, hindered a man's proceedings who
<hi rend=underline>had obtained all the letters
to Mr Boyd</hi>
]]>
</eg></p>

<p>The above examples presume the common case where a single word or
phrase is marked by a line, with no doubt as to where the marking begins
or ends and with no overlapping of the area of text with other marked
areas of text.  Where there is doubt, the <gi>certainty</gi> element may
be used to record the doubt.  In the Browning example cited above the
underlining actually begins half-way under <mentioned>who</mentioned>, and this
uncertainty could be remarked as follows:

<eg>
<![ CDATA [
I have once,--by declaring I would prosecute
by law--, hindered a man's proceedings who
<hi id=cstart1 rend=underline>had obtained all
the letters to Mr Boyd</hi>

<!-- ... -->
<certainty target=cstart1
           locus='#startloc'
           desc='may begin with previous word'
           degree='0.70'>
]]>
</eg></p>

<p>Where the area of text marked overlaps other areas of text, for
example crossing a structural division, one of the span mechanisms
outlined in these Guidelines may be used.  Where the line is thought to
mark a deletion, the <gi>delSpan</gi> element may be used.  Where it is
desired simply to record the marking of a span of text in circumstances
where it is not possible to surround the text with a <gi>hi</gi>
element, the <gi>span</gi> element may be used with the <att>rend</att>
attribute indicating the style of line-marking.</p>

<p>More work needs to be done on clarifying the treatment of other
textual features marked by lines which might so overlap or nest.  For
example, in many Middle English manuscripts (e.g. the Jesus and Digby
verse collections) marginal sidebars may indicate metrical structure:
couplets may be linked in pairs, with the pairs themselves linked
into stanzas. Or, marginal sidebars may indicate emphasis, or may
point out a region of text on which there is some annotation: in many
manuscripts of Chaucer's <title>Wife of Bath's Prologue</title> lines
655-8 are marked with nesting parentheses against which the scribe
has written <mentioned>nota</mentioned>.</p>

<p>At the lowest level, all such features could be captured by use of
the <gi>note</gi> element, containing a prose description of the
manuscript at this point.  It is not yet clear how best to mark up such
phenomena so as to
obtain more usefully structured encodings.  For example,
in the Chaucer example just cited, one may wish to record that the
<mentioned>nota</mentioned> is written in the Hengwrt manuscript in the right
margin against a single large left parenthesis bracketing the four
lines, with two right parentheses in the right margin bracketing two
overlapping pairs of lines:  the first and third, the second and fourth.
The <gi>note</gi> element allows us to record that the scribe wrote
<mentioned>nota</mentioned>, but is not well-adapted to show that the
<mentioned>nota</mentioned> points both at all four lines and at two pairs of
lines within the four lines.  Work will continue in this area.</p></div3></div2>

<div2 id="PHsk"><head>Headers, Footers, and Similar Matter</head>

<p>As a rule, matter associated with the page break (signature,
catchword, page number) should be drawn into the <gi>pb</gi> element
as attributes:  see section <ptr target="COrs">.  In text-critical
situations where these elements need tagging in their own right (for
instance, when the catch-word presents a variant reading, or spacing
in the header or footer is significant for compositor identification)
the element <gi>fw</gi> may be used:

<list type=gloss>
<label><gi>fw</gi></label>
<item>contains a running head (e.g. a 
<socalled>header</socalled>,
<socalled>footer</socalled>), 
catchword, or similar material
appearing on the current 
page.
Attributes include:
<list type=gloss>
<label><att>place</att></label>
<item>indicates where on the page this material appears.
Suggested values include:
<list type=gloss>
<label><term>left</term></label>
<item>in left margin.</item>
<label><term>right</term></label>
<item>in right margin.</item>
<label><term>top</term></label>
<item>top of the page.</item>
<label><term>bot</term></label>
<item>bottom of the page.</item>
</list></item>
</list>
</item>
</list>


The name <mentioned>fw</mentioned> is short for <q>forme work</q>. It
may be used  to encode any of
the unchanging portions of a page forme, such as:

<!-- often referred to as the <term>skeleton</term>.  Since -->
<!-- running heads are not always part of the skeleton, and -->
<!-- catchwords almost never are, the use of the term here -->
<!-- represents, strictly speaking, an extension of its usual -->
<!-- denotation.  The <gi>fw</gi> element may be used to encode: -->

<list type="bullets">
<item>running heads (whether repeated on every page, or changing on
every page)</item>
<item>running footers</item>
<item>page numbers</item>
<item>catch-words</item>
<item>other material repeated from page to page, which falls outside the
stream of the text</item>
</list>

It should not be used for marginal glosses, annotations, or textual
variants, which should be tagged using <gi>gloss</gi>, <gi>note</gi>, or
the text-critical tags described in chapter <ptr target="TC">,
respectively.</p>

<p>For example:

<eg>
<![ CDATA [
 <fw place=top-centre type=head>Po&euml;ms.</fw>
 <fw place=top-right type=pageno>29</fw>
 <fw place=bot-centre type=sig>E3</fw>
 <fw place=bot-right type=catch>TEMPLE</fw>
]]>
</eg><!-- Donne, Poems 1633, p. 29 -->


<!-- [Need several examples, all fuller than this one.     -->
<!-- Take from DOSL materials? -MSM]                          --></p>

<p>The formal declaration for the <gi>fw</gi> element is
this:

<eg id=dtchd>
<![ CDATA [
<!-- 18.3:  Headers and footers                               -->
<!ELEMENT fw            - O  (%phrase.seq;)                     >
<!ATTLIST fw                 %a.global;
          place              CDATA               #IMPLIED
          type               CDATA               #IMPLIED       >
<!-- This fragment is used in sec. 18                         -->
]]>
</eg>
</p></div2>



<div2 id="Phtrxx"><head>Other Primary Source Features not Covered in These Guidelines</head>

<p>We repeat the advice given at the beginning of this chapter, that
these recommendations are not intended to meet every transcriptional
circumstance ever likely to be faced by any scholar.  They are intended
rather as a base to enable encoding of the most common phenomena found
in the course of scholarly transcription of primary source materials.
These guidelines particularly do not address the encoding of physical
description of textual witnesses:  the materials of the carrier, the
medium of the inscribing implement, the layout of the inscription upon
the material, the organisation of the carrier materials themselves (as
quiring, collation, etc.), authorial instructions or scribal markup,
etc.  Some of these issues may be covered in future editions of these
guidelines.
</p></div2></div1>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
-->
             <!-- 18 Physical Character -->
