Script fit
Latin
left-to-right · alphabet- Primary script only
Language coverage
Kurmanji is the most widely spoken Kurdish variety, yet decades of restricted public use across its primary geographies left the language with limited standardized written resources and significant regional variation. MoniSa's Kurmanji linguists are verified for the regional variant your readers use.
Medical interpretation deployment is the closest available match, with script, dialect, reviewer fit, and content type made explicit before scoping.
Latin LTR
Translation fit
Kurdish (Kurmanji) scope checkActive coverage is reviewed against audience, script, dialect, content type, and proof need before work is planned.
Language readiness
Script direction, dialect scope, service coverage, and proof context are checked before timing or reviewer assumptions get locked too early.
Coverage model
Kurmanji is the most widely spoken Kurdish variety, yet decades of restricted public use across its primary geographies left the language with limited standardized written resources and significant regional variation. MoniSa's Kurmanji linguists are verified for the regional variant your readers use.
Request a Kurdish Kurmanji Translation Quote
| Service line | Planning status | Dialect scope | Start path | Turnaround note |
|---|---|---|---|---|
| Translation and review | Active coverage | Northern, Southern, Diaspora | Brief review | Confirmed on brief |
| AI data annotation | Active coverage | Standard | Brief review | Confirmed on brief |
| Audio transcription | Active coverage | Northern Kurmanji | Brief review | Confirmed on brief |
| Subtitling | Active coverage | Standard | Brief review | Confirmed on brief |
| Dubbing | Active coverage | Northern | Brief review | Confirmed on brief |
Service fit, reviewer continuity, and turnaround are confirmed against the live brief before production begins.
Buyer need
For Kurdish (Kurmanji), the buyer risk is community-sensitive routing and reviewer continuity, not generic translation quality. MoniSa confirms script, dialect, reviewer, and service fit against the brief before production begins.
Service answer
Kurmanji belongs to the Western Iranian branch of the Indo-Iranian language family and is spoken by approximately 20 million people across Turkey, Syria, northern Iraq, and a large European diaspora. It uses a Latin-based alphabet developed by Jeladet Ali Bedirkhan in the 1930s, making it visually and structurally distinct from Sorani Kurdish's Perso-Arabic script. Kurmanji was banned from public use in Turkey between 1938 and 1991, which suppressed written standardization and created significant variation across regional dialects. Most NLP systems either conflate Kurmanji with Sorani or fail to handle its agglutinative verb morphology, making machine translation unreliable for professional use.
MoniSa confirms the reviewer path, review depth, and delivery timing for Kurdish (Kurmanji) in the project brief. Every assigned linguist is verified for the variety and domain your project needs. We publish coverage and review depth, not the routes we recruit through.
A media or human rights organization needs Kurmanji content
for audiences in Turkey, Syria, or the European diaspora, and the current vendor cannot source linguists who distinguish Kurmanji from Sorani or Central Kurdish
A healthcare program targets Kurmanji-speaking communities
in Europe or the Middle East and requires culturally adapted materials in Latin-script Kurdish, not Arabic-script Sorani
An NLP or AI project requires Kurmanji-language data
and existing annotation vendors lack linguists trained to handle Kurmanji's agglutinative morphology and limited parallel corpora
A multilingual program lists "Kurdish" as a target language
without specifying the variant — Kurmanji and Sorani are distinct languages in practice, and treating them as interchangeable produces unusable output
Our Kurdish (Kurmanji) translation process
All Kurmanji Kurdish work follows MoniSa's 3-layer review model: translator (domain-matched, Hawar Latin alphabet native), editor (bilingual accuracy and terminology adherence), proofreader or community validator (cultural and contextual review). Review depth is scoped to the language pair, task type, and buyer risk.
We map the regional variant before assigning, because Turkey-origin, Syria-origin, and European-diaspora readers carry different vocabulary preferences and register expectations shaped by different media. The brief also confirms this is Kurmanji, written in Latin script, and not Sorani, which uses a Perso-Arabic script, since treating the two as one produces output no audience can use.
Variant-matched linguists work in the Hawar Latin alphabet. Because Kurmanji has no single universally enforced written standard, a project style guide is set during onboarding to fix spelling and variant vocabulary, then held across the work. Editors review against that guide so the text stays internally consistent rather than mixing conventions.
Delivery includes the files and the review notes needed for acceptance, covering orthographic consistency and variant terminology. For programs spanning several Kurmanji-speaking regions, the versions are checked against each other for alignment. Any correction keeps its style-guide and variant decisions attached to the change.
Backup path
Verified Network status means backup Kurmanji reviewer coverage is confirmed within 5 business days.
Reviewer path
Quality metrics are identical for rare and high-resource languages. Review layers are not reduced based on linguist scarcity.
Sourcing status after scope
Sourcing path and review depth are confirmed in the project brief.
Live interpreting
Kurdish (Kurmanji) work reaches MoniSa mainly as written material, and a spoken request is the exception rather than the rule. When one does arrive it is scoped as its own piece of work rather than folded into a translation quote, because the unit, the screening and the delivery are all different.
Interpreting in Kurdish (Kurmanji) means a qualified interpreter renders a live conversation between Kurdish (Kurmanji) and another language, delivered in one of three ways: on an audio call, over a video link, or in the room. It is not translation. Translation produces a written deliverable and is quoted on volume, file type and review depth; interpreting is a live event with a date, a duration and a setting, and is booked as time. That is also how the two appear on a quote, with content on one line and time on the other, so a matter that needs both is scoped as two pieces of work rather than one. MoniSa sources and screens interpreters across 300+ languages and 4,500+ dialects from its network of 110,000+ verified language specialists, and operates under ISO 9001 and ISO 27001 certification.
Screening for a Kurdish (Kurmanji) session starts with the variety the speaker actually uses, because a near match is not a match once a conversation is under way. The interpreter is then checked in the working pair and screened against the setting the session comes from, so a clinical encounter, a legal proceeding and a school meeting count as separate qualifications rather than one. Everyone assigned signs the confidentiality agreement before receiving access, and named backup coverage is recorded alongside the primary assignment. What MoniSa publishes is the coverage and the screening, never the routes it recruits through.
Audio line
An audio line connects faster than any other modality, which makes it the right route for short, unscheduled exchanges such as an intake call, a benefits query, or an appointment booking, where nothing visual carries meaning.
Over-the-phone interpretationVideo link
A live video link is used when a document, a device, a physical examination or a signed language is part of the conversation, and when the people in the room and the interpreter need to see each other without anyone travelling.
Video remote interpretingClinical setting
A clinical encounter adds a credential requirement and a domain screen on top of the language check, because a summarised symptom or a softened instruction changes the care that follows.
Medical interpreter servicesRelated proof
Medical interpretation deployment is the closest available match, with script, dialect, reviewer fit, and content type made explicit before scoping.
Related case study
Healthcare communication controls and conflict-sensitive reviewer routing.
Buyer questions
The questions buyers send before a scope conversation, answered on the page rather than in a meeting. Take them to your team, then send us the one we did not answer.
Kurmanji uses a Latin-based alphabet and is spoken primarily in Turkey, Syria, and the European diaspora. Sorani uses a Perso-Arabic script and is centered in Iraq and Iran. They are mutually intelligible only to a limited degree. Specifying the correct variant is essential — treating them as one language produces unusable translations.
Yes. Kurmanji reviewer availability is confirmed at scope, before a timeline is agreed. These are professionally trained linguists working in stable digital environments with access to standardized Kurmanji reference materials and active Kurdish media institutions.
Kurmanji lacks a single enforced written standard. We establish project-specific style guides during onboarding that define orthographic conventions, variant-specific vocabulary, and register expectations. These guides are enforced across all production work and validated during the editorial review layer.
We source Kurmanji and Sorani linguists independently through separate verified networks. Each language receives its own linguist team, style guide, and review workflow. Cross-variant consistency checks are available for programs that need terminological alignment between both Kurdish varieties.
Translation is written: a document, a record, a subtitle track, delivered as content and quoted on volume and review depth. Interpreting is spoken: a live conversation on the phone, over video or in the room, booked as time with a date attached. A hearing, an appointment or a call needs an interpreter; a form, a notice or a record needs a translation, and most matters need both. MoniSa scopes them separately, because the sourcing, the screening and the unit of work differ, and confirms which one the brief actually needs before quoting.
You are told before a date is agreed, not after. Coverage is reported pair by pair as staffed today or needing a recruitment window, with the window stated — in writing, while the scope is still being agreed. Nobody new goes onto live work until a pilot batch has been reviewed and signed off. A coverage claim you cannot check before signing is not coverage.
Next step
A useful brief names the language, content, deadline, review depth, and proof the buying team needs.
Production-ready brief
01Language pair, dialect, and script02Content or data type03Volume and deadline04QA and reviewer requirement05Security and access requirement06Proof needed for buyer approval