Show Summary Details

Page of

PRINTED FROM OXFORD HANDBOOKS ONLINE ( © 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: 16 May 2021

Abstract and Keywords

This chapter summarizes some first neurolinguistic studies conducted in Persian, using patholinguistic data taken from monolingual and bilingual brain-damaged patients, as well as five first neuroimaging studies in healthy native speakers of Persian. The patholinguistic data are extracted from formal clinical linguistic assessments of a heterogeneous group of brain-damaged patients with different etiologies and brain lesion sites. The data are indicative of general agrammatic features of ‘syntactic simplification’ and ‘morphological regression’ reported in cross-language studies, along with language-particular agrammatic features in spoken and written modalities for Persian consequent to brain damage. The present patholinguistic data are also suggestive of a ‘non-unitary’ model of aphasia as a symptom complex phenomenon with disruptions of independent linguistic levels consequent to different lesion sites. The data are not supportive of independent production and comprehension language centres claimed in ‘classical model’ of brain and language but in support of new non-narrow localization brain–language models.

Keywords: neurolinguistics, clinical linguistic, Persian, language neuroimaging, aphasia, morphological regression, syntactic simplification

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.