Certified Kurdish Document Translation Services

Which Kurdish variety and script is on the document?

Kurmanji and Sorani need separate script-aware review, while country, issuer, language, and writing system remain distinct facts.

Kurmanji, also called Northern Kurdish, is commonly encountered in Latin script with letters such as ç, ê, î, ş, and û. Sorani, also called Central Kurdish, commonly appears as کوردی in an Arabic-derived right-to-left script. Kurdish also has Arabic and Cyrillic orthographic history, so no script alone proves a variety or even proves that a page is Kurdish.

Share the issuing country, document type, and any known variety, but the page itself controls identification. Badini or Behdini commonly falls within the Kurmanji continuum, yet we confirm the supplied record instead of assigning it from geography. Zazaki, Gorani/Hawrami, Southern Kurdish, and uncertain labels go to quote review for source-language and specialist confirmation rather than being silently folded into Sorani or Kurmanji.

Which Kurdish-region records need document-specific handling?

Iraq, KRG, and Türkiye records use different fields and layouts, and their place of issue never proves the document language.

Iraqi and KRG materials may include civil-status records, a Unified National Card, older identity material, birth, death, or marriage records, Copy of Entry 1957, family or residence records, passports, and police or court records. Türkiye-issued files may include Nüfus Kayıt Örneği, Formül A, diplomas, transcripts, employment records, financial papers, or personal records.

Any of these may be Kurdish, Arabic, Turkish, Persian, English, or mixed. Corpus translates the readable supplied content and preserves field relationships. Source labels must remain traceable. It does not issue, retrieve, amend, replace, certify the source, apostille, authenticate, or validate a record, seal, signature, QR code, or barcode.

How are Sorani right-to-left text and Kurdish letters preserved?

Sorani review preserves right-to-left order, joining, punctuation, digits, tables, and Kurdish code points against the source image.

Extended letters such as ڕ, ڵ, ۆ, ێ, ە, ژ, and ڤ must remain distinct even when an Arabic or Persian glyph looks similar. Unicode also records the two-WAW sequence وو for a Sorani long vowel. Substituting lookalikes, splitting joined text, reversing a table, or collapsing distinct code points can change a name, number, or field.

Mixed-direction records need field-level handling. A right-to-left heading can sit beside Latin identifiers, dates, or English annotations without changing their own order. We preserve row and column relationships, punctuation placement, and printed numeral forms. If font rendering or a damaged scan leaves a character unresolved, the translation marks that uncertainty instead of choosing a convenient Arabic, Persian, or Kurdish form.

How are Kurmanji Latin spelling and diacritics handled?

Kurmanji text keeps ç, ê, î, ş, and û, plus the source capitalization, spacing, punctuation, and printed pairings intact.

Diacritics distinguish Kurdish letters and are not decorative. Removing them or replacing every letter with an ASCII approximation can alter a name, place, or word. We preserve apostrophes, hyphens, initials, capitalization, line order, and bilingual labels exactly enough to keep each translated field traceable to the page.

A mixed Latin and Arabic-script record may contain Kurmanji, Sorani, Turkish, Arabic, Persian, or several languages. Each field is identified separately instead of treating all Latin text as Kurmanji or all right-to-left text as Sorani. A passport or recipient-controlled identifier may supply a supported Latin spelling for the same person, but it does not permit changes to dates, numbers, classifications, or other source facts.

How are Kurdish names and transliteration kept consistent?

Printed Kurdish and Latin spellings control name work; one variety-neutral transliteration is never invented for every orthography.

The Library of Congress Kurdish table separately addresses Roman, Cyrillic, and Arabic orthographies. We preserve printed name order, patronymics, titles, initials, spacing, and identifier spellings, then keep one source-supported rendering consistent across the packet. A matching passport or identity card can guide consistency only when it clearly refers to the same person.

Buyer-provided spelling may also guide the same identity when the source supports it, but it cannot override conflicting facts. Material variants remain visible or are flagged for review instead of being silently harmonized. This matters when a family packet mixes Sorani and Kurmanji records, older Cyrillic material, or Latin identifiers produced by different authorities. Quote review is the correct route when several records show materially different spellings or the recipient mandates a particular rendering.

What can OCR and poor scans get wrong?

Kurdish OCR can reverse Sorani text, lose dots, break وو, strip Kurmanji diacritics, and merge bilingual fields or tables.

Right-to-left OCR may reorder segments, detach stamp text, confuse ڕ, ڵ, ۆ, ێ, ە, ژ, or ڤ with Arabic or Persian forms, and misread digits or identifiers. Latin-script OCR can flatten ç, ê, î, ş, and û into different letters. Dense tables and mixed-direction lines can merge unrelated entries.

Send an original PDF or a straight, high-resolution color image with uncropped edges, every page, both sides, flat lighting, and visible stamps, seals, and QR or barcode panels. We compare OCR with the image rather than treating extracted text as authority. Unresolved content is marked, not guessed. Handwriting, damage, faint print, historical forms, clipped fields, dense tables, or several files go through Get a Quote before timing and scope are confirmed.

What does the recipient control?

The receiving agency controls copy type, recency, format, names, supporting evidence, and deadlines; translation cannot set those rules.

For USCIS, 8 CFR 103.2(b)(3) requires a full English translation certified as complete and accurate and certification that the translator is competent. Corpus provides certified written translation and a signed certificate; it does not promise acceptance, approval, or an immigration result. Buyers can review USCIS translation services and the birth-certificate guide.

Department of State country reciprocity pages describe availability, issuers, and formats. They do not prove that a page is Kurdish or guarantee that a recipient will accept a specific copy. Courts, schools, evaluators, employers, licensing bodies, banks, consulates, and agencies can impose different rules. Provide the current request, notice, or instructions before work starts; Corpus does not give legal or immigration advice or evaluate credentials.

Should the buyer start an order or request a quote?

Checkout fits a clear standard typed file; quote review fits any uncertainty about variety, script, condition, layout, scope, or recipient.

Use Start Your Order only for an eligible clear, complete, ordinary modern typed file with a known page count and no special recipient instructions. Choose Other, specify Kurdish, and add Sorani or Kurmanji when known. Eligible pages start at $19.99 per page, with standard 24-hour delivery only after scope confirmation.

Use named Kurdish on Get a Quote and state the variety and script when known for Zazaki, Gorani/Hawrami, Southern Kurdish, uncertain labels, handwriting, mixed languages, right-to-left tables, old or damaged records, stamps, seals, QR panels, multiple files, unclear page counts, unusual layouts, or recipient rules. A quote confirms scope; it does not authenticate a record or promise recipient acceptance.