TEI Documentation
Para1The Douai Shakespeare Manuscript Project is encoded in TEI-XML using the customization
developed by Linked Early Modern Drama Online (LEMDO) for encoding early modern drama
and related critical paratexts. Full documentation for the LEMDO customization is
available at https://lemdo.uvic.ca.
Transcriptional Tagging
Para2We have followed the LEMDO Encoding Guidelines for our basic encoding model, in particular
Chapter 12. Semi-Diplomatic Transcriptions: Printand
Chapter 13. Semi-Diplomatic Transcriptions: Manuscript.Deletions from the manuscript are tagged with the
<del>
element. Additions are tagged with the
<add>
element. Additions in a different hand have been tagged with the
@hand
attribute either on the
<add>
element or on the
<stage>
element in the case of added stage directions. The value of the
@hand
attribute points to an description in the TEI Header, which in turn points to a hand
in the LEMDO Handography. Abbreviations have been tagged with the
<abbr>
and
<expan>
elements inside a parent
<choice>
element. Our expansions can be viewed via the Reading Modespane under
Toolsmenu. Conjoined words (i.e., words without a space in between) have been tagged with
<sic>
and
<corr>
elements inside a parent
<choice>
element. The Reader-friendlyreading mode expands the abbreviations and conjoined words by displaying the text node of the
<expan>
and
<corr>
elements, and suppresses the text node of the
<del>
elements. Page numbers stamped on the recto of each folio are transcribed into the
<fw>
elements.Structural Tagging
Para3Each play in the manuscript is transcribed and encoded in a
separate XML file. Titles and cast lists are contained in the
<front>
element. In those cases where the title is on its own page,
<docTitle>
is
contained with the
<titlePage>
element. The text of the play is contained
within the
<body>
element, but, in keeping with the LEMDO customization, not
further divided into
<div>
elements. The beginnings of acts and scenes are
encoded with
<milestone>
elements. The scribal act and scene numbers (often
marginal) are tagged with
<label>
. The main structural division in the manuscript is the page, which is captured with
the milestone
<pb>
element. Editorial page numbers (e.g., 171v) are captured in the value of the
@n
attribute on
<pb>
. In keeping with LEMDO practices, we make a link to the facsimile of the page using
the
@facs
attribute; this tagging should be taken as an indication that the file transcribes
the manuscript page represented by the digital facsimile.Para4Speeches and speech prefixes are captured
within
<sp>
and
<speaker>
elements respectively so that they can be
lightly styled with anthology-level CSS. A
@who
attribute on
<sp>
points to
an
@xml:id
defined on the
<castItem>
elements. All speeches are wrapped in
<ab>
to avoid making an implication about verse or prose. We capture
scribal line beginnings with self-closing
<lb>
tags. Stage directions are
tagged with
<stage>
. We make no claim about the type of stage direction and therefore do not use LEMDO’s
taxonomy of stage direction types. Stage directions added in a different hand bear
the
@hand
attribute.1Metadata
Para5The metadata uses LEMDO’s prescriptions for the
<teiHeader>
. Although all nine plays are now bound together in Douai MS 787, there is evidence
that the plays were prepared separately. Therefore, each XML file has its own
<msDesc>
element.Mise-en-page
Para6We have overwritten the inherited lemdo-dev styling and
styled certain elements at the anthology level using the anthology’s SCSS file to
describe and display the approximate mise-en-page of repeated features (like the
folio number stamp). In addition, we have added an
@style
attribute to elements as
necessary in order to write inline CSS and CSS Flexbox. Our XML thus includes
descriptive CSS that also functions as rendering CSS. We use the
<space>
element with the
@dim
attribute and values of "vertical"
and
"horizontal"
to capture significant white space. Vertical spaces are
measured in lines ("line"
and fractions thereof; horizontal spaces are measured in characters ("char"
) and
fractions thereof.Damaged Pages and Unreadable Passages
Para7Torn pages and local damage are encoded with the
<gap>
element and a
@reason
attribute with a value of "damage"
. Unreadable passages are also encoded with the
<gap>
element and a value of "illegible"
. One leaf of Macbeth, the manuscript has been cropped; in this case, the reason for the missing letters
or words is given as "original-cropped"
.
Encoding the Hands
Para8There are five discrete hands in the Douai MS. It is normal practice in TEI to define
the hands and give each one an
@xml:id
in the
<teiHeader>
. Because we have nine discrete XML files, one for each of the transcribed plays,
each of which must call on the same hand identifications, LEMDO has created a Handographyfor us (HAND1), in which all five hands are defined. A brief description of each hand is included in the HTML output and in the standalone XML file published in the anthology.
Encoding Later Additions by Hand 1
Para9Hand 1 made additions, presumably on a second reading, added free-floating stage directions
to the right of the text and made minor corrections throughout. We have given an
@xml:id
to the changes made by Hand 1 in the
<creation>
element of the
<teiHeader>
of each discrete transcription file, as follows:
<creation>
<listChange>
<change xml:id="emdDouai_Mac_CHG_1">Additions and corrections by Hand DOUH1 at a later date.</change></listChange>
</creation>
Later additions by Hand 1 are encoded as follows, with the <listChange>
<change xml:id="emdDouai_Mac_CHG_1">Additions and corrections by Hand DOUH1 at a later date.</change></listChange>
</creation>
@change
attribute pointing to the id given to the hand defined in the
<change>
element:
<stage change="#emdDouai_Mac_CHG_1" place="plc-right-inline">(Aside)</stage>