Whitman Encoding Guidelines

From Whitman Archive
Jump to: navigation, search

Note: The encoding practices documented below are based on the P4 version of the TEI Guidelines for Electronic Text Encoding and Interchange. The Whitman Archive is currently updating all existing files to the newest version of the guidelines, P5, and all new content is encoded according to P5. In addition to changes resulting from revised elements and attributes in the TEI guidelines, we have also taken this moment of transition as an opportunity to reflect on, and in some cases modify, our editorial policies and encoding practices. These changes are not yet represented in the guidelines below. Although the guidelines below do not represent all aspects of current editorial policy and encoding practice, we believe they are still valuable for documenting the work and history of the Whitman Archive. We will make a revised version of the guidelines available as soon as possible.


Contents

Links to Other Draft Encoding Guidelines

Blue Book

Introduction

Use your browser's "Find (on this page)" function (Ctrl + F) to locate the term or string of characters you're looking for.

Using The Walt Whitman Archive Encoding Guidelines

These guidelines define current transcription and encoding practices of the Whitman editors and staff as we make Whitman's writings available on our website, The Walt Whitman Archive. While for the most part our practices have stabilized, discussion is ongoing, and our practices continue to evolve. The guidelines were last updated October 2005.

Two major sections make up the core of the guidelines: "Global" and "Local." Global describes those aspects of encoding that are consistent from document to document. Local addresses aspects that vary from document to document. We have designed the guidelines to be read in order, so we recommend that you first read the section on the global encoding before moving on to the local. Additionally, there is an Annotated Template with the basic tagging filled in and a Resource Section which has many useful resource tools, such as library codes, preferred citations, and links to TEI guidelines. If you have questions or comments please email Kenneth Price or Brett Barney.

Some Basic Vocabulary

The primary audience for these guidelines is Walt Whitman Archive staff, and staff members come to the project with varying degrees of familiarity with humanities computing. The following explanations of selected basic terms are intended to help those with limited experience better understand the guidelines:

TEI (Text Encoding Initiative)

As described on the TEI Consortium hompage, "The TEI is an international and interdisciplinary standard that helps libraries, museums, publishers, and individual scholars represent all kinds of literary and linguistic texts for online research and teaching, using an encoding scheme that is maximally expressive and minimally obsolescent." In other words, the TEI is a standard for making transcriptions of complicated texts (including handwritten manuscripts) readable by computers.

Markup and Encoding

Generally, these terms refer to the "tags" that we include in our transcriptions to mark textual features in a way that allows them to be processed by a computer.

Tag

The string of characters surrounded by "<" and ">". For example: <add>. Tags typically come in pairs, an "opening" one to mark the beginning and a "closing" one to mark the end of a section of the transcription. The example above is an opening tag. A closing tag includes a slash after the "<" to distinguish it: </add>. A pair of tags describes all of the transcription that they enclose, so if you wanted to note that the word "crusty" was added to a text, you would tag it like this: <add>crusty </add>.

Element

This is the core part of a tag—the first string of characters after the "<" in the open tag. For example, in <add type="insertion">, "add" is the element.

Attribute

This is a secondary part of a tag that creates a category for further describing the element. It appears after the element name in the opening tag. An attribute must be followed by a value (see next). An element may have more than one attribute, each separated from the element name and from other attribute/value combinations by a single space.

Value

This is a word or short phrase that classifies the element in terms of a particular attribute. It is contained within quotation marks and preceded by an equal sign. For example, in the following add tag, "type" and "place" are attributes and "unmarked" and "supralinear" are values: <add type="unmarked" place="supralinear">.

DTD (Document Type Definition)

This is a file that functions as our rulebook. Validating (or "parsing") our markup against the DTD is one tool we use to see whether our files are properly encoded. Though our DTD implements the TEI standard, the Whitman Archive DTD is unique, customized for our specific project needs.

Nesting

This refers to the practice of enclosing pairs of tags within other pairs of tags, a basic principle of properly structuring XML documents. For example, the tag pair <TEI.2> and </TEI.2> contain almost all of the other markup within a document (see the Annotated Template for a visualization of this). It is important to nest tags properly, so that a particular element does not overlap other elements. The following is an example of improperly nested markup: <l><add></l></add>. Compare this properly nested example: <l><add></add></l>. At any given point in a document several tags may be "open," but the tag most recently opened must always close before earlier tags close.

Stylesheet

An XSLT (Extensible Stylsheet Language for Transformation) stylesheet is a file that transforms the encoded manuscript into HTML (HyperText Markup Language) for use on the web. In other words, stylesheets are what we use to make the various XML-encoded documents display in consistent and attractive ways on our site.

The Purpose of Encoding

The Walt Whitman Archive is developing in many areas simultaneously. Currently, work is underway on the image gallery, on the interviews, on the presentation of the various editions of Leaves of Grass, on the poems published in periodicals, and on Whitman's disciples—that group of close friends and associates who sometimes collaborated with him, who promoted his work, and who shaped his legacy. However, since 2000 the main effort of the Whitman Archive has been directed toward editing and providing access to all of Whitman's poetry manuscripts, highly revealing documents that have never before been systematically collected, transcribed, and published. Scattered in over sixty institutions worldwide and often difficult to decipher, Whitman's manuscripts remain little known despite their importance for students and scholars.

The XML encoding of manuscripts has presented us with numerous challenges—in part the TEI was initially designed with a focus more on books than on manuscripts. Our tagging of manuscripts has in many cases required us to develop extensions. The modifications to TEI conform to the guidelines provided in Chapter 29, "Modifying and Customizing the TEI DTD" in the Text Encoding Initiative Guidelines for Electronic Text Encoding and Interchange (Oxford: TEI Consortium, 2002).

XML encoding is not mechanical but interpretive. Sophisticated users of the Whitman Archive may wish to understand our tagging from the inside, as it were, thereby better grasping the query potential of our Archive. We wish to be overt about what the Whitman Archive has chosen, thus far, to encode regarding Whitman poetry manuscripts. The thus far in that sentence points to a key aspect of encoding: it is a process that can go through multiple passes and layerings. Generally speaking, our approach in tagging is to encode at a non-controversial structural level. Thus we tag titles, lines, and the like. This tagging will enable searches on discrete parts of documents (e.g., sections, lines, clusters, titles) within individual poems, across printed poems, across all poems, etc. One could also do, say, thematic tagging, but we have avoided that because we have felt that it would lead to endless internal debates on the project and might lead to a too-coercive editorial presence or at least to an end product that was too bound and too limited by the perspectives and the historical moment of the current creators of this site.

There are other features that it would not be controversial to tag, that would be useful information to have accessible, but that we have nonetheless chosen not to tag. For example, we have not recorded paper types, nor have we noted ink and pencil colors. We can certainly imagine scholars who could make brilliant use of this information if it were systematically recorded across all of Whitman's available documents. Still, a project such as the Whitman Archive constantly faces practical questions about what to prioritize. The magnitude of the entire undertaking is so vast that we know that we can at best hope to achieve a first pass through the material. Whitman himself sometimes thought that he left his writings for "poets to come" who would justify him and make clear his significance. Something analogous is at work in our hope that we can produce through the Whitman Archive not a monumental product but instead a monumental process that can be continued, corrected, and otherwise improved by future scholars. Other scholars with special interests in particular aspects of textuality could take our initial tagging and add additional layers that would enable various types of analysis.

Assuming continuing cooperation from libraries, we hope to make it possible for any interested person to look at images of all the known manuscripts; to search, in complicated ways, the text of those manuscripts and the rest of Whitman's work; to find out quickly where the physical documents are held; and to begin to make sense of a vast collection of important documents.

Like other electronic editing projects, we find we are limited in models to follow. Since we are doing new things, we cannot simply adopt tried-and-true methods but must to some extent invent our own way. The work of individual encoders is invaluable to the project, as it translates into practice the theoretical conclusions that we've come to since beginning work on the Whitman Archive in 1995. Encoding manuscripts and other documents is some of the most complex and valuable work we have underway.

Getting Started

Before you begin to encode your first manuscript, you'll need to get an assignment from one of the project editors. This process is managed by the Manuscript Tracking Database (password required). Here, you will get the image(s) of the manuscript and the unique id that you will use while encoding. After you locate an assigned document in the database, you must mark it "Checked Out."

Often, it will be useful for you to consult the notes accompanying the manuscript images, notes that were made by the institution or individual as they created the digital images. These notes describe the relationship of the individual images to other images (for example, recto/verso relationships) and, where applicable, provide the folder name and other important bibliographical information. To look at these notes (which, due to the complicated history of the project, vary in form and completeness), please go to the appropriate directory within the Image Warehouse (password required). In most cases, notes are included with the raw images.

Individual encoders use various software to create encoded documents, though NoteTab has been popular and is recommended. It is also important to work at a machine with imaging software that allows you to "zoom in" on complicated portions of the manuscript or do other manipulations that enable easier and more accurate transcription.

Once you have finished transcribing and encoding and have validated the file against the DTD, you must return to the Manuscript Tracking Database to "Check In" your document. This procedure uploads the file so that others may double-check it and publish it on the site. After you have uploaded the file, please type "Yes" in the "Final Transcription" box on the database upload screen.

Global

[Note: Above the Header of each document are the XML Declaration, Document Type Declaration, External Entity Declarations, and the open tag of the "root element," TEI, which contains all other elements. Please go to the Annotated Template to read more about how to insert these.]

Header

Every XML document we create has a "header," which carries essential information about who is responsible for creating and publishing the document, the source of the text we are marking up, and kind of electronic title page. The header is analogous to a book's first few pages, which inform you of the author, publisher, copyright date, terms of publication, etc.

Since much of the information in the header is the same for all of the XML documents we create, we recommend that you use the template to simplify your encoding of it.

Below, you will find descriptions of the main parts of the header, and you can click here to consult an annotated version of the template.

The <teiHeader> has three principal components:

  • <fileDesc> contains a full bibliographic description of an electronic file
  • <profileDesc> provides a detailed description of non-bibliographic aspects of a text, specifically the situation in which it was produced, the participants, and their setting
  • <revisionDesc> summarizes the revision history for a file

These elements are arranged within the <teiHeader> in this order, so the overall structure of <teiHeader> is this:

  • <teiHeader>
  • <fileDesc></fileDesc>
  • <profileDesc></profileDesc>
  • <revisionDesc></revisionDesc>
  • </teiHeader>


File description <fileDesc>
This should contain the following components:

Title statement <titleStmt> includes
1)the title given to the electronic work (which here always includes the subtitle provided by us: "a machine readable transcription"); 2) the author; 3) the editors; 4) information about others responsible for aspects of the electronic text; and 5) the name of the sponsors and funders. An example in which the original document bears a title given by Whitman:

<titleStmt>
<title level="m" type="main">Song of Myself</title>
<title level="m" type="sub"&gta machine readable transcription</title>
<author>Walt Whitman</author>
<editor>Ed Folsom</editor>
<editor>Kenneth M. Price</editor>
<respStmt>
<resp>Transcription and encoding</resp>
<name>The Walt Whitman Archive Staff</name>
</respStmt>
<sponsor>The Institute for Advanced Technology in the Humanities</sponsor>
<sponsor>University of Iowa</sponsor>
<sponsor>University of Nebraska-Lincoln</sponsor>
<funder>The National Endowment for the Humanities</funder>
<funder>The United States Department of Education</funder>
</titleStmt>


An example for a manuscript that lacks an authorial title (to read the guidelines for assigning titles, click here.):

<titleStmt>
<title level="m" type="main" rend="bracketed">I see who you are</title>
<title level="m" type="sub">a machine readable transcription</title>
. . .
</titleStmt>
etc.

Note that the title element includes a rend attribute that indicates it has been supplied by us and should therefore be displayed with brackets.

Edition statement <editionStmt> gives the current date. Example:

<editionStmt>
<edition>
<date>2005</date>
</edition>
</editionStmt>

Publication statement <publicationStmt>: includes the unique id number <idno>, distributor <distributor>, address <address>, and a statement of rights and availability <availability>.
Example:

<publicationStmt>
<idno>uva.00023</idno>
<distributor>The Walt Whitman Archive</distributor>
<address>
<addrLine>The Institute for Advanced Technology in the Humanities</addrLine>
<addrLine>Alderman Library</addrLine>
<addrLine>University of Virginia</addrLine>
<addrLine>P.O. Box 400115</addrLine>
<addrLine>Charlottesville, VA 22904-4115</addrLine>
<addrLine>whitman@jefferson.village.virginia.edu</addrLine>
</address>
<availability>

Copyright © 2005 by Ed Folsom and Kenneth M. Price, all rights reserved. Items in the Archive may be shared in accordance with the Fair Use provisions of U.S. copyright law. Redistribution or republication on other terms, in any medium, requires express written consent from the editors and advance notification of the publisher, The Institute for Advanced Technology in the Humanities. Permission to reproduce the graphic images in this archive has been granted by the owners of the originals for this publication only.

</availability>
</publicationStmt>

Source description <sourceDesc> gives a bibliographic description of the copy text(s) used in the creation of the present electronic text. Example:

<sourceDesc>
<bibl>
<author>Walt Whitman</author>
<title>Calamus Leaves</title>
<orgName>Yale Collection of American Literature, Beinecke Rare Book and Manuscript Library</orgName>
<note type="project">Transcribed from our own digital image of original manuscript.</note>
</bibl>
</sourceDesc>

Note on <orgName>: The institution that holds the manuscript should be cited as listed in the Preferred Citation table in the References section of the Encoding Guidelines.

Notes on description of source: This information is about the copy text, and the <title> here (as opposed to the one in titleStmt) should be given exactly as it appears in the records of the institutional repository, no matter how imprecise or wrong-headed their conventions may seem. Many times, the most specific title for the material will be that given to the folder used to store it, since few archives assign a title to each individual item; often, therefore, the <title> given in the <sourceDesc> will be a folder label.

