Steven Steple to mast. Camell

Steven Steple to mast. Camell

Table of contents

Steven Steple to mast Camell▪

§

[Page]

Steven Steple to mast Camell▪

REst ye mery vayre zyr, I trow ye be maste Camell.

ichā on message to you zent, vrom goodmā Geffrai Chapel

A hate ye zent a bottell a hay, and bad commaunde ma tye ye,

And vorde dyng he spake ye to, a preyd ye dat ye wood hy ye,

And zuch kynd daintrels as a had, zum draf he hate ye zent,

A zyerd ye vor to gnab deron, vor der is no better in Rent,

Tis goode and zoote & alzo new. to mende your zyckysh brayne

Vor weele a zeete ye ha great stud, & zet your self to payne,

Him vraid yer wits wud zore ye vayle, ye gyn to raue zo zone,

A dynkte ye wyll be mad, al out, beuore dat May be done:

And moch he merueilt dat ye wud, zo chorlshly to vin wryghte,

And dat ye zent vm such an Anser, dat zounded noding right

To Harry Hoball zyr ye wrot, as pearit in your letter,

zwap yer speckles vp se nase, and looke about ye better,

And Anser Geffray Chappell zyr, dat toke ye de zupplicacion,

Vor his name is not Hary whobal, ich zwear by gods zauacion

How zay ye now yore speckles be on, can ye vorstande his byll,

ych ween a trete ye (zereuerence a you) to do Churchard no yl

And her cha brought yor byll ayen, corrupt it or ich go,

Vor vende gods vorbod man I zedge, to let it go vorth zo:

But well ich zee yor brayne is dicke, yor wits be curstly vext,

Prey God ye be not zyde yor zelf, er be to morow next:

Deruore go couch and sleap a nowe, and dan com to yor parte,

And dyte a wyser dyng dan dat, or all is not wort a vart.

Now ych ha myne arnde a do,

Chud ha ye yor head to heede a

And ve good maister Churchard to,

And zo God be yor sprede a.

§

§

Imprinted by Richard Lant.

Information about this book

Title statement

Steven Steple to mast. Camell

Steple, Steven.

Edition statement

1552

Publication

Publisher

Text Creation Partnership,

Place of publication

Ann Arbor, MI ; Oxford (UK) :

Date

2008-09 (EEBO-TCP Phase 1).

ID [DLPS]

A12958

ID [STC]

STC 23251.5

ID [STC]

ESTC S3000

ID [EEBO-CITATION]

29647474

ID [OCLC]

ocm 29647474

ID [VID]

28060

Availability

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. This Phase I text is available for reuse, according to the terms of Creative Commons 0 1.0 Universal. The text can be copied, modified, distributed and performed, even for commercial purposes, all without asking permission.

Series

Early English books online.

Notes

(EEBO-TCP ; phase 1, no. A12958)

Transcribed from: (Early English Books Online ; image set 28060)

Images scanned from microfilm: (Early English books, 1475-1640 ; 1861:22)

Source

— Steven Steple to mast. Camell, Steple, Steven..

Extent

1 sheet ([1] p.).

Jmprinted by Richard Lant,. [S.l.] :: [1552?]. (In verse.) (Date of publication suggested by STC (2nd ed.)) (Reproduction of original in the Society of Antiquaries.)

Creation

Created by converting TCP files to TEI P5 using tcp2tei.xsl, TEI @ Oxford.

Editorial practices

EEBO-TCP is a partnership between the Universities of Michigan and Oxford and the publisher ProQuest to create accurately transcribed and encoded texts based on the image sets published by ProQuest via their Early English Books Online (EEBO) database (http://eebo.chadwyck.com). The general aim of EEBO-TCP is to encode one copy (usually the first edition) of every monographic English-language title published between 1473 and 1700 available in EEBO.

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).

The EEBO-TCP project was divided into two phases. The 25,363 texts created during Phase 1 of the project have been released into the public domain as of 1 January 2015. Anyone can now take and use these texts for their own purposes, but we respectfully request that due credit and attribution is given to their original source.

Users should be aware of the process of creating the TCP texts, and therefore of any assumptions that can be made about the data.

Text selection was based on the New Cambridge Bibliography of English Literature (NCBEL). If an author (or for an anonymous work, the title) appears in NCBEL, then their works are eligible for inclusion. Selection was intended to range over a wide variety of subject areas, to reflect the true nature of the print record of the period. In general, first editions of a works in English were prioritized, although there are a number of works in other languages, notably Latin and Welsh, included and sometimes a second or later edition of a work was chosen if there was a compelling reason to do so.

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 texts were encoded and linked to page images in accordance with level 4 of the TEI in Libraries guidelines.

Copies of the texts have been issued variously as SGML (TCP schema; ASCII text with mnemonic sdata character entities); displayable XML (TCP schema; characters represented either as UTF-8 Unicode or text strings within braces); or lossless XML (TEI P5, characters represented either as UTF-8 Unicode or TEI g elements).

Keying and markup guidelines are available at the Text Creation Partnership web site.