Show Summary Details

Page of

PRINTED FROM OXFORD HANDBOOKS ONLINE (www.oxfordhandbooks.com). © Oxford University Press, 2018. 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 and Legal Notice).

date: 20 October 2018

Abstract and Keywords

It took time for literatures in the vernacular languages to acquire sufficient status to be preserved in writing and thus to develop beside and away from Latin, the language of the Vulgate and that of an already established literature, of scholarship and of science. In the cases of the Celtic and West-Germanic cultures in particular, Latin was a completely distinct language, which had to be learned. Accordingly, these cultures often provide the clearest examples of the interpenetration with Latin at all levels—linguistic, thematic, and aesthetic. An early secular example of a slightly different integration of Latin and the vernacular is found where Roman legal codification was applied to the customs of very different cultures. The Lombardic Edict of Rothar of 643 is in Latin, but it incorporates Germanic terms, sometimes in Latinised form and usually explained, though the integration is not always clear. Of major significance in the consideration of vernacular and Latin interaction is the sermon, that part of Church ritual where the vernacular was encouraged. The exemplary case of Otfrid's ninth-century German Gospel-poem offers a number of perspectives on the interaction of Latin and the vernacular.

Keywords: vernacular languages, Latin, Vulgate, Celtic culture, West-Germanic culture, Edict of Rothar, Otfrid

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.