At present, we almost always work from our own digital images, but we have also worked from Joel Myerson's facsmile reproductions of Whitman manuscripts (published in Joel Myerson, The Walt Whitman Archive: A Facsimile of the Poet's Manuscripts, New York: Garland, 1993.); from the Primary Source Media Whitman CD (Major Author's on CD-ROM: Walt Whitman, Eds. Ed Folsom and Kenneth M. Price, Woodbridge, CT : Primary Source Media, 1997); or from the original manuscripts themselves. Whatever the case, specific information about the image(s) and/or text(s) you rely on should be given in a <note>. If you consult more than one thing, list each, separated by semicolons. (Please note that when citing Myerson, the volume #, part #, and page # change from manuscript to manuscript.)

By the way, we say "our own digital image" rather than, say, the Whitman Archive's digital image so as to draw a clear distinction with Myerson's volumes, also called—somewhat confusingly—the Whitman Archive.


Profile description <profileDesc>

In the <profileDesc> is a list of all hands other than Whitman's that the markup declares as being in any way responsible, typically as the value of a "resp" (or "responsibility") attribute in a note, unclear, or gap element.

For example, if you are transcribing a Whitman manuscript that has a note by Fredson Bowers written physically on it, the header must have a <profileDesc> that reads:

<profileDesc>
<handList>
<hand scribe="Fredson Bowers" id="fb"/>
</handList>
</profileDesc>

(For more on this topic and how to encode non-Whitman writing on manuscripts, see section 3.10, "Writing in Others' Hands".)

You also need to include a <handList> in the <profileDesc> if your markup includes any <unclear> or <gap> elements, which require a "resp" attribute. For example, if Andy Jewell is encoding a manuscript with an unclear word and inserts this markup:

<unclear reason="cut away" cert="60%" resp="awj">herbage</unclear>

the document's <teiHeader> will need to include this <profileDesc>:

<profileDesc>
<handList>
<hand scribe="Andrew Jewell" id="awj"/>
</handList>
</profileDesc>

Revision description <revisionDesc>:
The revisionDesc element is used to summarize the changes that have been made to the file. It contains date, respStmt, name, and item elements to specify the date, responsible individuals, and changes. IMPORTANT: TEI allows only one <item> per <change>. If changes are performed at the same time, insert additional changes within the same <item> and use semicolons. If multiple changes are performed at different times, add another <change> at the top, so that changes are listed in reverse chronological order (most recent change first). To describe the tasks in our routine workflow, choose from the following terms for the content of <item>:

  • Transcribed; encoded
  • Checked; revised
  • Edited
  • Blessed

If the task is something other than these, any descriptive phrase can be used. Example:

<revisionDesc>
<change>
<date>2002-10-30</date>
<respStmt>
<name>Brett Barney</name>
</respStmt>
<item>Converted to camel case</item>
</change>
<change>
<date>2002-09-14</date>
<respStmt>
<name>Kenneth M. Price</name>
</respStmt>
<item>Edited</item>
</change>
<change>
<date>2002-09-07</date>
<respStmt>
<name>Andrew Jewell</name>
</respStmt>
<item>Checked; revised</item>
</change>
<change>
<date>2000-08-22</date>
<respStmt>
<name>Matt Miller</name>
</respStmt>
<item>Transcribed; encoded</item>
</change>
</revisionDesc>

Unique Identifiers

Description

Unique identifiers are one-of-a-kind names assigned to each electronic text we create. That is, every poem, collection of poems and work (for an explanation of "work" vs. "document" click here) must have a unique ID.

Creating and Assigning ID's

For manuscripts, IDs are made up of a 3-character repository code plus a 5-digit number (assigned in ascending order), with the two fields separated by a dot.

Examples:

  • loc.00158 (a manuscript at the Library of Congress)
  • uva.00001 (a manuscript at University of Virginia)

Printed texts are all assigned the 3-letter prefix "ppp."

ID Databases on the Web

We use a database to track the unique identifiers and our workflow as we transcribe, encode, and upload manuscripts. This database can be accessed here.

Placement of ID's

The unique identifier appears in two places in the TEI header:

  • As an attribute value in the TEI.2 root element (the very first tag):
<TEI.2 id="uva.00001">
  • As content in the <publicationStmt>:
<publicationStmt>
<idno>uva.00001</idno>

Transcription File Names

To name the file when you save it, simply add the file extension ".xml" to the ID.
Example:

uva.00023.xml

Image File Names

Each page image of a document is also given an ID, created by adding a three-digit suffix to the document ID. For example:

loc.00158.002 (Page 2 of a manuscript)

These page image IDs are inserted as the value of the corresp attribute of the appropriate page break elements (<pb/>), and an entity declaration for each one must be inserted between the square brackets in the document type declaration. Example:

. . .
<!DOCTYPE TEI.2 PUBLIC "-//UVA::IATH//DTD whitman.dtd (Whitman Archive)//EN" "whitman.dtd" [
<!ENTITY uva.00023.001 SYSTEM "uva.00023.001.jpg" NDATA jpeg>
<!ENTITY uva.00023.002 SYSTEM "uva.00023.002.jpg" NDATA jpeg>
]>
. . .
<pb corresp="uva.00023.001" />
. . .
<pb corresp="uva.00023.002" />

Basic Document Structure

Basic Elements for Marking Structure

The following elements are used to describe the structure of Whitman's poetic works:

  • Division <div1> through <div7>: Used, with the type attribute, to mark structural units larger than the cluster or poem. Values for the type attribute include "book," "section," "contents," "poem notes," "title notes," and "multiple poems." The largest unit is marked as <div1>, and descending levels of <div> can be nested inside. Click here to read an explanation of how these type attributes are used when marking up Whitman documents.
  • Line Group <lg1> through <lg7>: Function in the same way as <div>, but are used exclusively to mark clusters, poems, and structural sub-units within them (ie, groups of lines—"sections" or "linegroups"—that constitute distinct units within a poem). If the poem has no distinguishable sub-units within it, no further <lgs> are needed; if the poem has one or more sub-units, you need to mark each of those units with the appropriate <lg>. As with <div>s above, descending levels of <lg> are nested inside <lg1>. For example, for a manuscript of a poem broken into three linegroups, the poem itself would be tagged <lg1 type="poem"> and each linegroup would be tagged <lg2 type="linegroup">. The type attribute is required; values include "cluster," "poem," "section," and "linegroup."
  • Head <head>: Marks the title. Used on all <div>s and <lg# type="poem">s, even when the source shows no title. For a more thorough discussion click here. Requires the type attribute; choose from "main-authorial," "main-derived," and "sub."
  • Line <l>: Used to mark a poetic line.
  • Segment <seg>: Used to mark groups of words within a line of poetry that are in the same physical line. PLEASE NOTE: This tag is omitted when poetic lines run to only one physical line. Please read this note about idententation and spacing.

A sample structure might look like this:


<div1 type="poem notes">
<lg1 type="poem">
<head type="main-authorial" rend="underline"></head>
<l></l>
<l>
<seg></seg>
<seg></seg>
</l>
</lg1>
<lg1 type="poem">
<head type="main-derived"></head>
<lg2 type="linegroup">
<l>
<seg></seg>
<seg></seg>
<seg></seg>
</l>
<l></l>
</lg2>
<lg2 type="linegroup">
<l></l>
<l></l>
</lg2>
</lg1>

</div1>

Manuscript Genres

To figure out how to tag a particular manuscript, first look closely at its structure, and decide which of the following four categories it falls into. A guide on how to deal with each type follows.

  • Verse Only (can usually be identified by the use of line segmentation/hanging indentation)
  • Prose Only (may be divided into paragraphs)
  • A Mixture of Verse and Prose
  • Title Page
Verse Only
  • For a manuscript of one poem composed of a single group of lines, do not use a
    . Instead, use a structure like the following:

<text type="manuscript">
<body>
<lg1 type="poem">
<l>There is no word . . .
  • For a single poem clearly divided into smaller chunks:

<text type="manuscript">
<body>
<lg1 type="poem">
<lg2 type="linegroup">
<l>
<seg>[line segment here]</seg>
<seg>[line segment here]</seg>
</l>
. . .
</lg2>
<lg2 type="linegroup">[lines and segments here] </lg2>
</lg1>
</body>
</text>
  • For a manuscript containing two or more poems:

<text type="manuscript">
<body>
<div1 type="multiple poems">
<lg1 type="poem">[poem here]</lg1>
<lg1 type="poem">[poem here]</lg1>
</div1>
Prose Only
Prose should be divided into paragraphs.

No division tag is required in a prose-only document unless the prose is divided into separate intellectual units. For example, a manuscript requires <div1 type="section"> if it begins with two paragraphs about democracy, then has a clear break (e.g., a sub-heading, a horizontal line, or white space) followed by three paragraphs about the sound of the fishmonger yelling on the street. In such a case, the discreet groups of paragraphs should be marked with <div1>s. Except on title pages, line breaks <lb/> are not encoded. Also note that <lg>s are only used to markup poetry, never prose.


<text type="manuscript">
<body>
<div1 type="section">
<p></p>
<p></p>
</div1>
<div1 type="section">
. . .
</div1>
</body>
</text>
Mixed Genre

Many manuscripts contain single intellectual units which are a mixture of poetry and prose. (For an example, see the manuscript "Ashes of Roses," here) "Mixed genre," for our purposes, does NOT just mean a manuscript leaf with poetry and prose on it (for example, a poetic draft on the recto and prose on the verso). Rather, "mixed genre" signifies writing that is thematically unified, apparently part of a single draft, but made up of a mix of prose and verse, as when Whitman composes an early draft that combines trial poetic lines with prose notes or lists. For a mixed-genre manuscript, use a <div1> with "poem notes" as the value of the "type" attribute, like this:


<text type="manuscript">
<body>
<div1 type="poem notes">
etc.
Title Page

Some manuscripts have only titles, with no content to follow those titles, or are pages with several trial titles that Whitman never used (for an example, click here). For these unusual manuscripts, we have a different <div1> type, "title notes."


<text type="manuscript">
<body>
<div1 type="title notes">
etc.

To read about the unique markup used in Title Page manuscripts, go here.

Heading

A <head> tag, used to mark titles, will be used for both indexing and display. Please go here to read more about this titling procedure. Note that <head> can be on any structure; <div#> and <lg#> will be most common.

Titles and Naming

Each poetry manuscript transcription will have three different kinds of titles. These titles may be identical; they may be different.

This title, which occurs inside the TEI header, names the electronic file you are creating and should therefore be distinguished from the title of the source material. Do this by adding the phrase "a machine readable transcription" as a subtitle, as in the following example.

<titleStmt>
<title level="m" type="main">Death dogs my steps</title>
<title level="m" type="sub">a machine readable transcription</title>
</titleStmt>

If you are transcribing and encoding a manuscript that does not have a title written on it, derive a main title from the first line, as described below. Also, include the attribute rend with the value "bracketed," to signify that the title is one we have assigned based on the first line and should therefore be bracketed when displayed. An example:

<titleStmt>
<title level="m" type="main" rend="bracketed">And to me each minute of the night and day is vital and visible</title>
<title level="m" type="sub">a machine readable transcription</title>
</titleStmt>

For manuscripts that contain more than one poem, follow the above procedure for each poem, but for the value of level use "a" (which indicates individual items within a larger item). Then wrap all of these individual titles in another <title level="m">. The following example imagines a manuscript with two poems, the first of which Whitman has given a title and the second of which he hasn't.

<titleStmt>
<title level="m">
<title level="a" type="main">Title Written on Manuscript</title>
and
<title level="a" type="main" rend="bracketed">Title derived from first line</title>
</title>
<title level="m" type="sub">a machine readable transcription</title>
</titleStmt>

This title is the one given to the artifact by the holding institution. The <sourceDesc> is essentially a bibliography of information that should be sufficient for a user to locate the item that is the source of the transcription. If the title is bracketed in the online repository guide, you should bracket it in the <sourceDesc>. In some cases, the "title" in the <sourceDesc> may bear little relation to the poem—for example, it might be the title of the folder which holds the item rather than the title of the item itself (this is typically the case only for the Feinberg collection at the Library of Congress).

  • Title in the <head>

This is the location to which the stylesheet will go to pull titles of poems, etc. for indexing and display. For more detailed rules on how to formulate these titles, please see the section below.

  • The rules for the use of <head>:
    • Each <lg> and division tag can have its own <head> (and thus its own title). Head tags are required for <lg1 type="poem"> and for all division tags within <text type="manuscript">. Head tags are not required—nor typically necessary—on any other <lg> other than <lg1 type="poem"> or on division tags within notebooks (<text type="notebook">).
    • The "type" attribute on this element is required to differentiate titles physically present on the manuscript from those assigned by our project and to distinguish between main titles and subtitles. Use one of these three values:
      • main-authorial (written by Whitman on the page)
      • main-derived (assigned by us, derived via the formula for titles (see next section below)
      • sub (subtitle written by Whitman on the page; "sub" is only used for secondary authorial titles and must be preceded by <head type="main-authorial">)

Naming Poetry Manuscripts

We have developed a simple set of rules for giving names to Whitman's manuscript poems. Note that this naming is IN ADDITION TO the assignment of a unique identifier. The rules are listed here in the order of priority:

  • First priority: a name written by Whitman. (<head type="main-authorial">)
    • Disregard numbers (roman or arabic) AND punctuation that precede the first word (e.g., "?")
    • For authorial titles that Whitman has edited with additions and deletions, the procedure works like this:
      • In the <titleStmt> title, use the final reading of the title, disregarding deleted passages and including added ones. For instance, for this example, the <titleStmt> title would read:
<titleStmt>
<title level="m" type="main">Ah, not this granite dead and cold.</title>
<title level="m" type="sub">a machine readable transcription</title>
</titleStmt>
  • In the <head>, encode all the additions, deletions, and substitutions as such. For the same example, the <head> would be encoded like this:
<head type="main-authorial" rend="underline">
<app>
<rdg varSeq="1">
<del type="overstrike">Beyond this</del>
</rdg>
<rdg varSeq="2">
<add type="unmarked" place="supralinear">Ah, not this </add>
</rdg>
</app>
granite dead and cold.
</head>
      • If a manuscript is not titled by Whitman, in the <titleStmt> use the first words not struckthrough, and go up to (but do not include) the first punctuation mark OR the end of the line OR the end of the segment, WHICHEVER COMES FIRST. For <head> follow the same procedure and assign the attribute type="main-derived."
      • For poems with recurrent titles (like "Leaf"), use the title AND, in brackets, the title derived from the first line. So: Leaf [A promise to Indiana]
      • Don't worry if two poems have the same title. Our unique identifier for the document will enable us to locate the correct document for processing through stylesheets.

Reference to External Files

Entity Declarations and Page Breaks

There are two steps to linking a document to its corresponding image:


FIRST, declare the name and location of each image in an "entity declaration" right before the <TEI2> tag. In the sample below, the identifier following "!ENTITY" is the string that will be inserted within a <pb> tag; the string following "SYSTEM" is the name of the image file that corresponds with this identifier. Together, the two strings basically to tell the computer how to find the pictures.
Sample:

<!ENTITY loc.00001.001 SYSTEM "loc.00001.001.jpg" NDATA jpeg>
<!ENTITY loc.00001.002 SYSTEM "loc.00001.002.jpg" NDATA jpeg>
<!ENTITY loc.00001.003 SYSTEM "loc.00001.003.jpg" NDATA jpeg>
etc.

PLEASE NOTE:

  • Entity names (the first string) should NOT include the file extension.
  • Be sure the file name which follows SYSTEM includes the dot before the file extension.
  • Be consistent when giving file extensions—we've chosen to always use ".jpg" rather than ".jpeg" or ".jpe," for example.
  • The last portion of the declaration, "NDATA jpeg" should always be noted in that way. This does not contradict the rule just above.

SECOND, include a pb element BEFORE the content of each page, and in the corresp attribute give to the name of the entity you've declared at the top of the document:

<text><body>
<pb corresp="loc.00001.001" id="leaf01r" type="recto"/>
<lg1><l>etc.

PLEASE NOTE:

  • Do not include the file extension here.
  • The "type" attribute is required on the <pb> element. Choose between "recto" and "verso."
  • ID's must be unique within each document, so for manuscripts that have writing on both the recto and verso and/or that have more than one page, modify the id attribute for subsequent <pb>'s. For the recto of leaf one, use id="leaf01r"; for the verso of leaf one, use id="leaf01v," etc.
  • Include the id attribute even on one-page documents.
  • For printed works or manuscripts that have page numbers, also include an "n" attribute in the <pb>. So: <pb corresp="ppp.00001.001" id="leaf01r" type="recto" n="1"/>

Local

ENCODING THAT VARIES FROM DOCUMENT TO DOCUMENT

Spacing

Recent work with stylesheets has taught us that paying attention to and regularizing the encoding of white space is important as we prepare manuscripts for display on the site. The most important guideline is simply to be conscious of spacing as you transcribe and encode, but here are a few more specific rules to follow:

  • Be sure to put a space between words. Remember that, after processing, the markup will be invisible, so your transcription needs to include the spaces that separate words even when the words are separated in the XML document by one or more tags.
  • Avoid spaces before closing add or delete (del) tags. Since Whitman's revisions typically did not involve the addition or deletion of white space after the last word of a phrase, make sure you insert the space outside the closing add or delete tags. A properly spaced transcription looks like this:
<add type="unmarked" place="supralinear">Song</add> of Myself.
  • Within <app> structures, insert the spaces between the closing add or delete tag and the closing <rdg> tag. All characters must be contained within the "reading" or <rdg>, so spaces outside of <rdg> will be ignored. A properly spaced <app> structure should look like this:
Song of <app>
<rdg varSeq="1">
<del type="overstrike">You</del> </rdg>
<rdg varSeq="2">
<add type="unmarked" place="supralinear">Myself</add> </rdg>
</app>
  • Spaces before closing <l> or <seg> tags are unnecessary and should be eliminated.
  • Spaces before and after the em dash (—) should be eliminated.
  • Do not insert unnecessary spaces. Often, encoders have inserted spaces that are not part of the transcription (for example, to make the tagging more human-readable). You can use as many returns as you wish to make the markup easier to read, but please do not use the space bar.

(To learn how to encode Whitman's use of intentional space within lines, go here)

Deletions

What to Mark

Use <del> to mark a letter, word or passage that has been deleted by any method. Use common sense when marking deletions; if an entire line has been crossed out, for example, but the horizontal line does not physically intersect with a comma that follows the passage, you should still assume that the comma is intended to be included in the deletion. In cases of doubt, please consult Ed Folsom or Kenneth Price for his reading of the passage.

Attributes

type is the only required attribute for the del element. Possible values are:

  • overstrike: A line or lines are drawn through rejected letters, words, or passages. This is by far the most common method of deletion in Whitman manuscripts.
  • erasure: Whitman has erased part of the text.
  • hashmark: A vertical or diagonal line or lines marks through a large chunk of text (often the whole manuscript page).
  • pasteover: Whitman has deleted text by pasting another piece of paper on top of it.
  • overwrite: Letters or words are marked for deletion by being written over with other letters or words.

NOTE: Each of these types of deletion can occur in combination with additions; "overwrite" does by definition, and "pasteover" almost always does. For information about marking combinations of additions and deletions, see section 3.4, "Additions and Deletions in Combination."

Whitman's overstrikes are usally emphatic and easily recognizable, but occasionally one sees a mark which may be either an overstrike OR a stray pen mark. In these cases, first check with Kenneth Price or Ed Folsom, and then use the optional cert attribute to indicate your degree of certainty that the passage has been deleted. For example, on the Duke manuscript "I see who you are," a few lines from the bottom, the word "editor" appears to be struckthrough. This might be tagged as follows:

<del type="overstrike" cert="80%">editor</del>

Deletions of Longer Passages

Occasionally you will encounter a long passage that has been deleted. For these passages, use <del> unless doing so would create a nesting problem. For example, consider again the manuscript in the example above. Here, the long vertical strike is marked simply by enclosing the entire poem with a del element thus:

. . .
<body>
<pb/>
<del type="hashmark">
<lg1 type="poem">
. . .
</lg1>
</del>
</body>
. . .

Imagine, however, a different scenario, one in which a deleted passage consists of the last two words of one line segment <seg> and all of the next line segment. Because using <seg><del></seg><seg></seg></del> would violate the nesting rule, using paired tags to mark this kind of deletion is unacceptable. Instead, you must use the elements delSpan and anchor, the first to mark the beginning of the deleted passage and the second to mark the end. As with the delete tag,the type attribute is required for <delSpan>. The to attribute is also required, since it provides a "pointer" to the anchor. The value of the to attribute must be the same as the value of the required id attribute on the corresponding anchor element. To create these, use "d" (for a deletion) plus the next available number ("d1" for the first <delSpan>, "d2" for the second, and so on). Please note: if the manuscript calls for multiple <delSpan> elements, you will need to use distinct identifiers for each anchor. In other words, you may only use "d1" or "d2" once in a document; subsequent identifiers will have to be "d3," "d4," etc.

Consider as an example the Duke manuscript "To be at all". If we ignore other complexities for the moment, the multi-segment deletion in the line that begins "One no more than" should be marked as follows:

. . .
<seg>and out of me <delSpan type="overstrike" to="d1"/>of me more bliss</seg>
<seg>than I thought the spheres</seg>
<seg>could carry.</seg>
</l>
<anchor id="d1"/>

Additions

What to Mark

Use <add> to mark any part of the text whose placement, ink, etc. clearly indicate that it was added to the manuscript after the surrounding text was written.

Attributes

Two attributes are required on the <add> element: type and place.

For type, the possible values are:

  • insertion: marked by a caret (which often looks like an "x").
  • unmarked: added without caret or other mark.
  • overwrite: written over earlier text.
  • pasteon: written on a piece of paper that is glued to paper with earlier text.

For place, the possible values are:

  • supralinear: above the line.
  • inline: in space available on the same line as earlier text.
  • infralinear: below the line.
  • over: over the earlier letter, word, or phrase.
  • margintop: in top margin.
  • marginbot: in bottom margin.
  • marginleft: in left margin.
  • marginright: in right margin.
  • interlinear: between lines.

Addition of Longer Passages

The rules for marking long additions are similar to those for marking long deletions. Use <add> unless doing so would create a nesting problem, and use the elements addSpan and anchor to mark the beginning and end of a deleted passage that doesn't nest within other elements. <addSpan> has three requried attributes: to, type, and place. Available values for type and place are the same as those listed above for <add>. The value of the to attribute must be the same as the value of the required id attribute on the corresponding anchor element. To create these, use "a" (for "addition") plus the next available number ("a1" for the first <addSpan>, "a2" for the second, and so on).

Transpositions Noted by Arrows or Asterisks

Some manuscripts have brackets, arrows, and/or a series of asterisks to indicate Whitman's desire to move a line or lines to a different place in the poem. To encode this phenomenon, we use the <transpose> element. In this example, Whitman has bracketed one line and indicated with an asterisk in the margin that the line should be moved down. The encoding for this section follows, with the tagging most pertinent to the transposition in bold.

<note type="authorial" place="marginleft">-down</note>
<transpose rend="bracketed" anchored="yes" target="t1">
<l><seg>Of the native scorn of grossness</seg>
<seg>and gain there, (O it lurks</seg>
<seg>in me night and day—What</seg>
<seg>is gain, after all, to savage-</seg>
<seg>ness and freedom?)</seg></l>
</transpose>
<l><seg>Of immense spiritual <app><rdg varseq="1"><del type="overstrike">things</del></rdg>
<rdg varseq="2"><add type="unmarked" place="supralinear"> results</add></rdg></app>, future years,</seg>
<seg>inland, spread there each side of</seg>
<seg>the Anahuacs,</seg></l>
<l><seg>Of these Leaves established there, and</seg>
<seg>well understood there.—</seg></l>
<anchor id="t1"/>
<milestone unit="undeclared" rend="horbar"/>
<note type="authorial" place="marginleft">take down-</note>

Explanation:

  • We use <note> to transcribe any marginal characters that indicate the transposition.
  • When Whitman brackets the part to be moved, we add rend="bracketed" to the <transpose> tag.
  • The anchored attribute is used to note whether or not the manuscript clearly indicates where the line(s) are to be moved. (We know of at least one example where this is not known.) This attribute has one of two possible values: yes or no.
  • If the value of the anchored attribute is yes, a target attribute is required; it points to an <anchor> that is placed at the target—the point in the manuscript to which the part is to be moved. If the value of anchored is no, the target attribute is not required.

Additions and Deletions in Combination

Substitutions

Very frequently, Whitman's additions are not merely appended to earlier text but are substituted for earlier text. It is our policy to link the deleted and added portions by marking each as a reading <rdg> within an <app> element. ("App" is short for "apparatus entry." For information about the use of this element in other contexts, see chapter 19 of the TEI Guidelines.) Each <app> will contain at least two <rdg>s, and may contain up to five. The <app> element requires no attributes; the rdg element requires the varSeq ("variant sequence") attribute, the value of which is a single-digit number that indicates the relative order in which the present reading is presumed to have been written. For this example line segment, the markup would look like so:

<l><seg>Old Asia's
<app>
<rdg varSeq="1"><del type="overstrike">self</del></rdg>
<rdg varSeq="2"><add place="supralinear" type="unmarked"> there </add></rdg>
</app>
with venerable</seg>
. . .

For obvious reasons, usually the first reading will contain a deletion and the second reading will contain an addition. This is not always true, however. You may come across instances where multiple variants are left undeleted. In this case, the first <rdg> will contain no other elements, just the transcribed word(s).

Or you may find that a second reading was added but subsequently rejected in favor of the first. In this case, the second <rdg> will contain both an <add> and a <del>. (See "Nesting Add Tags and Delete Tags" below for an explanation of how to arrange these.)

If the state of the manuscript makes it difficult to determine with certainty the order of the readings, a resp attribute is available for the <rdg> element; the value of this attribute can be used to identify (by initials) the person responsible for asserting an order of readings.

Overwriting

You will sometimes encounter a substitution in which a letter or word has been overwritten with another letter or word. In such cases, the value of the place attribute on the add element is "over"; the value of the type attribute for both the add tag and delete tag elements is "overwrite." For example, consider this manuscript excerpt, in which Whitman has changed the "e" from upper- to lower-case. The markup for this word is:

<app> <rdg varSeq="1">
<del type="overwrite">e</del>
</rdg>
<rdg varSeq="2">
<add type="overwrite" place="over">E</add>
</rdg>
</app>ach

Pasting

Fairly frequently, Whitman made substitutions by pasting one page or scrap over another. Treat such cases as you would other substitutions, by using the app, rdg, del, and add elements. For the type attribute on <del>, use the value "pasteover." The type attribute of the <add> should be given the value "pasteon," and the place attribute should be given the value "over." For an example, look at this manuscript leaf.

. . .
<app><rdg varSeq="1"><del type="pasteover">
<l><seg>And that night O you happy </seg>
<seg>waters, I heard you beating</seg>
<seg>the shores – But my heart</seg>
<seg>beat happier than you – for</seg>
<seg>he I love is returned and </seg>
<seg>sleeping by my side,</seg></l>
<l><seg>And that night in the stillness</seg>
<seg>his face was inclined toward</seg>
<seg> me while the moon's clear</seg>
<seg>beams shone,</seg></l>
<l><seg>And his arm lay lightly over my</seg>
<seg>breast – And that night I</seg>
<seg> was happy.</seg></l>
</del></rdg>
<rdg varSeq="2"><add type="pasteon" place="over">
<l><seg>And that night, while all</seg>
<seg>was still, I heard the</seg>
<seg>waters roll slowly continually</seg>
<seg>up the shores</seg></l>
<l><seg>I heard the hissing rustle of</seg>
<seg>the liquid and sands, as directed</seg>
<seg>to me, whispering, to congratulate</seg>
<seg>me, – For the friend I love lay</seg>
<seg>sleeping by my side,</seg></l>
<l><seg>In the stillness his face was in-</seg>
<seg>clined towards me, while the</seg>
<seg>moon's clear beams shone,</seg></l>
<l><seg>And his arm lay lightly over my</seg>
<seg>breast – And that night I was happy.</seg></l>
</add></rdg></app>
. . .

Nesting Add Tags and Delete Tags

Of course, not all combinations of add tags and delete tags are substitutions. Consider this manuscript excerpt. To indicate that the addition was deleted, the add element should be nested within the del element:

from
<del type="overstrike">
<add type="unmarked" place="supralinear">this</add>
</del>
base

There are a number of other ways in which Whitman combined additions and deletions—probably too many to cover each one separately here. You should be able to handle almost all situations you encounter by applying these principles and rules:

  • Nesting operates on a radial principal, working from the center out. For additions and deletions, this means that when the boundaries of a deletion and an addition are the same, the <add> should be nested within the <del>. This indicates 1) that the material was added; and 2) that the addition itself was deleted. If, however, only part of an addition has been deleted, the <del> will, of course, be nested inside the <add>.
  • <add>s and <del>s, in various combinations, can be nested within one another, with no theoretical limit to the "depth" of that nesting. So it's entirely possible to have, for example, a <del> within an <add> within an <add> within a <del>.
  • <app>s, however, should never be nested inside other <app>s, even though you will occasionally encounter situations which seem to call for such markup. Because <app>s within <app>s would create difficulties for computer processing, our project policy is to mark only the "highest level" substitution as such and to mark interior substitutions only with <add> and <del>, as appropriate.
  • All <add>s and <del>s must nest properly within any other elements that are present. In particular, you should be careful not to straddle line or line segment boundaries.

To understand how to approach a complicated series of additions and deletions, take a look at this manuscript line segment. Note that it shows two substitutions: the word "for" replaces "to," and the phrase "time's hourly ceaseless" replaces "the varied." The fact that "hourly" and "ceaseless" have then been deleted adds a further complication. This is how the segment should be encoded:

<seg>No more
<app>
<rdg varSeq="1">
<del type="overstrike">to</del>br> </rdg>
<rdg varSeq="2">
<add type="unmarked" place="supralinear"> for</add>
</rdg>
</app>
him
<app>
<rdg varSeq="1">
<del type="overstrike">the varied,</del>
</rdg>
<rdg varSeq="2">
<add type="insertion" place="supralinear">
time's
<del type="overstrike">hourly ceaseless</del>
</add>
</rdg>
</app>
mightiest,</seg>

Illegible or Missing Text

<gap>: for completely unreadable text

<gap>: This element is used when text is absolutely unreadable—when, for example, it has been torn or cut away, is obscured by deletion, or is simply illegibly written. Each <gap> needs a reason attribute, and you have the choice of two values: "cut away" or "illegible." Note: gap is an empty element (i.e, does not require a close tag).

  • <gap reason="cut away"/>: When a page has been torn or cut, leaving only tantalizing stubs of the letters you want to transcribe, as in this example, use this tag at the point in the transcription where the words would appear.
  • <gap reason="illegible"/>: Use this markup whenever the letters or words are present but unreadable. In cases where they have been overstruck, put this tag inside <del rend="overstrike">. For an example of this sort of circumstance, click here. Use this element/attribute combination also, but without the containing <del>, when characters on the page are not deleted but nevertheless impossible to decipher (as in this example, where the characters preceding the question marks cannot be resolved).

<supplied>: for text that is currently unreadable, but that has been supplied by another source

<supplied>: Sometimes a secondary source can supply a reliable transcription of text that is at present illegible, as for example when a transcription was done by an institution or editor before damage occurred. The supplied element is used in such situations. Enclose that part of the text that has been supplied in the supplied element, and use the reason attribute values listed for <gap> above to state the cause of the loss of text. Also insert a source attribute with a value that notes your source for the supplied text. For example, this excerpt is from our transcription of "Ashes of Roses":

<p>
Are we to have a National Hy
<supplied reason="cut away" source="Library of Congress transcription">
mn by
<orig reg="Centennial">Cen-<orig>
</supplied>
tennial time?
</p>

<unclear>: for text illegible enough to render your transcription questionable

<unclear>: When you believe you have an accurate reading of a difficult-to-read passage, but you are not completely confident, mark the questionable reading with the unclear element. Use the reason attribute to state the cause of the uncertainty in transcription, selecting from the values described above under <gap>. Use the cert (certainty) attribute to indicate the degree of confidence in the transcription. Its value will be a numeric percentage (e.g., "95%"). Also include a resp (responsibility) attribute to indicate your responsibility for the postulated reading, and as its value use your initials.

For example, if Andy Jewell is encoding a manuscript with an unclear deleted word that he thinks might be "herbage," he inserts this markup:

<unclear reason="deletion, illegible" cert="70%" resp="awj">herbage</unclear>

Remember, when the value of a "resp" attribute indicates a hand other than Whitman's, a note must be included in the <profileDesc> within the Header.

Hyphenation and Non-Standard Spelling

Segments with end-hyphenation

Because we wish both to record the lineation of the copy text and to enable searches for words that are broken by end-line hyphenation, we use the <orig> tag with the reg attribute to record the original and regularized readings. Tag such instances in the following way:

<l>
<seg> . . . and the dying <orig reg="emerging">emerg-</orig></seg>
<seg>ing from gates,</seg>
</l>

Non-Standard Spelling

The sic element is used to represent a mistake by the author. The required attribute corr provides a correction. These corrections will enable searches to use standardized spelling and not require the searcher to know, for example, that Whitman misspelled "Buildings" as "Buldings" in this manuscript. This word should be marked up in this way:

<sic corr="Buildings">Buldings</sic>

Sometimes what you might think of as a spelling error would more accurately be termed an alternate spelling. For words that are spelled in idiosyncratic—though not exactly incorrect—ways, use the orig tag and its required reg attribute. This element and attribute pair works in the same way as sic and corr; that is, Whitman's spelling is transcribed and the standardized spelling is recorded as the value of the reg attribute. As an example, look at Whitman's spelling of "Shakespeare" in this image. Since this spelling of Shakespeare's name is one he himself used (and he never, as far as we know, used "Shakespeare"), it should be encoded as follows:

<orig reg="Shakespeare">Shakspere</orig>

Unusual Characters & Marks

XML supports only the ASCII character set, which roughly corresponds with the set of characters on a standard keyboard. Not all of the characters you might encounter in a Whitman manuscript are part of the ASCII character set, so to represent one of these unsupported characters you will need to use the appropriate Unicode number—a string of numerals that begins with an ampersand and pound sign (&#) and ends with a semicolon (;).

The table below lists the Unicode numbers we are using on the project. It is important to use the numbers for the listed characters, even when it might be possible to key them in (as with the ampersand, for example) or to use a close approximation (e.g., two hyphens to represent an em-dash). For characters not listed, Unicode numbers are NOT necessary.

For the characters in the left-hand column to display correctly, you must have a Unicode font installed on your computer.

Common Characters
Character Function in Whitman Unicode Number
= Proofreader's mark for hyphen. WW sometimes uses "=" for compound words ("down=balls") and words split between two lines ("some=thing"). &#8209;
Em (long) dash e.g., "Not these—O none of these more" &#8212;
* An asterisk &#42;
& Indicates 'and' &#38;
© Copyright symbol &#169;
Checkmark &#10003;
½ Used often in Bowers's system of page numbering &#189;
¾ Used to indicate the fraction, occasionally on manuscripts &#190;
Indicates a new paragraph or a new line of poetry &#182;
ñ Spanish-language character, n with tilde &#241;
ó An "o" with an acute accent mark (to capitalize, change to &#211;) &#243;
é An "e" with an acute accent mark (to capitalize, change to &#201;) &#233;
è An "e" with a grave accent mark (to capitalize, change to &#200;) &#232;
File:RightPointing.gif A right-pointing finger &#9758;
File:LeftPointing.gif A left-pointing finger &#9756;
File:UpPointing.gif An up-pointing finger &#9757;
File:DownPointing.gif A down-pointing finger &#9759;

Graphically Distinctive Text

Underlined words: Underlined words require the "rend" attribute with the "underline" value. The "rend" attribute is global (can be used on any element), but typically you will use it with a <head> element, the <signed> element, or, if the underlined words are in the middle of a line, the <hi> element. However, if an entire line or linegroup is underlined, the element can be used on <l> or <lg>. For example, in this manuscript the underlined words in the first line would be encoded like this: <hi rend="underline">the necessity of</hi>

Dotted-underlined words: Occasionally, you may encounter a manuscript with a word that has been deleted and underlined with a series of dots. This is a printer's mark for "I don't want to delete this word after all; please leave it in," or, "stet." To handle these instances, which are rare, we surround the dotted-underlined word and the <del> with the <restore> element and use the "rend" attribute. For example, in this manuscript the dotted-underlined words are encoded like this:

<app>
<rdg varSeq="1">
<del type="overstrike">baleful</del>
</rdg>
<rdg varSeq="2"> <add place="supralinear" type="unmarked">
<restore rend="dotted"><del type="overstrike">mortal</del></restore>
</add>
</rdg>
</app> coals,

Line indentation: Though in most cases Whitman begins lines at the left edge of the writing space, he sometimes uses line indentation in distinctive ways, as in this copy of "O Captain! My Captain!" To encode this indentation, we add the "rend" attribute to the <l> element. The value of "rend" is "indented" plus a number that indicates the relative length of the indentation. For the shortest indentation, we use "indented1"; for the longest, "indented4."

Reference Chart for Use of the "Rend" Attribute
Value of 'rend' attribute Function in Whitman
underline Indicates underscored text
circled used when text, typically within a note in the margin, is surrounded by a circular line in order to separate it from other text
bracketed used in <title> within the <titleStmt> to distinguish derived titles
italic used only in transcriptions of printed material or in project notes to mark titles of books.
dotted used with <restore>
indented1 indented2 indented3 indented4 added to <l> when Whitman uses staggered indentation at the beginnings of lines; the numbers indicate relative amount of indentation (1=shortest, 4=longest)
horbar-full; horbar-short-right; horbar-short-left; horbar-short-center used in <milestone> to indicate various positions and lengths of horizontal separators

Signatures & Dates

Bylines

Bylines that immediately follow the title should be encoded using the byline element. Insert it after the head element and before the first <l>. The byline shown here is encoded as follows:

. . .
<head type="main-authorial" rend="underline">Up, lurid stars!</head>
<byline><hi rend="underline">By Walt Whitman</hi></byline>
<l>Up, lurid stars! martial constellation!</l>
. . .

Signatures at the Bottom

A signature that comes after the last line should be marked with the signed element. In order to properly unite the signature with the poem being signed, <signed> is included within <closer>. The <closer> ought to close before <lg1> closes.

The following example is based on this manuscript. . . .

<seg><add type="insertion" place="supralinear">scented</add> roses blooming.</seg>
</l>
<closer>
<signed rend="underline">Walt Whitman</signed>
</closer>
</lg1>
</body>
</text>
</TEI.2>

Dated Manuscripts

A date which Whitman has written on a manuscript in order to note the composition date or occasion date (as when he writes on Washington's birthday or on the death of General Sheridan) is encoded within the <dateline> tag. <dateline> can occur wherever Whitman has written the date, typically either after the <head> or within the <closer> after the signature.

Each time you use a <dateline> tag, you also need to use the <date> tag with the value attribute. The <date> element should contain only the date. The value of value is the normalized date, put into this form: YYYY-MM-DD. If, as in the example below, you need to encode a date range, the value attribute will have both dates, separated by a slash.

The following example is based on this manuscript.

. . .
<lg1 type="poem">
<head type="main-authorial" rend="underline">The Sobbing of the Bells—</head>
<dateline>(Midnight <date value="1881-09-19/1881-09-20">Sept: 19-20 1881</date>)—</dateline>
<milestone unit="undeclared" rend="horbar"/>
<l><seg>The sobbing of the bells, the sudden death‑news</seg>
<seg>everywhere</seg></l>
. . .

When is a date a <dateline> and when is it a <note>? We use the <dateline> element to note a date that is to be published with the poem and is part of the poem's meaning. As mentioned above, Whitman most often inserted these sorts of dates under the head or under his signature. On other manuscripts, Whitman has written a date that is not a <dateline> but instead is to be treated as a <note> (see 4.1.1) on the page. Most of the time, these <note>s will be distinguished by their placement on the manuscript page (in a margin, a corner, or otherwise beyond the layout of the poem proper) and by their ambiguous relationship to the lines of poetry.

Additional Local Encoding Guidelines

Other Writings in Whitman's Hand

Notes

You will sometimes come across writing on the manuscript page that is not part of the text of the poetry manuscript proper, but instead a note of some sort about it. For example, this note follows a poem, at the bottom of the page. This sort of material is encoded using the <note> element. Note also takes two required attributes: type and place. To distinguish the writing as Whitman's, use the value "authorial" for the type attribute. For the place attribute choose from the following values: "margintop," "marginbot," "marginleft," "marginright," "inline," "supralinear," or "interlinear."

The example should be marked up as follows:

<note type="authorial" place="marginbot">
<app>
<rdg varSeq="1">
<del type="overstrike">sent to</del>
</rdg>
<rdg varSeq="2">
<add type="unmarked" place="supralinear">pub in</add>
</rdg>
</app>
Herald early in Feb. '88
</note>

Sometimes, Whitman will visually separate his notes from the rest of the text by drawing a boundary line, as in this example. When this happens, you need to add the rend="circled" attribute and value to <note>. (The value circled is used even though Whitman's boundary line often does not make a proper geometric "circle"). The encoding for the example would read:

<note type="authorial" place="margintop" rend="circled">follow copy strictly</note>

Note that <p> is only used within <note> when there are multiple paragraphs within the note.

Reverse-Side Notes

Occasionally, Whitman will write a prose note about the poem on the reverse-side of the manuscript leaf, such as a note to the printer or a comment on the poem's placement in a larger work. These notes, though they are on the reverse side, are encoded basically the same way as the notes described above are encoded, with a few minor adjustments:

  • The <note> tag is inserted after the <pb> tag that identifies the verso (i.e., the one with "id='leaf01v'")
  • The value of the place attribute is "inline"

Unrelated Reverse-Side Writing

If reverse-side writing is in Whitman's hand, we encode it, regardless of its content. You will need to create a new <head> and, therefore, a second <title> in the <titleStmt> to deal with the separate intellectual unit on the reverse-side. It should be encoded to the same level as any other Whitman manuscript.

Miscellaneous Writing

The note element is also used to mark other writing on the page that, while not strictly a note, is not part of the text. Examples include: page numbers, addition or subtraction problems, and question marks.

Whitman's use of proofreading/typesetting marks is a special case. To encode a manuscript that has such marks, you should first decide whether the marks are being used to indicate a) changes to the base text, or b) emphasis of a typographic feature.

It is our current policy to encode only marks of the first type. Examples include the caret ( ^ ) to indicate an addition, and the paragraph mark (¶) to indicate a new paragraph (in prose) or line (in verse). For instructions on encoding the caret, see 3.3 Additions. The paragraph mark should be encoded as a named character entity(see chart 3.7)—¶.

At present we have chosen not to encode marks of the second type, though we may in a future stage of the project return and add representions of them to our markup. Examples of marks that you should not encode include triple-underlining to emphasize capitalization and horizontal curved brackets used to indicate lack of spacing between parts of hyphenated words.

Horizontal Lines

Whitman fairly often draws a line to signal the beginning or the end of a unit of text. These lines range from full page width to small bars at the left, right, or in the center. You can see an example of a small center line at the bottom of this manuscript and an example of a small line at the left at the top of this one. We take these lines to indicate some kind of division, though we make no claims about the sort of unit(s) they define. They are encoded using the empty milestone element, with "undeclared" as the value of the unit attribute and the following as possible values of the rend attribute:

  • horbar-full
  • horbar-short-right
  • horbar-short-left
  • horbar-short-center

The first example above should be encoded as follows:


<seg>We never separate again.—</seg></l>
<milestone unit="undeclared" rend="horbar-short-center"/>
</lg1>

Brackets

Whitman sometimes used brackets to group lines or other bits of text, as in this example. These should be indicated by using the span element. Like <addSpan> and <delSpan>, is an empty element (i.e., consists of a single open tag), but it works in a slightly different way. In addition to the to attribute, from and value are also required. Assign the span an id—use the formula s+number—and give the "from" the same id. This, in essence, means "start from here.") The value of the value attribute will always be "bracketed." And, as with addSpan and delSpan, you must always mark the end of the bracketed section with an empty anchor element bearing an id attribute whose value corresponds with the value of the 's to attribute. This is the markup for the example above:

<span value="bracketed" id="s1" from="s1" to="s2"/>
<l>I rate myself high—I receive no small sums;</l>
<l>I must have my full price—whoever enjoys me.</l>
<anchor id="s2"/>

Page Numbers

Whitman's use of page numbers—combined with the history of manuscript dispersal—means we are left with both ambiguous and reliable page numbering on Whitman manuscripts. By "ambiguous," we mean manuscripts with a number, like "43," written in the top corner but no corresponding "42" or "44"; by "reliable," we mean multiple-leaf manuscripts with an ordered numbering of each leaf (ordered numbering does not mean an uninterrupted sequence that begins with "1"; instead, it means any discernable numbering system that reliably determines the leaf order).

We handle these two types of page numbers in different ways. For ambiguous numbers, we use <note>. For reliable page numbering, we add an attribute to the Page Break, or <pb> element. Specifically, we add an "n" attribute with a value that corresponds to the number written on the page. So, if a three-leaf manuscript is numbered "2," "3," "4," then the <pb>s would have n="2", n="3", and n="4".

Section Numbers

Sometimes you will encounter a manuscript with distinctly numbered sections, as in this example. These sections are different than linegroups, as they are typically numbered or otherwise clearly marked, and they often contain multiple linegroups. To handle section numbers, add a <head> tag immediately after the <lg> tag to note the "head" of that section. Here's how you would encode the example manuscript :


...
<lg1 type="poem">
<head ... >
<lg2 type="section">
<head type="main-authorial">1</head>
<lg3 type="linegroup">
<l>Come, said the Muse,</l>
....
</lg3>
<lg3 type="linegroup">
...
</lg3>
<lg3 type="linegroup">
</lg3>
</lg2>
<lg2 type="section">
<head type="main-authorial">2</head>
...
</lg2>
...
</lg1>

Intentional Inline Spaces

Whitman will occasionally leave a blank space within a line of poetry, apparently making room for the perfect word that he has yet to discover. To encode these spaces, insert a <space> element with two attributes, dim (dimension), the value of which will almost always be "horizontal"; and extent, the value of which is expressed as a number of letters, determined by the size of the letters surrounding the space on the manuscript. The encoding for this manuscript would look like this:

action, <space dim="horizontal" extent="9 letters"/>in husky


In other cases, Whitman will leave a blank line that indicates the intentional blank space (apparently in addition to his major poetic innovations, Whitman also developed the Mad Lib). To encode this phenomenon, use the same strategy as above, but add a "rend" attribute with the value "underline." Therefore, this example would be tagged like this:

. . . .
<seg>As in Visions of <space dim="horizontal" extent="7 letters" rend="underline"/> at</seg>
<seg>night—</seg>

Writing in Others' Hands

Writing on the Front of the Leaf

Use the note element to mark letters, words, etc. that someone other than Whitman has written on the manuscript page you are encoding. As explained in section 3.9 above, this element requires both type and place attributes. For the value of type use "editorial." The possible values of the place attribute are the same as for other notes: "margintop," "marginbot," "marginleft," "marginright," or "interlinear." In addition, non-authorial notes should be given a resp attribute, with a two- or three-letter code to identify the responsible hand. Hands to which codes have been assigned are listed in the following table. Should you encounter a hand not accounted for, please email Brett Barney and Andy Jewell.

Name Primary Location of mss Code
Bowers, Fredson UVa fb
Traubel, Horace Library of Congress, Feinberg Collection ht
unknown n/a unk

This note, written by Traubel in the bottom right corner of a poem manuscript, is encoded as follows:

<note type="editorial" resp="ht" place="marginright">
For Francis Howard Williams May 1896 Traubel
</note>

Resp Values Any time the resp attribute is used (whether on <note> or on <unclear>, etc.) in the body of a document, you must also include in the header some information that explains each of the values you've used. To do this, add a profileDesc (profile description) element directly before the <revisionDesc> (revision description). Inside the <profileDesc>, create a pair of handList tags and one hand element for each different value given to a resp attribute in the file. hand has two required attributes: scribe and id. The value of scribe is the full name of the person being identified as responsible for the written note. The value of id corresponds with the value assigned to the resp attribute in the body. The following excerpt is taken from the file that contains the note discussed above:

<profileDesc>
<handList>
<hand scribe="Horace Traubel" id="ht"/>
</handList>
</profileDesc>
<revisionDesc>
>

Writing on the Back of the Leaf

Most cases of reverse-side writing in others' hands arise from Whitman's re-use of paper. Common examples include envelopes, fan letters, and government stationery. For such situations, we use the note element with the value "project" on the type attribute to describe (not transcribe) the non-authorial writing. Unlike "authorial" and "editorial" <note>s—which should be transcribed as close as possible to their position in the manuscript—these notes must be placed within the <teiHeader>. To do this,


1. insert a <notesStmt> immediately before the opening source description tag (<sourceDesc>);
2. inside the <notesStmt> create a <note> with no place attribute, the value "project" on the type attribute, and the additional attribute target;
3. find the page break that indicates the beginning of the reverse side;
4. copy the value of the page break's id attribute as the target attribute on the project note;
5. write a short description of the reverse-side writing

Note: You need not use <p>s to enclose these project notes, unless you want to write more than one paragraph of description. Here's how the envelope example above should be encoded:

<teiHeader>
<fileDesc>
. . .
<notesStmt>
<note type="project" target="leaf01v">Verso of manuscript leaf is addressed to Walt Whitman, Camden, New Jersey, postmarked September 25, 1890.</note>
</notesStmt>
<sourceDesc>
<bibl>
<author>Walt Whitman</author>
. . .
</teiHeader>
. . .
<pb corresp="loc.00046.001" id="leaf01v" type="verso"/>
. . .

Other Cases

Materials which accompany manuscripts (notes, transcriptions)
For now, we have decided not to transcribe or encode any of the items not written by Whitman—for example, notes about the text or transcriptions—that are sometimes stored with manuscripts. Eventually, these may be encoded as separate documents and linked to the relevant manuscript, but this work will happen at a later time.

Pasted clippings
See section 4.3 below for a discussion of how to encode clippings that Whitman has incorporated into his own manuscripts.

Cutting & Pasting

We distinguish among three sorts of pasting in Whitman's manuscripts. Please look over the description of each and decide which describes the instance you're encoding.

  • One page pastes over another, deleting old material and adding new. (See 3.4, "Additions and Deletions in Combination.")
  • Paper has been pasted together to provide more writing space. (See below.)
  • Whitman pastes a clipping onto his manuscript. (See below.)

Pasting that Extends Writing Area

To represent the seam of the two pages that have been joined, use the (empty) milestone element. Include the unit attribute with the value "glued." This example shows a manuscript that calls for such markup.

Clippings Pasted to the Manuscript

Sometimes Whitman pastes others' material to his manuscripts. For example, in "Ashes of Roses," Whitman has pasted a newspaper clipping in the lower left-hand corner of the first leaf. In these cases, use the <add> element and its available "type" attribute (if a manuscript's peculiarity requires it, as when pasted-on material begins in the middle of an <l> and crosses <l> boundaries, you may also use <addSpan>). In this particular case, the author of the newspaper clipping is "unknown."

<add place="marginbot" hand="unk" type="pasteon">
<p>Are we to have a National Hy<supplied source="Library of Congress transcription">
mn by <orig reg="Centennial">Cen-<orig></supplied> tennial time?</p>
</add>

Please remember that hands other than Whitman's must be declared in the <profileDesc>.

Page Breaks

Page Breaks (<pb>) are inserted in the encoding whenever you begin the transcription of a new page (including the first one). You use <pb> tags in every document, even if they are only one page long. <pb> is an empty tag, which means that you never need to "close" <pb>, but just insert a "/" at the end of the tag.

Each <pb> tag has three required attributes, "corresp," "id," and "type". The "corresp" attribute indicates the file that contains the page image, so you'll need to assign, as its value, the unique id with a three-digit suffix that indicates the page number (.001, .002, etc)—the image files will be given this name before they are mounted on our site. The "id" attribute identifies the page by "leaf" (or piece of paper) number and side—"r" for "recto" (front) or "v" for "verso" (back). The "type" attribute classifies the page as either "recto" or "verso." The "id" value must always end in either "r" or "v"—even if there is only one image. When there is only one image, the "id" value will almost always be "leaf01r."

Here is an example of what the <pb> tag looks like:

<pb corresp="loc.00008.001" id="leaf01r" type="recto"/>
The first <pb> tag goes after the <body> tag and before the first
or <lg>. If there are multiple pages, i.e., more than one corresponding image, simply insert a <pb> at each place in the encoding that corresponds to the beginning of a new page. Often, these will occur at the close of one linegroup (</lg1>) and before the opening of another (<lg1>). Or, commonly, you will need to include a <pb> to indicate untranscribed verso material; this should be done after the <lg> or
closes but before the <body> tag closes.

How to Handle Unusual Document Order: In some instances, Whitman has written a single poem on the rectos of several leaves that also have poetic lines on the verso that are not part of the same poem. In this case, you must encode in a way that preserves the intellectual unity of the poem on the rectos. To do that, you will have to break the typical order of <pb> "id" values. That is, instead of "leaf01r," then "leafo1v," "leaf02r", "leaf02v", etc., encode the pages in an order that preserves the integrity of each poem. For example, if you have a manuscript with a poem written across the rectos of three leaves and other poetic lines written on the versos of leaves 1 and 3, the <pb> will have id attributes ordered like this: leaf01r, leaf02r, leaf03r, leaf01v, leaf03v. It is done this way to ensure that the material on the rectos of leaves 1-3 are all contained within the same <lg1 type="poem">

Remember: For every <pb> you insert, you need to insert an Entity Declaration (section 2.5) in the header.

Encoding Corrected Proofs

Many manuscripts in various collections combine printed text and handwritten correction, as in this example. We have developed a an encoding procedure for these manuscripts that make distinctions between the two types of texts (printed and handwritten).

  • All "mixed media" mss of the kind described are assigned "prepub-proof" or "postpub-proof" as the value of the type attribute in the <text> element. Pre-publication proofs are the most common: typically, they are detatched sheets of paper with a typescript rendering of a poem. Post-publication proofs are what we are calling Whitman's hand-revised copies of published works. So, for example, if a copy of the 1876 edition of Leaves served, after being annotated, as the printer's copy for the 1881-1882 edition, we would call that a post-pub proof. Note that we are using the word "proof," in a way that is broader than is usual in the publishing world, to describe the proof-like functioning of a document.
  • The base text for these manuscripts is assumed to be printed, so we explicitly declare the medium of only the <add>s, <del>s, and <note>s.
  • We use the hand attribute on <add>, <del>, and <note> to record non-handwritten bits (that is, when Whitman cut text from a different printed source and pasted it in the first printed text). We assume that all <add>s, <del>s, and <note>s without a "hand" attribute in a "postpub-proof" are handwritten.
  • The handwritten "hand" is declared in the <teiHeader>'s <profileDesc> in the same way that we're already doing it for non-Whitman writing on mss. (E.g., when we have <note type="editorial" resp="ht" place="marginright"> for one of Traubel's ms. annotations, the <profileDesc> has <hand scribe="Horace Traubel" id="ht">). But instead of putting the elaborated description in the scribe attribute, we put it in an "ink" attribute.
  • Consonant with our practice of letting pass distinctions between colors of ink or between ink and pencil, all non-handwritten bits will share the same value for the hand attribute.
  • Whitman often changes the proof inline and also adds a marginal note, as when he adds a comma inline and puts "<," in the margin. In these cases, do not double-encode his corrections. Marking the addition inline is sufficient.

When Whitman notes the insertion of space with a "#", use <add> with the <space> element, noting whether or not it is vertical or horizontal space (in proofs it will most often be vertical), and noting the approximate size of the space, using "lines" as the measuring unit (relative to surrounding line-heights). An example would be: <space dim="vertical" extent="1 line"/>

  • When Whitman uses a curled line to correct inverted letters or words, use the <transpose> element to note his re-ordering. For example, if you see File:Beard.JPG in a corrected proof, you would encode it this way:
b<anchor id="t1"/>a<transpose hand="h1" anchored="yes" target="t1">e</transpose>rd

Whitman will often use specialized proofreading marks to note common changes, as when he uses a triple-underline to note his desire to capitalize an uncaptalized word. In these cases, you encode using an <app> structure and "edit" as the value of the type attribute on <add> and <del>. For example, if you saw File:Life lumps.JPG, you would encode it like this:

<app><rdg varSeq="1"><del type="edit">l</del></rdg><rdg varSeq="2"><add type="edit">L</add></rdg></app>


We use a controlled vocabulary for both the value of the hand attribute on <add>, <del&gt, and <note>, and for the ink attribute on <hand>: ink="handwritten"; hand="h1". An example follows.

<profileDesc>
<handList>
<hand id="h1" ink="handwritten"/>
</handList>
</profileDesc>
. . .
<text type="prepub-proof">
<body>
. . .
<add type="insertion" place="supralinear" hand="h1"> . . .</add>
. . .
</body>
. . .

Encoding Prose

Even though we are focusing on Whitman's poetry, the manuscripts will sometimes contain prose that you will need to represent. You might encounter prose in Whitman's poetry manuscripts in a few different ways:

  • Prose notes about the verse on the same leaf:

Sometimes Whitman will have lines of prose on the same leaf that he has used for poetic composition. This is ususally deemed a mixed genre manuscript and requires the "poem notes" value for the <div1> type attribute. Occasionally, though, the prose will be a note about the poem. In that instance, consult the section in the guidelines about authorial notes (section 4.1).

  • Prose with imagery or language that was later incorporated into a poem, or prose notes about an idea for a poem:

For prose writings that relate to poetic work, you will simply encode the manuscript as a prose only document (section 2.3).

  • Prose unrelated to the poetic lines on the leaf:

Prose unrelated to the verse on the leaf, which almost always is on the verso of the manuscript, is discussed in the Unrelated Reverse-Side Writing section 4.1 of the guidelines.

Transcribed prose is always encoded in the same way: the text is surrounded by <p> tags and all line breaks and line segments are ignored.

Encoding Lists

Whitman sometimes made lists of words or phrases that led, in one way or another, to his poems; for example, this list has been traced to Whitman's poem "When Lilacs Last in the Dooryard Bloom'd."

To encode these lists, we use the <list> element, which contains the <item> element. The structure is pretty straightfoward: at the beginning of the list, open the <list> element; then, if appropriate, insert a <head> tag; finally, encode each item on the list with an <item> tag, which is nested within <list>. The following sample encoding is based upon the manuscript example above:

. . .
<list>
<item>sorrow (saxon)</item>
<item>grieve</item>
<item>sad</item>
<item>mourn (sax)</item>
. . .
</list>

Manuscripts That Are Neither Poetry Nor Prose

Encoding Lines that are Neither Verse nor Prose

Occasionally, you will run across a manuscript with lines that appear to have all the layout qualities of verse (hanging indentation, initial capitalization, etc.) but otherwise seem like prose notes about an idea for a poem (for an example, click here). Rather than imprecisely calling such manuscripts either "prose" or "verse," we have developed a method that acknowledges the indeterminacy of the genre. Specifically, we use the "anonymous block," or <ab> element in place of either <l> or <p> and mark line segments. Also, the <div1> type is the same we use for "mixed genre" manuscripts, "poem notes." Here's an example of how the encoding would look (click here to look at the manuscript):

<-- markup is simplified -->
<text type="manuscript">
<body>
<div1 type="poem notes">
<head type="main-authorial">incidents for (Soldier in the Ranks)</head>
<milestone unit="undeclared" rend="horbar"/>
<ab>
<seg>describe a group of men coming off the</seg>
<seg>field after a heavy battle, the grime,</seg>
[. . .]
</ab>

IMPORTANT: We don't want to use this tagging indiscriminately; it should only be used when the editors cannot decide if material is prose or poetry. Therefore, if you come across a manuscript that you think fits the description above, please consult with either Ken or Ed before you use the <ab> markup.

Encoding Title Pages

If you encounter a manuscript that has only titles on it, like this one, please use this variation on the <ab> tagging described above (note the different <div1> type and attributes for the <ab> elements):

<-- markup is simplified -->
<text type="manuscript">
<body>
<div1 type="title notes">
<ab type="title" rend="underline">American to Old-World Bards</ab>
<ab type="subtitle" rend="underline">A reminiscence from reading Walter Scott</ab>
</div1>


NOTE: Only use "rend='underline'" if the title is indeed underlined as it is in this example. Otherwise, omit that attribute.

Enigmas

What Not to Encode

Although we are attempting to accurately encode all of the important aspects of Whitman's texts, absolute comprehensiveness is not our goal. Specifically, we have decided, for now at least, to ignore

  • ink blots, smudges, and stray pen marks;
  • pin holes;
  • embossing;
  • variations in ink, pencil, or paper;
  • distinctions between single and multiple overstrikes

Things Not Covered by the Guidelines

The encoding practices articulated in these guidelines have evolved over the last several years, and that evolution has mainly been driven by the needs of encoders, editors, programmers, and consultants as we have worked to create and deliver electronic transcriptions of individual manuscripts. When we first began, every manuscript presented a host of new challenges that had to be addresssed before the encoding could be completed. Naturally, the pace of change has slowed as the number of encoded manuscripts has grown. Even so, new puzzles continue to present themselves occasionally, and you should not be unduly disturbed if you find yourself in an encoding dilemma for which the guidelines seem to give no guidance. In such cases, you should write or call Brett Barney or Andy Jewell as soon as possible and explain as clearly as you can the nature of the difficulty. If the problem is indeed new, you may be asked to draft a summary of the issues to be sent to the members of the listserv.

Dealing with Uncertainty

Encoding manuscript materials is difficult for a number of reasons, and you will no doubt sometimes feel confused or indecisive. If the difficulty is one of reading or interpreting, consult with Ed Folsom or Kenneth Price. If, instead, the problem has to do with markup, consult with Brett Barney or Andy Jewell.

If the problem is relatively minor, in that it doesn't prevent your continuing to work on other parts or aspects of the manuscript, you might decide to handle the problem in the best way you know how and leave yourself and the editors a detailed comment—in the file itself—about the problem and how you've handled it. Then you and they can return to it later. Do this by writing the comment and then surrounding it with these characters:

<!--                  -->

This sequence of characters signals the computer's SGML processor to ignore everything that comes between the first and last marks.

Alternatively, you can write your comment and wrap it in a <what> element. This is an element we have borrowed from the Brown Women Writers Project, and it can be used in essentially the same way as the "commenting out" convention explained above.

Work Relationships and Date Information

*this encoding is typically inserted by upper-level staff people and editors As part of the header, we encode the relationship of the individual manuscript to a "work" (or "works"). As opposed to a document, which is a particular instatiation of a poem or book, etc., a "work" is the abstract idea of a poem or book, etc. We name the work according to the last instance published in Whitman's lifetime. For example, the work "Song of Myself" refers not to any particular manuscript or printed version of that poem, but to all of the versions collectively. Individual documents of that work include: the poem printed in the "deathbed edition," titled "Song of Myself"; the first, untitled version of the poem in the 1855 edition of Leaves of Grass; manuscript drafts of lines included in the poem; and notebooks that contain ideas and trial phrases that contributed to the composition of the poem.

We encode this work relationship at the beginning of the transcription file, immediately before the <teiHeader> element. The following example is taken from the transcription of this manuscript):

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE TEI.2 PUBLIC "-//UVA::IATH//DTD whitman.dtd (Whitman Archive)//EN" "whitman.dtd" [
<!ENTITY loc.00213.001 SYSTEM "loc.00213.001.jpg" NDATA jpeg>
<!ENTITY xxx.00358 SYSTEM "xxx.00358.xml" NDATA xml>]>
<TEI.2 id="loc.00213" type="doc">
<relations>
<work entity="xxx.00358" cert="high">
<p>This manuscript is a draft of "Life and Death," which was published first in the New York
<hi rend="italic">Herald</hi>, <date value="1888-05-23">May 23, 1888</date>.
</p>
</work>
</relations>
<teiHeader>
. . .

To encode the work relationships, we must first look up the work ID. A table of work IDs can be found here in the reference section of the Encoding Guidlines. The ID, which is a string of characters beginning "xxx" and ending with a five-digit number, corresponds to a work file which will contain prose descriptions of the compositional history of the work as well as connect the transcription files with other elements of the Whitman Archive. The ID is inserted two places: in the entity declaration and as the value of the "entity" attribute in the "work" element.

In addition to this ID, project editors also assign either "high" or "low" as the value of "cert" to describe their confidence in connecting the individual manuscript to the work. For a manuscript with lines that are identical or very close to a published poem, the certainty will be "high"; notes that describe an idea in a way that bears a general resemblence to a published poem will get a "low" certainty.

The final part of the <relations> section is a brief prose description of the publication history of the work. This editorial note will be displayed along with the transcription on the site. If there is something distinctive and noteworthy about the manuscript, the editor may also insert a project note within the <noteStmt>.

A new <work> element, with a prose description, is used for every work related to the document. All dates within the prose description are tagged with a <date> element with a "value" attribute that records the date in the form YYYY-MM-DD, (or, if appropriate, just YYYY). Any titles that are normally italicized need to be marked with <hi rend="italic">

Dating the Manuscript

We have recently begun inserting information in the transcription files that will allow us both to sort manuscripts by composition date and to provide users with a note about that date. Here is an example, taken from the same manuscript transcription as the sample above:

. . .
<notesStmt>
<note type="project" target="dat1">This manuscript was probably composed in the spring of
<date value="1888">1888</date> shortly before it was published.
</note>
</notesStmt>
<sourceDesc>
<bibl>
<author>Walt Whitman</author>
<title>Life and Death</title>
<date certainty="high" value="1888" id="dat1">1888.</date>
<orgName>The Charles E. Feinberg Collection of the Papers of Walt Whitman, 1839-1919,
Library of Congress, Washington, D.C.
</orgName>
<note type="project">Transcribed from our own digital image of original manuscript.</note>
</bibl>
. . .

There are two major steps to inserting the dating information. The first is the insertion of the <date> element within <bibl>. Within this element we insert either the year of composition ("1888"), the year plus qualifying language ("About 1888"), a date range ("1867-1888"), or whatever brief description of the date is appropriate. (We have decided to only list the year in this space, even when month and day information is available.) The <date> element takes three required attributes: "certainty," "value," and "id." The value of "certainty" can be low (when we only have a conjectural date to offer), high (when we are fairly certain about the composition date), or absolute (when Whitman dated the manuscript or there is some other very conclusive evidence of its composition date). The value of "value" is a regularized date, written as "YYYY" or, in the case of a range, "YYYY/YYYY" (the first year represents the earliest year in the range; the second year represents the latest year). The value of "id" is always "dat1."

The second step is to insert a prose note within the <noteStmt> that describes the reasoning behind our dating of the manuscript. This <note> takes two attributes: "type='project'" and "target='dat1'" (required). The "target" attribute allows us to associate the dating information with the <date> in the <sourceDesc>. The prose note will display below the transcription, giving users fuller information about when Whitman wrote the manuscript.

Templates

The template will help you complete the consistent components of the encoded poetry manuscript, primarily the header. Though no template can exist that will provide all the necessary elements, we hope this file will help with important and complex parts of the encoding.


Using the Template

After you download the template file and open it in NoteTab or other software, you will see a document with tags, many of which require you to insert content. To help you visually identify the areas that require information, and to help explain the information that is needed, a convention called "commenting out" is used. To "comment" something out means to make the computer ignore it; in other words, it is a way to insert words that are to be read only by humans. A "commented out" section is contained within this structure: . Whenever that string of characters surrounds text, what it contains is not machine-readable. For example, if you are looking at an SGML file and you see "", you know that the words are meant for others on the project, not the computer.

Though the template is a helpful tool, avoid getting too dependent on it. The varying nature of Whitman's manuscripts means that no template will accomodate all the possible distinctions. You must consult the rest of the guidelines to make sure you encode all the necessary individual attributes of the specific manuscript you are working on.

To help you make sense of the template, we have created an Annotated Template as part of the Encoding Guidelines. This should help you both to understand why you are doing what you are doing and how to "fill in" the correct content in the template.

Staying Current

Though we don't anticipate needing to update the template too often, as discussions about best practices continue, we will undoubtedly alter our procedures in some fashion. To make sure that you are following the most up-to-date procedures, please ensure you have the most up-to-date template.

The date at the bottom of the page will let you know when the template was updated last, and we will send a email to the Whitman Archive listserv to alert everyone to the existence of the update.

The Annotated Template

In the following template, the asterisks ("******") denote places where encoders must fill in pertinent information. For further line-by-line explaination, please see Explaination of Annotated Template

><?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE tei.2 PUBLIC "-//UVA::IATH//DTD whitman.dtd (Whitman Archive)//EN" "whitmanXML.dtd"[
<!--ArborText, Inc., 1988-2000, v.4002-->
<!ENTITY ***.*****.*** SYSTEM "***.*****.***.jpg" NDATA jpeg>
]>
<TEI.2 id="***.*****" type="doc">
<relations></relations>
<teiHeader>
<fileDesc>
<titleStmt>
<title level="m" type="main">***********</title>
<title level="m" type="sub">a machine readable transcription</title>
<author>Walt Whitman</author>
<editor>Kenneth M. Price</editor>
<editor>Ed Folsom</editor>
<respStmt>
<resp>Transcription and encoding</resp>
<name>The Walt Whitman Archive Staff</name>
</respStmt>
<sponsor>The Institute for Advanced Technology in the Humanities</sponsor>
<sponsor>University of Iowa</sponsor>
<sponsor>University of Nebraska-Lincoln</sponsor>
<funder>The National Endowment for the Humanities</funder>
<funder>The United States Department of Education</funder>
</titleStmt><editionStmt>
<edition><date>2003</date></edition>
</editionStmt><publicationStmt>
<idno>***.*****</idno>
<distributor>The Walt Whitman Archive</distributor>
<address>
<addrLine>The Institute for Advanced Technology in the Humanities</addrLine>
<addrLine>Alderman Library</addrLine>
<addrLine>University of Virginia</addrLine>
<addrLine>P.O. Box 400115</addrLine>
<addrLine>Charlottesville, VA 22904-4115</addrLine>
<addrLine>whitman@jefferson.village.virginia.edu</addrLine>
</address>
<availability>
<p>Copyright © 2003 by Ed Folsom and Kenneth M. Price, all rights reserved. Items in the Archive may be shared in accordance with the Fair Use provisions of U.S. copyright law. Redistribution or republication on other terms, in any medium, requires express written consent from the editors and advance notification of the publisher, The Institute for Advanced Technology in the Humanities. Permission to reproduce the graphic images in this archive has been granted by the owners of the originals for this publication only.</p>
</availability>
</publicationStmt>
<sourceDesc>
<bibl>
<author> Walt Whitman </author>
<title>**************</title>
<orgName>******************</orgName>
<note type="project">Transcribed from our own digital image of original manuscript.</note>
</bibl>
</sourceDesc>
</fileDesc>
<profileDesc>
<handList>
<hand scribe="Fredson Bowers" id="fb">
</handList>
</profileDesc>
<revisionDesc>
<change>
<date>2002-xx-xx</date>
<respStmt>
<name>YOUR NAME HERE</name>
</respStmt>
<item>Encoded</item>
</change>
<change>
<date>2003-xx-xx</date>
<respStmt>
<name>YOUR NAME HERE</name>
</respStmt>
<item>Transcribed</item>
</change>
</revisionDesc>
</teiHeader>
<text type="manuscript">
<body>
<pb corresp="***.*****.***" id="leaf01r" type="recto"/>
<lg1 type="poem">
<head type="main-authorial" rend="underline">************</head>
<l> </l>
<l>
<seg> </seg>
<seg> </seg>
</l>
</lg1>
</body>
</text>
</TEI.2>

Explanation of Annotated Template

This section provides a line-by-line explaination of the annotated template.

  • ><?xml version="1.0" encoding="utf-8"?><!DOCTYPE tei.2 PUBLIC "-//UVA::IATH//DTD whitman.dtd (Whitman Archive)//EN" "whitmanXML.dtd"[ <!--ArborText, Inc., 1988-2000, v.4002-->

These lines of tagging appear at the top of every document we create and point to the DTD that the Whitman Archive uses

  • <!ENTITY ***.*****.*** SYSTEM "***.*****.***.jpg" NDATA jpeg>

This is the "Entity Declaration" and the file needs one of these lines for each page image of the manuscript. Replace the asterisks with a unique id plus a three-digit number for each image.

  • <TEI.2 id="***.*****" type="doc">

The <TEI.2> tag is basic to the structure of a document marked up with the TEI standard and carries the unique id that helps the Whitman Archive keep track of the thousands of documents being created. You'll need to insert a unique id to replace the asterisks.

  • <relations></relations>

Relations tagging is an innovative effort to encode relationships among Whitman's texts. Though we will institute procedures for this soon, we only insert these tags currently to hold the place for future markup.

  • <teiHeader><fileDesc>

These two tags begin the "TEI Header" which is included in every document.

  • <titleStmt>; <title level="m" type="main">***********</title>; <title level="m" type="sub">a machine readable transcription</title>

The Title Statement (<titleStmt>) is the first tag within the File Description (<fileDesc>). <titleStmt> contains the information one would find on the title page of a book, inlcuding the title, author(s), editor(s), sponsor(s), and funder(s). The first tag, <title>, is the only one that changes from document to document, and each encoder needs to replace the asterisks with the proper title.

  • <author>Walt Whitman</author>; <editor>Kenneth M. Price</editor>; <editor>Ed Folsom</editor>; <respStmt>; <resp>Transcription and encoding</resp>; <name>The Walt Whitman Archive Staff</name>;

</respStmt>; <sponsor>The Institute for Advanced Technology in the Humanities</sponsor>; <sponsor>University of Iowa</sponsor>; <sponsor>University of Nebraska-Lincoln</sponsor>; <funder>The National Endowment for the Humanities</funder>; <funder>The United States Department of Education</funder>; </titleStmt><editionStmt>; <edition><date>2003</date></edition>; </editionStmt><publicationStmt> This part of the <titleStmt> and <editionStmt> remains the same for each file. *<idno>***.*****</idno> Insert the unique id at this point in the file. You need only to insert the three-letter prefix and the 5-digit number following it—you do not need to include the file extension (.sgm). The unique id will be given to you on the database when you are assigned manuscripts to encode.

  • <distributor>The Walt Whitman Archive</distributor>; <address>; <addrLine>The Institute for Advanced Technology in the Humanities</addrLine>; <addrLine>Alderman Library</addrLine>; <addrLine>University of Virginia</addrLine>; <addrLine>P.O. Box 400115</addrLine>; <addrLine>Charlottesville, VA 22904-4115</addrLine>; <addrLine>whitman@jefferson.village.virginia.edu</addrLine>; </address>; <availability>; <p>Copyright © 2002 by Ed Folsom and Kenneth M. Price, all rights reserved. Items in the Archive may be shared in accordance with the Fair Use provisions of U.S. copyright law. Redistribution or republication on other terms, in any medium, requires express written consent from the editors and advance notification of the publisher, The Institute for Advanced Technology in the Humanities. Permission to reproduce the graphic images in this archive has been granted by the owners of the originals for this publication only.</p>; </availability>; </publicationStmt>

This markup remains consistent on each document. It provides important publication information and our copyright notice.

  • <sourceDesc>; <bibl>; <author> Walt Whitman </author>; <title>**************</title>; <orgName>******************</orgName>; <note type="project">Transcribed from our own digital image of original manuscript.</note>; </bibl>; </sourceDesc>; </fileDesc>

The Source Description (<sourceDesc>) provides a bibliographic description of the texts being encoded. The author is always Walt Whitman, and the note, at this point in the project, will probably always read as above (previously, some were encoding from other sources). The title will vary for each file, and the title within the <sourceDesc> is different than other titles, as it must match the title given by the repository. The name of the repository must also be inserted each time you encode a new manuscript.

  • <profileDesc>; <handList>; <hand scribe="Fredson Bowers" id="fb">; </handList>; </profileDesc>

The <profileDesc> is used to identify hands other than Whitman's that show up on the manuscript. Other hands typically show up in editorial notes and "resp" (or "responsibility") attributes on the <gap> or <unclear> elements.

  • <revisionDesc>; <change>; <date>2002-xx-xx</date>; <respStmt>; <name>YOUR NAME HERE</name>; </respStmt>; <item>Encoded</item>; </change>; <change>; <date>2002-xx-xx</date>; <respStmt>; <name>YOUR NAME HERE</name>; </respStmt>; <item>Transcribed</item>; </change>; </revisionDesc>; </teiHeader>

The <revisionDesc> is where we describe all the work that goes into each file. To read about the procedures for this section.

  • <text type="manuscript">

The <text> tag describes the document being encoded at the basic level, and we have a type attribute in the <text> element in our DTD. The allowable values for type are:

  • galley-proof
  • letter
  • manuscript (for every item that doesn't fall into one of the two more specific categories above)
  • printed
  • periodical
  • ancillary (for essays by project editors and staff, for example)

Most of the time, you will use <text type="manuscript">.

  • <body>

The <body> tag is the basic container for all non-header markup. Specifically, the <body> tag contains the transcribed and encoded manuscript page.

  • <pb corresp="***.*****.***" id="leaf01r" type="recto"/>

The Page Break (<pb>) tag allows us to connect page images with encoded transcriptions, and we insert a <pb> tag before every <lg1> in the file. The "corresp" attribute indicates which image the page corresponds to, so you'll need to insert the unique id with a three-digit suffix that indicates the page number (.001, .002, etc). The "id" attribute refers to the "leaf" (or piece of paper) that the image is from. The "type" attribute refers to which side of the leaf the image corresponds to, the front ("recto") or back ("verso"). The "r" appended to the end of the id marks that the image is of the recto; a "v" is used there when the image is of the verso.

  • <lg1 type="poem">
The Line Group tag (<lg1>) is used to mark poems and the structural units within them. For most poetry manuscripts, you will not use a
tag but, instead, will use <lg1 type="poem"> to note the highest-order structural unit on the page.
  • <head type="main-derived">************</head>

The Head tag (<head>) is used to provide the title of the manuscript that will be used for indexing and display. To read about the procedures for providing a title within a <head>.

  • <l> </l>; <l>; <seg> </seg>; <seg> </seg>; </l>

This is very, very simplified basic structure for encoding poetic lines.

  • </lg1>; </body>; </text>; </TEI.2>

Remember, all tags that open must close by the end of the document. The end of your markup is likely to have a list of three or four end tags.

Downloadable Template

Click [template.xml here] to download the template.

Resources

Repository Codes

These codes are used to create unique identifiers for documents. Email Brett if the repository you're looking for isn't listed. **NOTE: As of November 2012, this list of repository codes is out of date. Please see the list of repositories in the Tracking Database, accessed here: [1].

Library Codes
Library/Collection Location Code
American Antiquarian Society Worcester, MA aas
Amherst College Amherst, MA amh
Anderson Galleries and
Boston Public Library Boston, MA bpl
Boston University Boston, MA bos
Brigham Young University Provo, UT byu
Brown University Providence, RI brn
Clifton College Bristol, UK clc
Dartmouth College Hanover, NH dar
Duke University, Trent Collection of Whitmaniana Durham, NC duk
Harvard University, Houghton Library Cambridge, MA har
Haverford College Haverford, PA hav
Huntington Public Library Huntington, NY hpl
The Huntington Library, Art Collections, and Botanical Gardens San Marino, CA hun
Johns Hopkins University Baltimore, MD jhu
Kansas State Historical Society Topeka, KS khs
Library of Congress Washington, DC loc
Manchester University Manchester, UK man
Massachusetts Historical Society Boston, MA mas
Mills College Oakland, CA mil
Missouri Historical Society St. Louis, MO mhs
National Archives Washington, DC; College Park, MD nar
New York Historical Society New York, NY nyh
New York Public Library New York, NY nyp
Ohio Wesleyan Univeristy Delaware, OH owu
Pierpont Morgan Library New York, NY pml
Princeton University Princeton, NJ pru
Private Collection prc
Rutgers University New Brunswick, NJ rut
St. John's Seminary sjs
Stanford University Palo Alto, CA sta
Temple University Philadelphia, PA tem
University of California, Berkeley, The Bancroft Library Berkeley, CA ucb
University of North Carolina Chapel Hill, NC unc
University of Pennsylvania Philadelphia, PA upa
University of Rochester Rochester, NY uro
University of South Carolina Columbia, SC usc
University of Texas, Humanities Research Center Austin, TX tex
University of Tulsa Tulsa, OK tul
University of Virginia, Valentine-Barrett Collection Charlottesville, VA uva
Washington University St. Louis, MO wau
Walt Whitman House Camden, NJ wwh
Western Carolina University Cullowhee, NC wcu
Yale University New Haven, CT yal

Preferred Citations

These citations need to be used when creating EAD documents and when completing the bibliographic information in <sourceDesc>.

Preferred Citations for Institutions Holding Whitman Materials
Library/Collection Preferred Citation
American Antiquarian Society Bolton-Stanwood Family Papers, American Antiquarian Society
Amherst College Amherst College Archives and Special Collections
Boston Public Library The Walt Whitman Collection, Boston Public Library
Boston University From the The Alice and Rollo G. Silver Collection in the Special Collections at Boston University
Brigham Young University L. Tom Perry Special Collections, Brigham Young University
British Library By permission of The British Library
Brown University John Hay Library, Brown University
Dartmouth College The Rauner Special Collections Library, Dartmouth College
Duke University, Trent Whitman Collection The Trent Collection of Walt Whitman Manuscripts, Duke University Rare Book, Manuscript, and Special Collections Library
Harvard University, Houghton Library Manuscripts Department, Houghton Library, Harvard University
Haverford College Haverford College Quaker and Special Collections
The Huntington The Huntington Library, Art Collections, and Botanical Gardens
The Huntington Public Library Treasures From Walt Whitman, Huntington Public Library, Huntington, New York
Johns Hopkins University Special Collections, The Milton S. Eisenhower Library, The Sheridan Libraries, The Johns Hopkins University
Knox College Special Collections and Archives, Knox College Library, Galesburg, Illinois
Library of Congress, Feinberg Collection The Charles E. Feinberg Collection of the Papers of Walt Whitman, 1839-1919, Library of Congress, Washington, DC.
Library of Congress, Harned Collection The Thomas Biggs Harned Collection of the Papers of Walt Whitman: A Register of His Papers in the Library of Congress, 1842-1937
Mills College Albert M. Bender Collection, Special Collections Department, F. W. Olin Library, Mills College
The Morgan Library The Pierpont Morgan Library, New York
New York Public Library The Henry W. and Albert A. Berg Collection of English and American Literature
Ohio Wesleyan Univeristy The Bayley-Whitman Collection, Ohio Wesleyan University, Delaware OH
Princeton University Manuscripts Division, Department of Rare Books and Special Collections, Princeton University Library
Rosenbach Library The Rosenbach Library and Museum
Rutgers University Special Collections and University Archives, Rutgers University Libraries, Rutgers, The State University of New Jersey
Temple University Rare Books and Manuscripts, Special Collections, Temple University Libraries, Temple University
University of California, Berkeley Walt Whitman Collection, The Bancroft Library, University of California, Berkeley
University of Pennsylvania Walt Whitman Collection, 1842-1957, Rare Book & Manuscript Library, University of Pennsylvania
University of Rhode Island University of Rhode Island Special Collections and Archives
University of Texas, Humanities Research Center The Walt Whitman Collection, Harry Ransom Humanities Research Center, The University of Texas at Austin
University of Tulsa Walt Whitman Ephemera, University of Tulsa
University of Virginia Papers of Walt Whitman (MSS 3829), Clifton Waller Barrett Library of American Literature, Albert H. Small Special Collections Library, University of Virginia
Washington University George N. Meissner Collection, Department of Special Collections, Washington University Libraries, Washington University
Yale Yale Collection of American Literature, Beinecke Rare Book and Manuscript Library

Links to TEI Guidelines

This part of the Encoding Guidelines is still under construction. If you have any suggestions for appropriate links, please email Andy.

Link to unScripting Whitman

unScripting Whitman

Unusual Characters or Marks

Please see the table in Section 3.7.

Work ID's

List of Work I.D.'s
Work I.D.
"Going Somewhere" xxx.00352
"Intestinal Agitation" xxx.00580
"Society" xxx.00538
"Specimen Days in America," London Edition, June, 1887. Preface to the Reader in the British Islands xxx.00476
"The Rounded Catalogue Divine Complete" xxx.00404
"Unassail'd Renown" xxx.00570
"Walt Whitman's Last 'Public'" xxx.00581
A Backward Glance O'er Travel'd Roads xxx.00410
Aboard at a Ship's Helm xxx.00135
A Boston Ballad (1854) xxx.00143
Abraham Lincoln, born Feb. 12, 1809 xxx.00327
Abraham Lincoln xxx.00479
A Broadway Pageant xxx.00021
A Carol Closing Sixty-Nine xxx.00315
A Child's Amaze xxx.00158
A Christmas Greeting From a Northern Star-Group to a Southern, 1889-'90. xxx.00396
A Clear Midnight xxx.00291
Additional Note, 1887, to English Edition "Specimen Days" xxx.00477
A Death-Bouquet xxx.00562
Adieu to a Soldier xxx.00213
A Farm Picture xxx.00157
A Font of Type xxx.00317
After an Interval xxx.00455
after certain disastrous campaigns xxx.00595
After the Argument xxx.00565
After the Dazzle of Day xxx.00326
After the Sea-Ship xxx.00141
After the Supper and Talk xxx.00376
Ages and Ages Returning at Intervals xxx.00057
A Glimpse xxx.00097
A Hand-Mirror xxx.00145
Ah Poverties, Wincings, and Sulky Retreats xxx.00279
A Leaf for Hand in Hand xxx.00098
A Lincoln Reminiscence xxx.00549
All is Truth xxx.00276
A March in the Ranks Hard-Prest, and the Road Unknown xxx.00188
A Memorandum at a Venture xxx.00530
America's Bulk Average xxx.00591
American National Literature xxx.00560
America xxx.00323
Among the Multitude xxx.00106
An American Problem xxx.00553
An Army Corps on the March xxx.00184
And Yet Not You Alone xxx.00335
An Ended Day xxx.00387
An Engineer's Obituary xxx.00587
An Evening Lull xxx.00374
An Indian Bureau Reminiscence xxx.00470
A Noiseless Patient Spider xxx.00013
An Old Man's Rejoinder xxx.00558
An Old Man's Thought of School xxx.00255
Any thing is as good as established xxx.00614
A Paumanok Picture xxx.00268
A Persian Lesson xxx.00402
Apparitions xxx.00385
A Prairie Sunset xxx.00364
A procession without halt xxx.00622
A Promise to California xxx.00094
Are You the New Person Drawn toward Me? xxx.00081
A Riddle Song xxx.00277
As Adam Early in the Morning xxx.00065
As a Strong Bird on Pinions Free. And Other Poems xxx.00501
As at Thy Portals Also Death xxx.00298
As Consequent, Etc. xxx.00224
Ashes of Soldiers (Cluster) xxx.00499
Ashes of Soldiers (Poem) xxx.00293
A Sick Spell xxx.00578
As I Ebb'd with the Ocean of Life xxx.00132
As If a Phantom Caress'd Me xxx.00008
A Sight in Camp in the Daybreak Gray and Dim xxx.00189
As I Lay with My Head in Your Lap Camerado xxx.00208
As in a Swoon xxx.00567
As I Ponder'd in Silence xxx.00025
As I Sit Writing Here xxx.00318
As I Walk These Broad Majestic Days xxx.00290
As I Watch'd the Ploughman Ploughing xxx.00019
As of Forms xxx.00611
A Song for Occupations xxx.00119
A Song of Joys xxx.00115
A Song of the Rolling Earth xxx.00120
A Soul Duet xxx.00602
Assurances xxx.00009
As the Greek's Signal Flame xxx.00371
As the Time Draws Nigh xxx.00294
As They Draw to a Close xxx.00303
As Toilsome I Wander'd Virginia's Woods xxx.00190
A Thought of Columbus xxx.00600
A Thought on Shakspere xxx.00466
A Twilight Song xxx.00398
Autumn Rivulets xxx.00223
A Voice from Death xxx.00401
A Woman Waits for Me xxx.00053
A Word About Tennyson xxx.00468
A World's Show xxx.00576
Bathed in War's Perfume (Cluster) xxx.00423
Bathed in War's Perfume (Poem) xxx.00424
Beat! Beat! Drums! xxx.00175
Beautiful Women xxx.00160
Beginners xxx.00034
Beginning My Studies xxx.00033
Behavior xxx.00621
Behold This Swarthy Face xxx.00086
Birds of Passage xxx.00122
Bivouac on a Mountain Side xxx.00183
Blood-Money xxx.00520
Book-Classes—America's Literature xxx.00551
Bravo, Paris Exposition! xxx.00392
British Literature xxx.00536
Broadway xxx.00345
By Blue Ontario's Shore xxx.00221
By Broad Potomac's Shore xxx.00284
By That Long Scan of Waves xxx.00337
By the Bivouac's Fitful Flame xxx.00185
By the Roadside xxx.00142
Calamus xxx.00066
Camps of Green xxx.00301
Cavalry Crossing a Ford xxx.00182
Centennial Songs---1876 xxx.00492
Chanting the Square Deific xxx.00005
Chants Democratic and Native American xxx.00411
Children of Adam xxx.00049
City of Orgies xxx.00085
City of Ships xxx.00180
Collect xxx.00506
Come, said my Soul xxx.00596
Come Up from the Fields Father xxx.00186
Complete Poems & Prose of Walt Whitman, 1855-1888 Authenticated & Personal Book (handled by W.W.) . . . Portraits from Life . . . Autograph xxx.00503
Complete Prose Works xxx.00504
Continuities xxx.00349
Crossing Brooklyn Ferry xxx.00112
Darest Thou Now O Soul xxx.00004
Darwinism—(then Furthermore) xxx.00537
Death's Valley xxx.00593
Death's Valley xxx.00605
Death in the School-Room (A Fact) xxx.00510
Death of Abraham Lincoln. Lecture deliver'd in New York, April 14, 1879—in Philadelphia, '80—in Boston, '81 xxx.00531
Death of General Grant xxx.00341
Debris (Cluster) xxx.00453
Debris (Poem) xxx.00418
Delicate Cluster xxx.00209
Democracy in the New World xxx.00540
Democratic Vistas xxx.00524
Dirge for Two Veterans xxx.00196
Dough-Face Song xxx.00509
Drum-Taps xxx.00172
Dumb Kate xxx.00518
Earth, My Likeness xxx.00099
Eidólons xxx.00030
Eighteen Sixty-One xxx.00174
Election Day, November, 1884 xxx.00339
Emerson's Books, (the Shadows of Them) xxx.00534
Ethiopia Saluting the Colors xxx.00200
Europe, The 72d and 73d Years of These States xxx.00144
Excelsior xxx.00278
Faces xxx.00271
Facing West from California's Shores xxx.00064
Fancies at Navesink xxx.00330
Fast Anchor'd Eternal O Love! xxx.00105
Father Taylor (and Oratory) xxx.00463
Feeling Fairly xxx.00583
First Annex: Sands at Seventy xxx.00310
First O Songs for a Prelude xxx.00173
Five Thousand Poems xxx.00473
For Him I Sing xxx.00031
For Queen Victoria's Birthday xxx.00557
For Us Two, Reader Dear xxx.00566
For You O Democracy xxx.00074
Foundation Stages—then Others xxx.00541
France, the 18th Year of These States xxx.00126
Franklin Evans; or The Inebriate: A Tale of the Times xxx.00488
Freedom xxx.00550
Friendship, (the Real Article) xxx.00544
From Far Dakota's Cañons xxx.00285
From Montauk Point xxx.00313
From My Last Years xxx.00494
From Noon to Starry Night xxx.00269
From Paumanok Starting I Fly like a Bird xxx.00176
From Pent-up Aching Rivers xxx.00051
Full of Life now xxx.00109
Gathering the Corn xxx.00561
Gay-heartedness xxx.00574
General Suffrage, Elections, &c. xxx.00542
George Fox (and Shakspere) xxx.00487
Germs xxx.00147
Give Me the Splendid Silent Sun xxx.00195
Gliding o'er All xxx.00165
Gods xxx.00146
Good-Bye my Fancy! (Good-bye my Fancy!) xxx.00378
Good-Bye my Fancy (cluster in Complete Prose Works) xxx.00555
Good-Bye my Fancy (I had a word to say) xxx.00382
Good-Bye My Fancy (separate volume) xxx.00459
Grand is the Seen xxx.00408
Great Are the Myths xxx.00430
Had I the Choice xxx.00332
Halcyon Days xxx.00329
Hands Round xxx.00607
Hast Never Come to Thee an Hour xxx.00166
Health, (Old Style) xxx.00573
He is wisest who has the most caution xxx.00418
Here the Frailest Leaves of Me xxx.00095
Hours continuing long xxx.00070
How Solemn as One by One xxx.00207
Hush'd be the Camps To-day xxx.00219
I am He that Aches with Love xxx.00060
I do not expect to see myself xxx.00597
I Dream'd in a Dream xxx.00100
I Hear America Singing xxx.00041
I Heard You Solemn-Sweet Pipes of the Organ xxx.00063
I Hear It was Charged against Me xxx.00090
In Cabin'd Ships at Sea xxx.00026
Indications xxx.00613
In Former Songs xxx.00490
Ingersoll's Speech xxx.00582
In Paths Untrodden xxx.00071
Inscription for a Little Book on Giordano Bruno xxx.00571
Inscriptions xxx.00022
Interpolation Sounds xxx.00393
In the New Garden xxx.00434
I Saw in Louisiana a Live-Oak Growing xxx.00087
I Saw Old General at Bay xxx.00198
I Sing the Body Electric xxx.00052
I Sit and Look Out xxx.00153
Italian Music in Dakota xxx.00257
I was Looking a Long While xxx.00241
I will take an egg out of the robin's nest in the orchard xxx.00620
Joy, Shipmate, Joy! xxx.00304
Kosmos xxx.00248
L. of G.'s Purport xxx.00406
Lacks and Wants Yet xxx.00545
Last of Ebb, and Daylight Waning xxx.00334
Last of the War Cases xxx.00485
Last Saved Items xxx.00592
Last Words xxx.00603
Laws for Creations xxx.00240
Leaflets xxx.00450
Leaves of Grass (1860 cluster) xxx.00436
Leaves of Grass (1867 cluster 1) xxx.00438
Leaves of Grass (1867 cluster 2) xxx.00439
Leaves of Grass (1867 cluster 3) xxx.00440
Leaves of Grass (1867 cluster 4) xxx.00441
Leaves of Grass (1871-72 cluster 1) xxx.00442
Leaves of Grass (1871-72 cluster 2) xxx.00443
Leaves of Grass (1871-72 cluster 3) xxx.00444
Leaves of Grass (1871-72 cluster 4) xxx.00445
Leaves of Grass (1871-72 cluster 5) xxx.00446
Leaves of Grass (1871-72 cluster 6) xxx.00448
Leaves of Grass (1871-72 cluster 7) xxx.00449
Leaves of Grass (cluster in Passage to India) xxx.00497
Leaves of Grass xxx.00001
Lessons xxx.00429
Life and Death xxx.00358
Life xxx.00351
Lingave's Temptation xxx.00516
Lingering Last Drops xxx.00381
Little Jane xxx.00517
Little or Nothing New, After All xxx.00548
Lo, Victress on the Peaks xxx.00211
Locations and Times xxx.00169
L of G. xxx.00564
Long, Long Hence xxx.00391
Long, too Long America xxx.00194
Long I thought that knowledge alone would suffice xxx.00069
Look Down Fair Moon xxx.00205
Mannahatta (I was asking) xxx.00275
Mannahatta (My city's) xxx.00311
Marches Now the War is Over xxx.00421
Mediums xxx.00281
Me Imperturbe xxx.00038
Memoranda During the War xxx.00502
Memoranda xxx.00575
Memories of President Lincoln xxx.00216
Memories xxx.00324
Messenger Leaves xxx.00412
Miracles xxx.00243
Mirages xxx.00405
Monuments—the Past and Present xxx.00547
Mother and Babe xxx.00161
My 71st Year xxx.00384
My Canary Bird xxx.00319
My Legacy xxx.00299
My Picture-Gallery xxx.00259
Myself and Mine xxx.00127
Nationality—(and Yet) xxx.00533
Native Moments xxx.00061
Nay, Tell Me Not To-day the Publish'd Shame xxx.00608
New Orleans in 1848 xxx.00480
New York—The Bay—The Old Name xxx.00577
Night on the Prairies xxx.00016
No Labor-Saving Machine xxx.00096
Notes (such as they are) founded on Elias Hicks xxx.00486
Notes Left Over xxx.00532
Notes to Late English Books xxx.00475
Note to a Friend xxx.00482
Not Heat Flames up and Consumes xxx.00083
Not Heaving from my Ribb'd Breast Only xxx.00076
Not Meagre, Latent Boughs Alone xxx.00369
Not My Enemies Ever Invade Me xxx.00457
Not the Pilot xxx.00191
Not Youth Pertains to Me xxx.00201
November Boughs xxx.00460
Now Finalè to the Shore (Cluster) xxx.00426
Now Finalè to the Shore (Poem) xxx.00308
Now Lift Me Close xxx.00452
Now List to My Morning's Romanza xxx.00612
Now Precedent Songs, Farewell xxx.00373
O Captain! My Captain! xxx.00218
Offerings xxx.00170
Of Him I Love Day and Night xxx.00006
Of ownership xxx.00414
Of That Blithe Throat of Thine xxx.00344
Of the Terrible Doubt of Appearances xxx.00077
Of the visages of things xxx.00416
Of waters, forests, hills xxx.00415
O Hymen! O Hymenee! xxx.00059
Old Actors, Singers, Shows, &c., in New York Flitting mention—(with much left out.) xxx.00588
Old Age's Lambent Peaks xxx.00375
Old Age's Ship & Crafty Death's xxx.00388
Old-Age Echoes xxx.00601
Old Brooklyn Days xxx.00584
Old Chants xxx.00395
Old Ireland xxx.00227
Old Poets xxx.00559
Old Salt Kossabone xxx.00347
Old War-Dreams xxx.00286
O Living Always, Always Dying xxx.00014
O Magnet-South xxx.00274
O Me! O Life! xxx.00151
On, on the Same, ye Jocund Twain! xxx.00383
Once I Pass'd through a Populous City xxx.00062
One's-Self I Sing xxx.00024
One Hour to Madness and Joy xxx.00055
One or Two index Items xxx.00523
One sweeps by, attended by an immense train xxx.00616
One sweeps by, old, with black eyes, and profuse white hair xxx.00616
One Wicked Impulse! xxx.00511
On Journeys through the States xxx.00036
On the Beach at Night Alone xxx.00138
On the Beach at Night xxx.00136
Orange Buds by Mail From Florida xxx.00366
Or from that Sea of Time xxx.00493
Origins of Attempted Secession. Not the whole matter, but some side facts worth conning to-day and any day xxx.00525
Osceola xxx.00400
O Star of France 1870-71 xxx.00253
O Sun of Real Peace xxx.00422
O Tan-Faced Prairie-Boy xxx.00204
Others may Praise What They Like xxx.00249
Our Eminent Visitors, Past, Present, and Future xxx.00461
Our Old Feuillage xxx.00114
Our Real Culmination xxx.00552
Out from Behind This Mask xxx.00236
Out in the Open Again xxx.00590
Outlines for a Tomb xxx.00235
Out of May's Shows Selected xxx.00328
Out of the Cradle Endlessly Rocking xxx.00131
Out of the Rolling Ocean the Crowd xxx.00056
Over the Carnage Rose Prophetic a Voice xxx.00197
O You whom I Often and Silently Come xxx.00107
Passage to India xxx.00496
Patroling Barnegat xxx.00140
Paumanok xxx.00312
Pensive and Faltering xxx.00020
Pensive on Her Dead Gazing xxx.00300
Perfections xxx.00150
Pieces in Early Youth 1834-'42 xxx.00508
Pioneers! O Pioneers! xxx.00124
Poem—a perfect school xxx.00604
Poem of Existence xxx.00599
Poem of Remembrances for a Girl or a Boy of These States xxx.00431
Poetry To-Day in America—Shakspere—the Future xxx.00529
Poets to Come xxx.00045
Portals xxx.00306
Prayer of Columbus xxx.00263
Preface, 1872, to "As a Strong Bird on Pinions Free," (now "Thou Mother with thy Equal Brood," in permanent ed'n.) xxx.00527
Preface, 1876, to the two-volume Centennial Edition of L. of G. and "Two Rivulets" xxx.00528
Preface Note to 2d Annex, concluding L. of G.—1891. xxx.00379
Preface to "Democratic Vistas" with Other Papers.—English Edition xxx.00478
Preface to a volume of essays and tales by Wm. D. O'Connor, pub'd posthumously in 1891 xxx.00586
Preface to Leaves of Grass (1855) xxx.00526
Proudly the Flood Comes In xxx.00336
Proud Music of the Storm xxx.00262
Queries to My Seventieth Year xxx.00320
Quicksand Years xxx.00010
Race of Veterans xxx.00202
Reconciliation xxx.00206
Recorders Ages Hence xxx.00079
Red Jacket (from Aloft) xxx.00342
Respondez! xxx.00433
Reversals xxx.00222
Rise O Days from Your Fathomless Deeps xxx.00178
Roaming in Thought xxx.00156
Robert Burns as Poet and Person xxx.00467
Roots and Leaves Themselves Alone xxx.00082
Rulers Strictly Out of the Masses xxx.00546
Sailing the Mississippi at Midnight xxx.00522
Sail Out for Good, Eidólon Yacht! xxx.00380
Salut au Monde! xxx.00110
Savantism xxx.00039
Says xxx.00417
Scantlings xxx.00609
Scented Herbage of My Breast xxx.00072
Sea-Drift xxx.00130
Sea-Shore Memories xxx.00500
Second Annex: Good-Bye my Fancy xxx.00377
Sequel to Drum-Taps xxx.00456
Shakspere-Bacon's Cipher xxx.00390
Shakspere for America xxx.00569
Ship Ahoy! xxx.00556
Shut not Your Doors xxx.00044
Slang in America xxx.00469
Small Memoranda xxx.00481
Small the Theme of My Chant xxx.00353
So far, and so far, and on toward the end xxx.00437
Solid, Ironical, Rolling Orb xxx.00447
So Long! xxx.00309
Some Diary Notes at Random xxx.00471
Some Laggards Yet xxx.00563
Some Personal and Old-Age Jottings xxx.00589
Sometimes with One I Love xxx.00103
Some War Memoranda Jotted Down at the Time xxx.00472
Song at Sunset xxx.00297
Song for All Seas, All Ships xxx.00139
Song of Myself xxx.00048
Song of Prudence xxx.00232
Song of the Answerer xxx.00113
Song of the Banner at Daybreak xxx.00177
Song of the Broad-Axe xxx.00116
Song of the Exposition xxx.00117
Song of the Open Road xxx.00111
Song of the Redwood-Tree xxx.00118
Song of the Universal xxx.00123
Songs of Insurrection xxx.00425
Songs of Parting xxx.00292
Soon Shall the Winter's Foil Be Here xxx.00360
Sounds of the Winter xxx.00397
Spain, 1873-74 xxx.00283
Sparkles From the Wheel xxx.00244
Specimen Days & Collect (separate volume) xxx.00458
Specimen Days xxx.00505
Spirit That Form'd This Scene xxx.00289
Spirit whose Work is Done xxx.00212
Splinters xxx.00572
Spontaneous Me xxx.00054
Starting from Paumanok xxx.00047
States! xxx.00067
Still though the One I Sing xxx.00043
Stronger Lessons xxx.00363
Suggestions xxx.00419
Talk to an Art-Union (A Brooklyn fragment.) xxx.00519
Tears xxx.00133
Tests xxx.00251
Thanks in Old Age xxx.00357
That Music Always Round Me xxx.00011
That Shadow My Likeness xxx.00108
The Answerer xxx.00420
The Artilleryman's Vision xxx.00199
The Base of All Metaphysics xxx.00078
The Beauty of the Ship xxx.00454
The Bible as Poetry xxx.00462
The Boy Lover xxx.00514
The Bravest Soldiers xxx.00316
The Calming Thought of All xxx.00356
The Centenarian's Story xxx.00181
The Child and the Profligate xxx.00515
The City Dead-House xxx.00228
The Commonplace xxx.00403
The Dalliance of the Eagles xxx.00155
The Dead Emperor xxx.00370
The Dead Tenor xxx.00348
The Dismantled Ship xxx.00372
The Dying Veteran xxx.00362
The Eighteenth Presidency! xxx.00610
The First Dandelion xxx.00322
The greatest thing is to make a xxx.00598
The Last Collective Compaction xxx.00554
The Last Invocation xxx.00018
The Last Loyalist xxx.00512
The Mystic Trumpeter xxx.00272
Then Last of All xxx.00338
The Old Bowery xxx.00474
The Ox-Tamer xxx.00254
The Pallid Wreath xxx.00386
The Perfect Human Voice xxx.00568
The Pilot in the Mist xxx.00331
The Place Gratitude Fills in a Fine Character xxx.00484
The Prairie-Grass Dividing xxx.00091
The Prairie States xxx.00260
The Return of the Heroes xxx.00225
There was a Child Went Forth xxx.00226
The Runner xxx.00159
These Carols xxx.00307
These I Singing in Spring xxx.00075
The Ship Starting xxx.00040
The Singer in the Prison xxx.00233
The Sleepers xxx.00264
The Sobbing of the Bells xxx.00302
The Spanish Element in Our Nationality xxx.00464
The Torch xxx.00252
The Tramp and Strike Questions. Part of a Lecture proposed, (never deliver'd.) xxx.00539
The Unexpress'd xxx.00407
The United States to Old World Critics xxx.00355
The Untold Want xxx.00305
The Voice of the Rain xxx.00359
The Wallabout Martyrs xxx.00321
The World Below the Brine xxx.00137
The Wound-Dresser xxx.00193
Thick-Sprinkled Bunting xxx.00287
Think of the Soul xxx.00432
This Compost xxx.00229
This Day, O Soul xxx.00428
This Dust was Once the Man xxx.00220
This Moment Yearning and Thoughtful xxx.00089
Thought (As I sit) xxx.00017
Thought (Of Equality) xxx.00167
Thought (Of Justice) xxx.00164
Thought (Of obedience) xxx.00162
Thought (Of persons) xxx.00242
Thought (Of what I write from myself) xxx.00451
Thoughts (Of ownership) xxx.00148
Thoughts (Of public opinion) xxx.00280
Thoughts (Of these years) xxx.00296
Thoughts xxx.00413
Thou Mother with Thy Equal Brood xxx.00267
Thou Orb Aloft Full-Dazzling xxx.00270
Thou Reader xxx.00046
Thou West that gave'st him to us xxx.00606
Three old men slowly pass xxx.00618
To a Certain Cantatrice xxx.00037
To a Certain Civilian xxx.00210
To a Common Prostitute xxx.00261
To a Foil'd European Revolutionaire xxx.00230
To a Historian xxx.00028
To a Locomotive in Winter xxx.00273
To a President xxx.00152
To a Pupil xxx.00245
To a Stranger xxx.00088
To a Western Boy xxx.00104
To Be Present Only xxx.00579
To-day and Thee xxx.00325
To Foreign Lands xxx.00027
To Get the Final Lilt of Songs xxx.00346
To Him That was Crucified xxx.00238
To Old Age xxx.00168
To One Shortly to Die xxx.00015
To Rich Givers xxx.00154
To the East and to the West xxx.00102
To Thee Old Cause xxx.00029
To the Garden the World xxx.00050
To the Leaven'd Soil They Trod xxx.00215
To the Man-of-War-Bird xxx.00134
To the Pending Year xxx.00389
To the Reader at Parting xxx.00427
To the States, To Identify the 16th, 17th, or 18th Presidentiad xxx.00171
To the States xxx.00035
To the Sun-set Breeze xxx.00394
To Think of Time xxx.00266
To Those Who've Fail'd xxx.00314
To You (Let us twain) xxx.00498
To You (Stranger, if you) xxx.00023
To You (Whoever you are) xxx.00125
Transpositions xxx.00265
Trickle Drops xxx.00084
True Conquerors xxx.00354
Turn O Libertad xxx.00214
Twenty Years xxx.00365
Twilight xxx.00367
Two Letters xxx.00507
Two Questions xxx.00585
Two Rivulets, including Democratic Vistas, Centennial Songs, and Passage to India xxx.00489
Two Rivulets xxx.00495
Unfolded Out of the Folds xxx.00246
Unnamed Lands xxx.00231
Unseen Buds xxx.00409
Veil with their lids, &c xxx.00594
Ventures, on an Old Theme xxx.00535
Vigil Strange I Kept on the Field One Night xxx.00187
Virginia—the West xxx.00179
Visor'd xxx.00163
Vocalism xxx.00237
Wandering at Morn xxx.00256
Warble for Lilac-Time xxx.00234
Washington's Monument, February, 1885 xxx.00343
Weave in, My Hardy Life xxx.00282
We Two, How Long We were Fool'd xxx.00058
We Two Boys Together Clinging xxx.00093
What am I After All xxx.00247
What Best I See in Thee xxx.00288
What General has a good army in himself xxx.00615
What Lurks Behind Shakspere's Historical Plays? xxx.00465
What Place Is Besieged? xxx.00042
What Ship Puzzled at Sea xxx.00012
What Think You I Take My Pen in Hand? xxx.00101
What weeping face is that looking from the window? xxx.00619
When I Heard at the Close of the Day xxx.00080
When I Heard the Learn'd Astronomer xxx.00149
When I Peruse the Conquer'd Fame xxx.00092
When I Read the Book xxx.00032
When Lilacs Last in the Dooryard Bloom'd xxx.00217
When the Full-grown Poet Came xxx.00399
While Not the Past Forgetting xxx.00361
Whispers of Heavenly Death (Cluster) xxx.00002
Whispers of Heavenly Death (Poem) xxx.00003
Whoever You are Holding Me Now in Hand xxx.00073
Who Gets the Plunder? xxx.00543
Who is now reading this? xxx.00068
Who Learns My Lesson Complete? xxx.00250
Wild Frank's Return xxx.00513
With All Thy Gifts xxx.00258
With all Thy Gifts xxx.00491
With Antecedents xxx.00129
With Husky-Haughty Lips, O Sea! xxx.00340
World Take Good Notice xxx.00203
Wounded in the House of Friends xxx.00521
Written Impromptu in an Album xxx.00483
Year of Meteors (1859-60) xxx.00128
Years of the Modern xxx.00295
Year that Trembled and Reel'd Beneath Me xxx.00192
Yet, Yet, Ye Downcast Hours xxx.00007
Yonnondio xxx.00350
You Felons on Trial in Courts xxx.00239
You Lingering Sparse Leaves of Me xxx.00368
Youth, Day, Old Age and Night xxx.00121
You Tides With Ceaseless Swell xxx.00333

Retrieved from "http://whitmanarchive.org/mediawiki/index.php?title=Whitman_Encoding_Guidelines&oldid=269"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox