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: 21 February 2019

Abstract and Keywords

Gathic Avestan, the earliest documented form of Old Iranian, had a rich case system typical of archaic Indo-European languages: three genders, eight cases in the singular, a six-term plural, and a four-term dual. Old Persian, a somewhat later stage of Old Iranian, had already begun some case syncretisation with the old dative merging into the genitive. By the very earliest stages of Middle Persian and Parthian, gender and the dual were already completely lost and further stages of case syncretisation yielded a two-case system: the null-marked Direct case versus the Oblique case derived from the original genitive. Reduction or loss of case throughout Iranian and the emergence of numerous innovations have led to a bewildering array of compensating strategies whose evolution can be characterised by the interplay of three axes/dimensions: the Reduction Axis, the Innovation Axis, and the Nominal-Pronominal Axis. This article discusses the evolution of case in West Iranian languages, focusing on floating clitics and word order.

Keywords: West Iranian languages, floating clitics, word order, case, loss, reduction, innovations, Reduction Axis, Innovation Axis, Nominal-Pronominal Axis

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.