This edition is still being proofed. Please do not cite this
preview until this notice is removed.
The editors welcome suggestions and corrections (see link above).
The following guidelines constitute a formalized markup scheme for this edition of the William B. Anderson letters. It approaches the problem of "levels of transcription" by supporting a continuum of presentations, from modernized to diplomatic.
| Feature Group | Feature |
|---|---|
| Abbreviation | Abbreviation |
| Annotation | Footnote |
| Bibliography | Works Cited Entry |
| Corrections and Emendations | Supplied text |
| Corrections and Emendations | Uncertain Reading |
| Corrections and Emendations | Additions-interlinear |
| Corrections and Emendations | Additions-marginal |
| Corrections and Emendations | Cancelation-Unrecoverable |
| Corrections and Emendations | Apparent Errors |
| Corrections and Emendations | Cancellation-Recoverable |
| Quotation | Quotation (speech or thought) |
| Handwriting | Shift in hand or medium |
| Highlighting | Underlining |
| Language | Foreign Terms |
| Names | Referring String |
| Names | Place Name |
| Names | Person’s Name |
| Page Layout | Line Break |
| Page Layout | Page Break |
| Gap in Transcription | Gap in transcription |
| Punctuation | Hyphen |
| Punctuation | Em Dash |
| Punctuation | Hyphen-End of Line |
| Rich Media | Images, Audio, and Video |
| Structure | Signature |
| Structure | Closing |
| Structure | Salutation |
| Structure | Paragraph |
| Structure | Misc. Divisions |
| Structure | Dateline |
| Titles | Title |
Common Name: Abbreviation
Contextual Notes: Abbreviations and acronyms might occur anywhere in your text. For purposes of markup, we will treat the entire abbreviation (e.g., “Cin”) as the abbreviation, not just the mark, if any, indicating missing letters; and the entire word as the expansion (e.g., “Cincinnati”), not just the missing letters.
Element Name: <abbr>
Encoding Rule: We will “favor” a diplomatic perspective, tagging abbreviations with <abbr> and providing an expanded version of most abbreviations and acronyms as “expan” attributes. Note two special cases: we will not tag common contractions such as “don’t” or “won’t" as abbreviations, nor will we tag initials as abbreviations. Anderson often uses abbreviations as a kind of shorthand, and it is that use that we want to capture in our encoding, rather than conventional spellings that no one would normally spell out (e.g., "don't").
Sample Source Text: Geo Morris
Sample Encoding:
<name type="person" reg="Morris,George"> <abbr expan="George">Geo</abbr> Morris</name>
Sample Image from the MSS: No example available
Common Name: Footnote
Contextual Notes: You may need to annotate your text in order to identify a person or place or to explain an editorial judgment you have made (e.g., if you think that the date Anderson wrote in his dateline is incorrect).
Element Name: <note>
Encoding Rule: When you need to annotate your text, place a note reference in the body of your letter and the text of the note in the <back> of your text in a separate <div> for Annotations. <note> tags in the body should have a “target” attribute, and <note> tags in the back matter should have a matching “id” attribute. [See TEI 6.8.1]
Sample Source Text: W. B. Anderson
Sample Encoding:
<!-- Place in text at point of note reference: --> W. B.
Anderson <seg> <note target="n1">1</note> </seg>
. . . . . . . . .
<!-- Place within the <back> element at the end of your file
(after the body of the letter): -->
<back>
<div1 type="Annotations" n="1">
<head>Notes</head>
<note id="n1">1. Riverboat captain . . . (10 October 1822-15 November 1897).
<bibl><title level=m>History of Allegheny County</title> 298-299</bibl>
</note>
</div1>
</back>
Sample Image from the MSS: No example available
Common Name: Works Cited Entry
Contextual Notes: Anytime you paraphrase, quote, or otherwise present information gleaned from another source, you need to provide a citation to that source.
Element Name: <bibl>
Encoding Rule: We will place a <div> of type “Citations” in the <back> of our texts. Below, I provide examples for encoding a printed book or journal article and a Web site. If you have questions about how to encode a particular site, please bring them up in class.
Sample Source Text: Author name. Book Title. Place of publication: publisher, year.
Sample Encoding:
<div1 type="Citations" n="2"> <listBibl> <head>WORKS CITED IN NOTES</head> <bibl id="XXX"> <author >LASTNAME, FIRSTNAME</author> [OR] <editor> LASTNAME, FIRSTNAME</editor> <title level="a" >ARTICLE, POEM, ETC</title> <title level="m" >BOOK, WEB SITE, ETC</title> <pubPlace>PLACEOFPUB</pubPlace> <publisher>PUBLISHER</publisher> <date>YEAR OF PUBLICATION</date> <extent>PAGES IN FORM XXX-XXX</extent> </bibl> <bibl id="HAC"> <author>Anon.</author>< title level="a">The Peabody Sisters</title> <title level="m" >Dictionary of Unitarian & Universalist Biography</title> <biblScope type="URL">http://www.uua.org/uuhs/duub/articles/peabodysisters.html</biblScope> <date>2002</date> <biblScope type="DateOfVisit">10 Feb 2003</biblScope> </bibl> </listBibl> </div1>
Sample Image from the MSS: No example available
Common Name: Cancelation-Unrecoverable
Contextual Notes: When Anderson or some later hand has canceled a letter, word, or phrase in such a manner that we cannot read the canceled material, we will encode an unrecoverable cancelation, distinguishing it from a physical gap in the page or text we cannot decipher.
Element Name: <del>
Encoding Rule: The tag should surround one of the following: [deleted letter], [deleted word], or [deleted words]. Provide three attributes: type=”unrecoverable”, rend=”(overstrike | overwritten | erased)”; hand=”WBA” [or whatever value is appropriate].
Sample Source Text: [an erased word]
Sample Encoding:
<del type=”unrecoverable” rend=”erased” hand=”WBA”>[deleted word]</del>
Sample Image from the MSS: No example available
Group: Corrections and Emendations
Common Name: Cancellation-Recoverable
Contextual Notes: When Anderson or some later hand has canceled a letter, word, or phrase in such a manner that we can read the canceled material, we will encode a recoverable cancelation.
Element Name: <del>
Encoding Rule: The tag should surround the recovered words. Provide three attributes: type=”recoverable”, rend=”(overstrike | overwritten | erased)”; hand=”WBA” [or whatever value is appropriate].
Sample Source Text: I will bring down and hand to some one on the shore
Sample Encoding:
<lb n=”013”/><del type="recoverable" hand="WBA" rend="overstrike"> I will bring down and hand to <lb n=”014”/> some one on the shore</del>
Sample Image from the MSS: Sample manuscript image
Group: Corrections and Emendations
Common Name: Uncertain Reading
Contextual Notes: This encoding should be used only as a last resort. If, after assessing all the available evidence, you cannot read a word that is not canceled or otherwise obscured, you may provide an uncertain reading.
Element Name: <unclear>
Encoding Rule: Surround the text is question with the <unclear> tag and provide attributes indicating your degree of certainty (e.g., cert=”50%) and your initials (e.g., resp=”HLU”).
Sample Source Text: [some text I am unsure of]
Sample Encoding:
<unclear cert=”50%” resp=HLU>unclear words</unclear>
Sample Image from the MSS: No example available
Group: Corrections and Emendations
Common Name: Additions-interlinear
Contextual Notes: Interlinear additions may appear above or below a line of text.
Element Name: <add>
Encoding Rule: Include a “place” attribute indicating whether the addition is above the line (”supralinear”) or below the line (”infralinear”). If the addition is by another hand. . . .
Sample Source Text: let’s go downtown [the day after] tomorrow
Sample Encoding:
let’s go downtown <add place=”supralinear” hand=”WBA”> the day after </add>tomorrow
Sample Image from the MSS: No example available
Group: Corrections and Emendations
Common Name: Additions-marginal
Contextual Notes: Additions may be placed in the top, left, right, or bottom margins.
Element Name: <add>
Encoding Rule: Include a “place” attribute indicating the placement of the addition (”top margin,” “left margin,” and so on. If the addition is by another hand, add a “hand” attribute.
Sample Source Text: Writing in line [can sometimes continue in the margins]
Sample Encoding:
Writing in lines <add place=”right margin” hand=”WBA”> can sometimes continue in the margins</add>
Sample Image from the MSS: No example available
Common Name: Underlining
Contextual Notes: The most commonly used highlighting technique in the Anderson letters is underscoring to add emphasis to a word.
Element Name: <hi>
Encoding Rule: Surround the highlighted text with the <hi> element and provide a “type” attribute that indicates the type of highlighting (underscoring most often in letters).
Sample Source Text: He took the worst approach
Sample Encoding:
He took the <hi rend=”underscore”>worst </hi>approach.
Sample Image from the MSS: No example available
Group: Corrections and Emendations
Common Name: Apparent Errors
Contextual Notes: If you believe that the writer has written something in error, report it along with whatever you believe the correct text to be.
Element Name: <sic>
Encoding Rule: Since we are favoring a diplomatic transcription, we will report the error and include a “corr” attribute giving the correct text.
Sample Source Text: percieve
Sample Encoding:
<sic corr="perceive">percieve</sic>
Sample Image from the MSS: No example available
Group: Corrections and Emendations
Common Name: Supplied text
Contextual Notes: You may add text to the document if you are certain that the text was intended but inadvertently omitted by the writer
Element Name: <supplied>
Encoding Rule: Enclose the text you are supplying within the <supplied> element and provide a “reason” attribute. Common values would be “illegible” and “omitted.” You can also include a “source” attribute if another source suggests your reading. You can use the <supplied> to contain an <unclear> or <del type=”unrecoverable”> element. See TEI 18.2.4.
Sample Source Text: you Can fork over to me all get when I come home
Sample Encoding:
you Can fork over to me all <supplied reason=”omitted”>you</supplied> get when I come home
Sample Image from the MSS: No example available
Common Name: Quotation (speech or thought)
Contextual Notes: This element should be understood as containing a textual structure; it does not suggest a particular manner of punctuating quotations. According to TEI, it represents “speech or thought marked as being quoted from someone else.”
Element Name: <q>
Encoding Rule: Enclose the quoted text within the <q> element and include any punctuation as entities (e.g., ").
Sample Source Text: He shouted, “get out of here!”
Sample Encoding:
He shouted, <q>"get out of here!"</q>
Sample Image from the MSS: No example available
Common Name: Shift in hand or medium
Contextual Notes: Changes in handwriting from one writer to another or one medium to another should be noted in your transcript.
Element Name: <handShift/>
Encoding Rule: See the sample encoding below for establishing a list of hands in the TEI header. In the text, include the empty <handShift/> element at the point where the handwriting shifts. Include a “new” attribute to indicate the writer by the ID established in the <handList> and an “ink” attribute to indicate the medium (e.g., ink=”pencil | pen”).
Sample Source Text:
Sample Encoding:
In the TEI Header within the <profileDesc>: <handList> <!-- IDENTIFY ANY HANDS THAT APPEAR IN A HANDWRITTEN OR ANNOTATED DOCUMENT--> <hand id="WBA" scribe=”William B. Anderson” first="yes"/> <hand id="UNK" scribe="Unknown" first="no"/> </handList> In the body of the letter: <handShift ink="pencil" new="UNK"/>
Sample Image from the MSS: Sample manuscript image
Common Name: Foreign Terms
Contextual Notes: If the writer shifts to a foreign language or uses a foreign term, note the shift.
Element Name: <foreign>
Encoding Rule: In the TEI header, you need to declare a list of languages used in your document (see example below). In your text, enclose any foreign terms or phrases in a <foreign> element and provide a “lang” attribute.
Sample Source Text:
Sample Encoding:
<!-- Languages: Declaring languages in your text. In order to indicate
shifts from one language to another in your text, TEI requires that
the profile description in your header first declare all the languages
used in your text. [See TEI 5.4.2 Language Usage]-->
<langUsage>
<language id="eng">American English</language>
<language id="lat">Latin</language>
<language id="ger">German</language>
</langUsage>
<!-- Languages: Marking a shift in language. In your
text, you indicate a shift in language using the global "lang"
attribute with the id value of the language from the header. [See TEI 4.3 Code Shifting] -->
<foreign lang="ger">Gott sei Dank!</foreign>
<foreign lang="lat">memento mori.</foreign>
Sample Image from the MSS: No example available
Common Name: Person’s Name
Contextual Notes: Note the difference between a proper name and a referring string (e.g., “Wife”).
Element Name: <name>
Encoding Rule: Include a “type” attribute with the value “person” and a “reg” attribute with a regularized version of the person’s name. If the person referred to is an author whose name appears in OSU's library catalog, we will use that version of the name for the regularized version. For Anderson's family members whose names are given in the biography that I have posted in Carmen (under the content topic "W. B. Anderson") , we can use those names. However we find the name, it should be listed in the format LASTNAME, FIRSTNAME MIDDLE_NAME (YEAR OF BIRTH - YEAR OF DEATH). If any of that information is not available, leave it out. If you have no information beyond a given name that appears in the text (e.g., an unidentified person referred to in the letters only by his or her first name), then do not supply a regularized version of the name.
Sample Source Text: Geo Morris
Sample Encoding:
<name type="person" reg="Morris, George"> <abbr expan="George">Geo</abbr> Morris</name>
Sample Image from the MSS: Sample manuscript image
Common Name: Place Name
Contextual Notes: Names of cities and towns should be encoded.
Element Name: <name>
Encoding Rule: The <name> element should have a “type” attribute that identifies the whether the string refers to a person or place as well as a “reg” attribute that supplies a regularized version of the proper name referred to. In the case of cities, the regularized name should include the state.
Sample Source Text: Shousetown
Sample Encoding:
<name type="place" reg="Shousetown, PA">Shousetown</name>
Sample Image from the MSS: No example available
Common Name: Referring String
Contextual Notes: Text that refers to a proper name without using a version of the name can be identified with the "referring string" element <rs>
Element Name: <rs>
Encoding Rule: The <rs> element should have a “type” attribute that identifies whether the string refers to a person or place as well as a “reg” attribute that supplies a regularized version of the proper name referred to. For the special case of the sender and recipient of a letter, we will nest <rs> tags in order to provide a second "type" attribute with the value "sender" OR "recipient" (see the example below). If the person referred to is an author whose name appears in OSU's library catalog, we will use that version of the name. For Anderson's family members whose names are given in the biography that I have posted in Carmen (under the content topic "W. B. Anderson") , we can use those names. However we find the name, it should be listed in the format LASTNAME, FIRSTNAME MIDDLE_NAME (YEAR OF BIRTH - YEAR OF DEATH). If the years of birth and/or death are not available, leave them out. In the case of cities, the regularized name should include the state.
Sample Source Text: Dear Wife
Sample Encoding:
<rs type="recipient"> <rs reg="Anderson, Mary Louisa, née Fischgens (1837-1911)" type="person"> Wife</rs></rs>
Sample Image from the MSS: No example available
Common Name: Page Break
Contextual Notes:
Element Name: <pb/>
Encoding Rule: Provide an “mmid� attribute whose value is the Media Manager Item ID for that page (see the content item in Carmen titled "Media Manager Item IDs for Page Images"). Also provide an “n� attribute whose value is the sequential page number -- even if Anderson does not number his pages. The page break with appropriate Media Manager ID and page number should appear at the beginning of each page, including the first.
Sample Source Text: [a page break]
Sample Encoding:
<pb mmid="/0/0fae4c6e-0056-4419-9325-15799bf50925" n="1"/>
Sample Image from the MSS: No example available
Common Name: Line Break
Contextual Notes: Lines may be difficult to determine. For instance, if Anderson adds a word or phrase between two lines of a letter, the added text would not constitute a line. If in doubt, consult.
Element Name: <lb/>
Encoding Rule: Encode the beginning of each line of the text with a <lb> tag, including salutations and closings. Provide an “n” tag whose three-digit value represents the sequential line number in the letter. The tag should be followed by a space unless the two lines are run together (as in the case of a soft hyphen).
Sample Source Text: I wish to inform you that
Sample Encoding:
<lb n="003"/> I wish to inform you that
Sample Image from the MSS: No example available
Common Name: Gap in transcription
Contextual Notes: Use when your transcription is incomplete because you are unable to read the text at all, perhaps because of a stain, torn page, or cancellation that renders the canceled text illegible. Do not use for legible text that you have difficulty deciphering.
Element Name: <gap>
Encoding Rule: The <gap> element should have a “reason” attribute and an “extent” attribute. For an inkblot covering a word or words, you could describe the extent as the number of words obscured. For a tear, provide approximate dimensions in centimeters.
Sample Source Text: allow for [illegible text] want of light.
Sample Encoding:
allow for <gap reason="ink blot" extent="one word"/>want of light.
Sample Image from the MSS: No example available
Common Name: Hyphen-End of Line
Contextual Notes: Nineteenth-century texts may break words across lines with a hyphen at the end of the first line, a colon or equal sign at the beginning of the second line, or with some other mark. Encoding such marks allows us to suppress them in presentations whose line breaks don’t match those of the manuscript.
Element Name: <seg>
Encoding Rule: If Anderson breaks a word across two lines with a hyphen or other mark, encode the end- and/or beginning-of-line hyphens (or marks) and the <lb> tag within a <seg> tag and a “type” attribute with the value “softhyphen.” Note: If he breaks a word across a line without a mark, make sure not to leave a space after the <lb> tag so that the word will not be separated when the lines are run together in a "literary" view.
Sample Source Text:
we are not able
to get out till tom
=orrow we will not
Sample Encoding:
<lb n="004"/> we are not able to get out till tom<seg type="softhyphen"> <lb n="005"/>=</seg>orrow we will not <lb n="009"/> . . . enjoy the com<seg type="softhyphen">
<lb n="010"/></seg>forts of our own fireside . . .
Sample Image from the MSS: Sample manuscript image
Common Name: Em Dash
Contextual Notes: Encode dashes (not hyphens) as em dashes.
Element Name: —
Encoding Rule: Use the entity name — to encode this mark of punctuation. Add white space around the entity only if you wish to indicate that Anderson did so.
Sample Source Text: Some text—some following text
Sample Encoding:
Some text—some following text
Sample Image from the MSS: No example available
Common Name: Hyphen
Contextual Notes: “True” hyphens—hyphens considered part of the conventional spelling of a word—should be encoded as dashes. If, by chance, they appear at the end of a line, they should be encoded as “true” hyphens rather than soft-hyphens because we want to retain them even if we reformat lines.
Element Name: ‐
Encoding Rule: Encode hyphens with the ‐ entity. Do not place extra white space around the entity if none appears in the text.
Sample Source Text: top-heavy load
Sample Encoding:
top‐heavy load
Sample Image from the MSS: No example available
Common Name: Images, Audio, and Video
Contextual Notes: You may want to embed images or other rich media in your edition or provide links to those media. In either case, you encode using the figure tag.
Element Name: <figure>
Encoding Rule: The <figure> element should contain a “rend” attribute with one of the following values: “link," “embedAud," "embedMov," or "embedImg." Text contained in the <head> element will be used as a caption for the image. The "url" attribute of the <xref> element should contain a URL pointing to the image. Text contained in the <xref> element will constitute the link text for any figure whose "rend" attribute has the value "link."
Sample Source Text: NA
Sample Encoding:
<!-- Code for linking to, or embedding, an image detail at a particular
place in your file. Here, we supply only the information unique to this use
of this image (in this case, the Media Manager itemID); everything else will be
handled by our XSL style sheet. The contents of the <head> can be superimposed
on the image; the contents of the <xref> can be used to construct a link. -->
<figure rend=”link”>
<head>Dateline 27 June 1862 - Letter03_pg1</head>
<figDesc> <xref url="C/cc918f45-896e-4226-a419-9261be2361ac.jpg?crop=1200,500,2000,400&scale=.4">
Click to view the dateline of this letter as it appears in the manuscript</xref>
</figDesc>
</figure>
Sample Image from the MSS: No example available
Common Name: Dateline
Contextual Notes: Typically appears on a separate line at the top of the first page of the letter.
Element Name: <dateline>
Encoding Rule: the <dateline> element should include (if present in the source document) a <name> element containing the city and a <date> element.
Sample Source Text: Pittsburgh June 27/62
Sample Encoding:
<dateline><address><name type="city" reg="Pittsburgh, PA">Pittsburgh</name></address> <date value="1862-06-27">June 27/62</date></dateline>
Sample Image from the MSS: Sample manuscript image
Common Name: Paragraph
Contextual Notes: Remember that you are encoding W. B. Anderson’s paragraphing. He might indicate paragraphing by indenting first lines, by starting a new line, or by leaving white space between paragraphs.
Element Name: <p>
Encoding Rule: Surround paragraphs with the <p> tag.
Sample Source Text: Any paragraph
Sample Encoding:
<p> <lb n="003"/>I wish to inform you that <lb n="004"/>we are not able to get out till tom . . . . . . . . . . . . . . . </p>
Sample Image from the MSS: No example available
Common Name: Salutation
Contextual Notes: Typically appears on a separate line at the beginning of a letter, after a dateline. Almost always contains either a name or a referring string.
Element Name: <salute>
Encoding Rule: Typically, the <salute> element will be followed by a <name> or <rs> element depending on how the recipient is addressed.
Sample Source Text: Dear Wife
Sample Encoding:
<salute>Dear</salute> <rs type="recipient"> <rs key="MLA" reg="Anderson, Mary Louisa, née Fischgens (1837-1911)" type="person">Wife</rs></rs>
Sample Image from the MSS: Sample manuscript image
Common Name: Closing
Contextual Notes: The Anderson letters each contain a closing at the end of the letter, in a few instances followed by a post script (PS).
Element Name: <closer>
Encoding Rule: The closing of a letter may include the closing salutation (encoded <salute>, as in the opener, and a <name>. Note that the sender’s name is enclosed in a <signed> element.
Sample Source Text: Your W B Anderson
Sample Encoding:
<closer> <lb/><salute>Your </salute> <signed> <name reg="Anderson, William B. (1822-1897)" type="person">WB Anderson</name> </signed> </closer>
Sample Image from the MSS: Sample manuscript image
Common Name: Signature
Contextual Notes: The signature in the closing of the letter.
Element Name: <signed>
Encoding Rule: The <signed> element should normally contain a <name> element with “reg” and “type” attributes.
Sample Source Text: Your WB Anderson
Sample Encoding:
<closer> <lb/><salute>Your </salute> <signed> <name reg="Anderson, William B. (1822-1897)" type="person">WB Anderson</name> </signed> </closer>
Sample Image from the MSS: No example available
Common Name: Misc. Divisions
Contextual Notes: Use the <div1> tag to encode text that is associated with, but not part of, the letter proper. Examples would include envelopes, notes written on the letter by a person other than the letter writer, or notes written at a time other than the time of composition.
Element Name: <div1>
Encoding Rule: The <div1> tag encloses a top-level division of the text of your document. Provide an “n” attribute indicating the number of the division within the text and a “type” attribute describing the nature of the division.
Sample Source Text: Mr Geo Morris [?] Room # 6
Sample Encoding:
<div1 n="1" type="Note"> <head/> <p> <add place="top-margin"> <handShift ink="pencil" new="UNK"/> <lb/>Mr <name type="person" reg="Morris, George"> <abbr expan="George">Geo</abbr> Morris</name> <unclear>[unclear word]</unclear> <lb/>Room # 6</add> </p> </div1>
Sample Image from the MSS: Sample manuscript image
Common Name: Title
Contextual Notes: Refers to titles of works, not honorific titles such as “Captain.”
Element Name: <title>
Encoding Rule: The title element takes a "level" attribute, which indicates whether the title refers to an article, book (or monograph), journal, series, or unpublished material, indicated as a, m, j, s, or u, respectively, thus making it possible to distinguish among such titles when processing and rendering them accordingly (TEI P4X, ch. 5.2.1).
Sample Source Text: Lord of the Rings
Sample Encoding:
<title level=”m”>Lord of the Rings</title>
Sample Image from the MSS: No example available
