Journal article
Not Diane: the risk of error in Chaucerian classicism
- Abstract:
- When Chaucer, Lydgate, and their contemporaries made classical characters and classical allusions an important part of English poetry, they risked confusing scribes and readers. In the vein of recent studies of scribes as readers, this article explores the mistakes of scribes in copying and comprehending those details. In addition, this article explores the ways that poets’ phrasing implies awareness of those risks and seeks to mitigate them. The article thus presents the creation of the text as a coproduction between agents, which might be understood in the framework of pragmatics, the analysis of speech acts in social context. These problems in transmission, and the forestalling of them, first reveal how classicism, which later became a monumental tradition, was a risky interaction in some of its earliest phases in English poetry. Second, more briefly and tentatively, these problems suggest the risks of writing for scribal transmission in general.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Accepted manuscript, pdf, 605.9KB, Terms of use)
-
- Publisher copy:
- 10.1080/10412573.2017.1409962
Authors
- Publisher:
- Routledge
- Journal:
- Exemplaria More from this journal
- Volume:
- 29
- Issue:
- 4
- Pages:
- 331-348
- Publication date:
- 2018-03-23
- Acceptance date:
- 2017-10-15
- DOI:
- EISSN:
-
1753-3074
- ISSN:
-
1041-2573
- Keywords:
- Pubs id:
-
pubs:735492
- UUID:
-
uuid:40242898-b645-4060-a18e-444f884ec234
- Local pid:
-
pubs:735492
- Source identifiers:
-
735492
- Deposit date:
-
2017-10-15
Terms of use
- Copyright holder:
- Informa UK Limited, trading as Taylor & Francis Group
- Copyright date:
- 2018
- Notes:
- Copyright © 2018 Informa UK Limited, trading as Taylor & Francis Group. This is the accepted manuscript version of the article. The final version is available online from Routledge at: https://doi.org/10.1080/10412573.2017.1409962
If you are the owner of this record, you can report an update to it here: Report update to this record