A practical guide to identifying Kurdish source languages, distinguishing script from language, checking translated quotations and verifying text from historical newspaper scans.

Identify the source language precisely
A report described simply as Kurdish may reach readers through more than one language variety, alphabet or translation. Start with the original publication and record the language, date, author and route to the version being quoted. Glottolog 5.3 groups Northern, Central and Southern Kurdish under its Kurdish family node. [1] Its linguistic categories should be named as a catalogue’s classification, rather than treated as a test of cultural belonging. The previous article’s unqualified four-dialect list and unsupported speaker total have been removed.
An alphabet is not the same as a language
Inalco’s programme describes Kurmanji written in Latin script and Sorani written in Arabic-based script, with their own literary norms. [2] These are important contemporary conventions, not a rule that every historical text follows. The 1898 newspaper page above provides an immediate warning against identifying a text’s language solely from its alphabet. When citing a name, retain the spelling in the original source where possible, and explain any transliteration used for readers. A Latin-letter rendering alone does not turn a Sorani statement into a Kurmanji source.
Translation needs an auditable chain
For this site’s editorial work, the recommended record is the original statement, the person or organisation that issued it, the translator and any intermediate version. Translation and transliteration perform different jobs: one conveys meaning in another language, while the other renders writing in another script. Compare consequential words against the original and seek a competent speaker’s review when the meaning is uncertain. If only a translated summary is available, label it as a summary. Do not present reconstructed wording as a direct quotation or invent a dialect-specific meaning for a political term.
A source’s claim and the reporter’s finding are different
A multilingual report should preserve attribution as carefully as wording. Record whether a statement is an allegation, an organisation’s count, an official announcement or a finding supported by independent evidence. Keep the place and reporting period attached to numbers. An event date, a publication date and a translation’s upload date may differ. These are editorial checks proposed here, not findings from a survey of all Kurdish newsrooms. They replace the earlier page’s unsupported predictions that a new generation was becoming uniformly fluent across varieties.
Historical scans require checking against the page
Yaseen and Hassani’s 2024 preprint describes OCR work on pre-1950 Kurdish publications from the Zheen Center. The researchers assembled 1,233 transcribed line images and identified damage, unusual fonts and irregular spacing as obstacles. [3] Their abstract concerns a particular research dataset, not an accuracy guarantee for every newspaper. A responsible archive citation should retain the page image and identify the issue and page. Check names, dates and quotations against that image before reuse. Searchable text is an aid to reading; its apparent precision cannot substitute for checking what was actually printed.
Sources and further reading
- Glottolog 5.3, Kurdish, kurd1259; classification and Northern, Central and Southern Kurdish nodes.
- Inalco, Kurdish licence brochure, updated 29 August 2025, printed p.4; Kurmanji and Sorani scripts and literary norms.
- Blnd Yaseen and Hossein Hassani, Making Old Kurdish Publications Processable by Augmenting Available Optical Character Recognition Engines, 9 April 2024; public abstract, arXiv:2404.06101.
- Kurdistan newspaper, Cairo, 1898; historical public-domain front-page scan, Wikimedia Commons.