Comparative Persian Dialectology for Readers

Comparative dialectology asks where linguistic features occur, how they pattern together, and what historical or contact processes may explain them. It does not begin by ranking named varieties. A map label such as “Gilaki,” “Luri,” “Kurdish,” “Central dialect,” or “regional Persian” is a hypothesis about related patterns; actual speech may form continua, transitional zones, and multilingual repertoires.

The broad classification and methodological vocabulary here follow Encyclopaedia Iranica’s Dialectology and its language-specific surveys. Iranian Persian remains the production target. Review that baseline in Iranian Regional Dialects versus Persian Accents.

An isogloss marks a feature, not a people

An isogloss is a line marking the geographical boundary between variants of one feature: a vowel outcome, a plural suffix, a copula form, a clitic position, or a past-tense alignment. Several isoglosses may bundle together, but they often cross. Political borders, provincial boundaries, and self-identification need not coincide with any one line.

Persian specialist writing commonly calls an isogloss مرز همگویی. Terminology can vary, so a study should still define what its mapped line represents.

Build a feature matrix before a family tree

For reading a grammar sketch, construct a matrix of comparable domains. “Same word” and “different word” are weak measures if the items occupy different grammatical slots.

Copula or pronoun? Distribution decides

In Iranian Persian, ـم in خوبم is first-person copula, while ـم in کتابم is a possessive clitic. Identical sound does not mean identical morpheme. Dialect descriptions must test which predicates, nouns, negators, and tense forms accept a suffix.

Do not compare isolated suffix lists. A form glossed “1SG” may encode subject agreement, copula, possessor, object, or past agent in different systems.

Clitic hosts reveal syntactic organization

Iranian languages vary in where pronominal clitics can attach and what role they express. A clitic may remain beside its semantic host, move to an earlier word in the clause, or occupy a preferred cluster position. The label “mobile” needs examples: mobility is normally constrained, not free.

The established Iranian Persian clitic system is the production baseline. A clitic pattern documented in a Caspian or Central Iranian variety is evidence for that system, not a template to import into Persian.

Past systems and alignment

Modern standard Persian uses a broadly nominative–accusative pattern in simple past clauses: the subject controls verbal person in both intransitives and transitives. Many Northwestern and Central Iranian varieties retain “split” past constructions in which a past transitive agent is oblique or represented by a pronominal clitic while the verb behaves differently. Iranica’s overview of case and alignment documents that contrast.

This does not mean such languages have a “passive past.” Older scholarship used “passive construction,” but modern alignment analysis asks how agent, patient, agreement, and tense interact. Iranica’s Central Dialects survey gives concrete examples of split past alignment and mobile agent clitics.

Evidentiality is not merely a tense translation

Perfect forms may mark a completed result, current relevance, inference, surprise, or reported information. In some contact areas, indirective/evidential contrasts are grammaticalized more strongly. Translating every such form as English “apparently” can hide whether the meaning belongs to morphology, a particle, discourse, or the researcher’s gloss.

Evidentiality claims require controlled contexts: direct witness, report, inference from results, dream, and unexpected discovery. A translation elicited without context is insufficient.

Data limits belong in the analysis

A century-old word list, one consultant, a translated questionnaire, and a recorded conversation answer different questions. State who spoke, when, where, to whom, and under what task. Negative evidence—“this form did not occur”—is meaningful only relative to corpus size and genre.

Ethical description

Consultants are speakers with rights, not containers of “pure dialect.” Record preferred language names, consent, access conditions, and whether publication could identify a vulnerable community. Do not dismiss code-switching as contaminated data; it may be the normal repertoire.

Common Mistakes

1. Drawing a language border from one form

2. Calling a past system passive from its English gloss

3. Generalizing beyond the sample

4. Treating code-switching as unusable noise

Key Takeaways

• An isogloss maps one feature; language boundaries require converging evidence.
• Compare functions and distributions, not isolated word shapes.
• Distinguish copula, possessor, object, and past-agent clitics.
• Past alignment and evidentiality require paradigms plus controlled contexts.
• Report sample limits, speaker labels, multilingual practice, and consent as part of the analysis.
• Keep Iranian Persian as the production baseline; other systems are evidence to understand, not forms to imitate casually.