The Chronicle of Walter of Guisborough: Previously Edited as the Chronicle of Walter of Hemingford or Hemingburgh

The Chronicle of Walter of Guisborough: Previously Edited as the Chronicle of Walter of Hemingford or Hemingburgh

The Chronicle of Walter of Guisborough: Previously Edited as the Chronicle of Walter of Hemingford or Hemingburgh

The Chronicle of Walter of Guisborough: Previously Edited as the Chronicle of Walter of Hemingford or Hemingburgh

Excerpt

In a work of this nature one becomes, if one is fortunate, as I have been, indebted to many friends and friendly institutions. I hope none will be disappointed that I cannot mention all by name. With all in mind I give general thanks.

Most of the many manuscripts I have had to consider are in the great institutions which are the scholar's places of common resort, but one is not less grateful for the efficiency and the courtesy (self-sacrificing courtesy) of their officials because one does not always mention them. Manuscripts in private custody have not been denied me either, and I am particularly grateful to the Rt. Hon. the Earl of Dalhousie of Brechin Castle for permission to examine his eighteenth-century transcript of the manuscript in the National Library of Scotland (and to the good offices in the matter of Mr. C. T. McInnes, Curator of Historical Records, The General Register House, Edinburgh); to the Inner Temple Library and its Librarian, Mr. E. A. P. Hart, for access to the Petyt MS. More even than previous editors of the chronicle, I am indebted to the College of Arms -- for access to MS. N.5 as well as A1 (MS. N.13). I look back, as I finish my work, with particular pleasure to hours spent in the Library of Trinity College, Cambridge. My greatest debt of all is to the Royal Historical Society for publishing my work and to the University of Southampton for a generous grant towards the extra cost of publishing it as I wanted it.

H. ROTHWELL. 14 May, 1957.

SOUTHAMPTON.

Author Advanced search

Oops!

An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.