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: 19 November 2017

Abstract and Keywords

The genesis of African American Vernacular English (AAVE) has been contested territory for decades, marked by a heated debate between adherents of “creolist” and “dialectologist” explanations of its origin. While early scholarship had hardly any factual documentation to test these hypotheses, new resources documenting Earlier African American English usage have been unearthed since then. This chapter surveys these text types and sources as well as their contribution to our understanding of the diachrony of AAVE. The resources focused on include the WPA ex-slave narratives, the Library of Congress ex-slave recordings, Hyatt’s “hoodoo” transcripts, studies of diaspora varieties (notably from Samaná), historical corpora of letters written by semi-literate writers, and transcripts of early blues lyrics. Results imply that a simple dichotomy cannot do justice to the issue in question. The chapter concludes with a call for recognition of the internal heterogeneity of AAVE and its history and of compromise origins positions.

Keywords: dialect history, Blues lyrics, African American Vernacular English (AAVE), early African American English, WPA ex-slave narratives, semi-literate writers, Hyatt’s “hoodoo” transcripts, diaspora varieties

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.