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: 18 April 2019

Abstract and Keywords

English dialects are generally classified as either rhotic or non-rhotic. Rhotic dialects produce /r/ non-prevocalically (for example, in sword, car, and heart). Non-rhotic dialects produce these words with no /r/, having abandoned the production of /r/ in non-prevocalic position at some stage in their history. The worldwide geographic distribution of non-rhotic dialects has often been ascribed to the later dates of settlement from Britain. The loss of rhoticity appears to have resulted in the emergence of a system of linking and intrusive /r/ in most dialects. Linking /r/ and intrusive /r/ are together known as “/r/-sandhi,” and are characteristic of most non-rhotic varieties of the English language. This article takes a narrow and specific view of rhoticity and non-rhoticity by focusing on what can be learned from an analysis of the history of New Zealand English. Recent work at the University of Canterbury has investigated various aspects of the loss of rhoticity in this dialect, along with the subsequent emergence of /r/-sandhi.

Keywords: rhoticity, New Zealand, English, dialects, /r/-sandhi, linking /r/, intrusive /r/, University of Canterbury, non-rhoticity, continua, linguistics

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.