VVhereas the Lord Generall hath received a message from the Committee for the Admirality, ...

VVhereas the Lord Generall hath received a message from the Committee for the Admirality, ...

Table of contents

§

§

[Page]

[Page]

London ss.

WHereas the Lord Generall hath received a message from the Committee for the Admiralty, to recommend unto me how some good quantity of old Linnen may be gotten and made ready to be speedily sent to the sea-coast, for the dressing of the wounds of the souldiers who were wounded in the late Ingagement at Sea; which his excellency by his letter hath done accordingly: These are therefore earnestly to desire you that on the next Lords day you do publish and make known, the same in your respective Congregations, and that the Church-wardens of the severall Parishes do take notice thereof, and do forthwith repair to the houses of the severall inhabitants within the same Parishes, and receive and take into their custody all such linnen as well disposed people shall give for the purpose aforesaid, and to let them know that some trusty Persons will be appointed for the receiving of such linnen from the Church-wardens as they shall gather and get ready, and will send and dispose of the same to the use of the wounded Souldiers; And hereof I desire your and their care and furtherance herein, it being a work so pious and charitable,

Dated this 6 of August 1653.

John Fowke Maior.

To the Ministers and Church-wardens of the severall Parishes within the City of London, and Liberties thereof.

Information about this book

Title statement

VVhereas the Lord Generall hath received a message from the Committee for the Admirality, ...

Fowke, John, d. 1662.

Edition statement

1659

Publication

Publisher

Text Creation Partnership,

Place of publication

Ann Arbor, MI ; Oxford (UK) :

Date

2008-09 (EEBO-TCP Phase 1).

ID [DLPS]

A88480

ID [STC]

Wing L2883F

ID [STC]

Thomason 669.f.17[41]

ID [STC]

ESTC R211673

ID [EEBO-CITATION]

99870379

ID [PROQUEST]

99870379

ID [VID]

163290

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

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

Images scanned from microfilm: (Thomason Tracts ; 246:669f17[41])

Source

— VVhereas the Lord Generall hath received a message from the Committee for the Admirality, ..., Fowke, John, d. 1662..

Extent

1 sheet ([1] p.)

s.n.,. [London :: 1653]. (Title from opening lines of text.) (Dated and signed at end: Dated this 6 of August 1653. John Fowke Maior.) (Imprint from Wing.) (Reproduction of the original in the British Library.)

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.