The Annotator: The Pursuit of an Elizabethan Reader of Halle's Chronicle Involving Some Surmises about the Early Life of William Shakespeare

The Annotator: The Pursuit of an Elizabethan Reader of Halle's Chronicle Involving Some Surmises about the Early Life of William Shakespeare

The Annotator: The Pursuit of an Elizabethan Reader of Halle's Chronicle Involving Some Surmises about the Early Life of William Shakespeare

The Annotator: The Pursuit of an Elizabethan Reader of Halle's Chronicle Involving Some Surmises about the Early Life of William Shakespeare

Excerpt

It is over ten years since the start of investigations into the mystery of who wrote in the margin. The claim here advanced is that the writer was William Shakespeare. The reader's patience is invited, for he must suffer himself to be entangled in the network of Shakespearian connexions in order to appreciate our contention that the writer of the marginalia in the Newport copy of Halle's Chronicle was the young Shakespeare. Our exploration will endeavour to show the signposts in the progress of the fourteen-year-old boy, who, we believe, did not leave his native Stratford to hold horses' heads outside the Bankside playhouses, but was occupied in an environment and with associations more likely to encourage literary and historical inventiveness.

Those who have followed Alan Keen's researches since 1940 from the occasional bulletins that have appeared in the press, may recall how several years ago he declared that the apparent dissimilarity in form between the marginalia and Shakespeare's acknowledged signatures had convinced him that the notes could not, in fact, have been made by Shakespeare. Expert opinion which we now quote has since shown that conclusion to have been premature.

We include in the Appendices, by kind permission of the author, an analysis by A. P. Rossiter of what Shakespearian scholars might expect to find in marginal notes made by the young Shakespeare.

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.