Show Summary Details

Page of

PRINTED FROM OXFORD HANDBOOKS ONLINE (www.oxfordhandbooks.com). (c) Oxford University Press, 2015. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Handbooks Online for personal use (for details see Privacy Policy).

date: 17 October 2017

Abstract and Keywords

Sir Thomas Smith and William Bullein were the most accomplished dialogue writers of their generation. Both men were humanists and moralists, who used dialogue in innovative and stylistically striking ways. They were also proponents of ‘commonwealth’ who examined the limits and possibilities of ‘counsel’ in their respective fields of expertise. Furthermore, while Smith affirmed the potential of ‘discourse’ and ‘counsel’ to resolve dissension and establish an acceptable truth among self-interested parties, Bullein came to suggest the opposite: that eloquence and knowledge were dangerous tools to be manipulated for private interest and profit. In this way, their work illustrates the contrasting scribal and commercial audiences to which dialogues could be directed as well as the different kinds of knowledge the form could bear. Perhaps most importantly, they suggest two trajectories of the English humanist project as it had developed by 1560: the idealistic faith in the power of rhetoric to identify and serve the public good; and the more pessimistic intimation that not only was the ‘new learning’ socially ineffectual, but in the wrong hands it actively corroded commonwealth.

Keywords: dialogue writers, humanists, moralists, commonwealth

Access to the complete content on Oxford Handbooks Online requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can''t find the answer there, please contact us.