This keyboarded and encoded edition of the work described above is co-owned by the institutions providing financial support to the Early English Books Online Text Creation Partnership. Searching, reading, printing, or downloading EEBO-TCP texts is reserved for the authorized users of these project partner institutions. Permission must be granted for subsequent distribution, in print or electronically, of this text, in whole or in part. Please contact project staff at eebotcp-info@umich.edu for further information or permissions.
"Presented at Salisbury court by Her Majesties servants."
Reproduction of original in Bristol Public Library, Bristol, England.
The goal of this project is
This text is derived from an EEBO-TCP text but has undergone additional curation. The following passage, quoted from the editorial declaration of the TCP header, summarize the TCP encoding and quality assurance practices, and define appropriate levels of expectation about TCP transcriptions:
EEBO-TCP aimed to produce large quantities of textual data within the usual project restraints of time and funding, and therefore chose to create diplomatic transcriptions (as opposed to critical editions) with light-touch, mainly structural encoding based on the Text Encoding Initiative (http://www.tei-c.org)...Image sets were sent to external keying companies for transcription and basic encoding. Quality assurance was then carried out by editorial teams in Oxford and Michigan. 5% (or 5 pages, whichever is the greater) of each text was proofread for accuracy and those which did not meet QA standards were returned to the keyers to be redone. After proofreading, the encoding was enhanced and/or corrected and characters marked as illegible were corrected where possible up to a limit of 100 instances per text. Any remaining illegibles were encoded as <gap>s. Understanding these processes should make clear that, while the overall quality of TCP data is very good, some errors will remain and some readable characters will be marked as illegible. Users should bear in mind that in all likelihood such instances will never have been looked at by a TCP editor.
The editorial work on this project has been done mainly by undergraduates, who have turned out to require very little training to become expert at identifying and fixing a high percentage of manifest textual defects. But each text will require editorial attention before it could be certified as a text that meets the standards one associates with a printed text good enough for many scholarly purposes. At the minimum, each text should be proofread against its printed source or a high-quality facsimile of it.
The texts were tokenized. Each token was wrapped in a
The structural elements
The TCP transcriptions ignored linebreaks but marked hyphenated words as well as words split across lines without a hyphen. In this version such hyphen markers have been tacitly removed unless there was clear evidence that the word was a hyphenated word.
Incompletely and incorrectly transcribed or printed words were corrected without distinguishing between printer's or transcriber's errors. But all changes from the spellings that occur in the TCP text have been logged in something like an
Variant spellings have been mapped to standard forms using the Oxford English Dictionary as a guide. Spellings have been standardized rather than modernized. Thus 'louyth' has been mapped to 'loveth' rather than 'loves'. The capitalization of standardized spellings has followed modern rules. The original and standardized spellings appear in the text as alternate
A few typographical and orthographic features have been tacitly standardized. All instances of long 's' have been mapped to the modern form. The character 'Ʋ' (\u01b2), has been mapped to 'V'. A number of printers' abbreviations, captured in the original SGML transcriptions as character entities, have been tacitly resolved to the spellings they represent--ee.g cum&abque; > 'cumque'. In some very early texts 'the' ,'that', and 'thou' are represented as 'y' followed by a superscripted 'e', 't', or 'u'. They have been tacitly resolved to 'the', 'that' and 'thou'. The same policy has been followed for the rarer instances of 'with' or 'which' spelled as 'w' followed by a superscripted 't' or 'c'. The decorations of initial characters have been ignored.
The following
The textual notes below aim at making textual corrections readable in their immediate context and facilitating access to the source text. A five-dit number preceded by 'A' or 'B' represents an EEBO-TCP filenumber. A notation like "6-b-2890" means "look for EEBO page image 6 of that text, word 289 on the right side of the double-page image." That reference is followed by the corrupt reading. A black dot stands for an unidentified letter, a black square for an unidentified punctuation mark, a diamond for a missing word, and the ellipsis for a short span of undefined length. The corrected reading is displayed as a kewyord in context.