Skip to main content Accessibility help
×
Hostname: page-component-7479d7b7d-767nl Total loading time: 0 Render date: 2024-07-11T05:24:55.447Z Has data issue: false hasContentIssue false

4 - The Yale Gower Manuscript, Beinecke Osborn MS fa.1: Paleographical, Codicological, Technological Challenges and Opportunities

from I - Manuscripts

Published online by Cambridge University Press:  05 August 2014

Barbara A. Shailor
Affiliation:
Yale University
Ana Sáez-Hidalgo
Affiliation:
Associate Professor at the University of Valladolid, Spain
R. F. Yeager
Affiliation:
Professor of English and World Languages and chair of the department at the University of West Florida
Get access

Summary

History of the manuscript

Early on in my career, in the late 1970s, Stephen Parks, then the Curator of the Osborn Collection in the Beinecke Rare Book and Manuscript Library, asked me to consider the possibility of cataloging the Osborn early manuscript collection. When I went to the library stacks and pulled out Osborn MS fa.1 (the official call number of the Gower manuscript under discussion) I was astounded by two things: first, the terrible smell that drifted my way upon removing the codex from its slip case, and second, the degree of what looked to be mildew damage that the parchment had experienced. Since this startling introduction to the manuscript, off and on, I have been intrigued with this codex and the various challenges it presents to scholars wishing to study it.

Stephen Parks quickly sent the volume off to the Cockerell studio in England to see if the mildew was still active; Sydney Cockerell kept the manuscript for two years, and in November 1979, wrote to Parks in a letter that is today in the Beinecke bibliographical files:

When the manuscript arrived here on December 31st, 1977, I drew round the mildew stains on verso 52 and recto 53 in pencil and there appears to be no change. The British Museum Research Laboratory had a look at the manuscript and the sample of the vellum from it that you sent to me and they were of the opinion that the staining was caused by mildew Dr. Lowring of the Biology Department of Cambridge University also had a look at a fragment and could not decide what the staining was caused by. He suggested that it might be chemical rather than a fungus and wanted to know the history of the manuscript.

Type
Chapter
Information
John Gower in England and Iberia
Manuscripts, Influences, Reception
, pp. 77 - 86
Publisher: Boydell & Brewer
Print publication year: 2014

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×