| The wrong variety or script | Kurmanji (Latin) and Sorani (Arabic script) are barely mutually readable. Treat one as the other and the text is unusable. | We establish the variety and script first — Kurmanji, Sorani or Zazaki — and assign a specialist for exactly that. |
| Kurmanji gender and oblique case | Kurmanji marks grammatical gender and an oblique case; Sorani does not. Carry Sorani habits into Kurmanji (or vice versa) and the forms break. | We write from the grammar of the specific variety, with gender and case set correctly. |
| The ergative past in Kurmanji | In the Kurmanji past tense of transitive verbs the agent stands in the oblique — an ergative pattern with no German parallel. Rebuilt as a plain subject, the sentence inverts. | The ergative construction is rendered correctly, so who did what to whom stays clear. |
| Zazaki treated as Kurmanji | Zazaki (Zaza-Gorani) is linguistically its own language. Handle it as Kurmanji and the result is wrong at every level. | Where a document is Zazaki, we treat it as Zazaki, not as a Kurmanji dialect. |
| Missing q, w, x in names | The Turkish alphabet has no q, w or x, so Turkish-issued documents spell Kurdish names without them. Copied literally, the name diverges from its Kurdish form. | Names are restored to their correct Kurdish spelling and reconciled with the passport, with the divergence explained where an office needs it. |
| Sorani script details | Sorani uses Arabic-based characters adapted for Kurdish. Set with the wrong glyphs or joins, words and names are misread. | We use the correct Sorani characters and joining, so the script is right, not approximated. |
| A document that is not in Kurdish | A birth certificate “from a Kurdish region” is officially often Turkish, Arabic or Persian. Assume it is Kurdish and the wrong specialist is assigned. | We identify the actual source language first and translate that, with the right certified specialist. |