Middle East & North Africa · Arabic / Latin
Kurdish Speech Translation Dataset
Kurdish speech translation sourced to your specification — no inventory, no fixed listing. This page covers what is specifically hard about this pairing, and which fields your specification needs to pin down.
Why speech translation in Kurdish is its own problem
Kurdish speech translation starts with two choices that are easy to get wrong. The source audio is in one branch, and the translator has to be matched to it — a Sorani translator working on Kurmanji audio will produce confident but wrong output, since the two do not cross-communicate. The source transcript then has to be written in a fixed script, and the translation has to decide what to do with state-language segments inside the audio: translate them, keep them, or tag them. All three decisions shape the delivered pairs, and none can be recovered after the fact.
The field to pin down first: The source branch, the transcript script, and the rule for state-language segments are all fixed before translation begins, and translators are branch-matched to the audio they handle.
At a glance
| Language | Kurdish |
|---|---|
| Primary region | Middle East & North Africa |
| Writing system | Arabic / Latin |
| Category | Speech Translation |
| Specification field to settle first | The source branch, the transcript script, and the rule for state-language segments are all fixed before translation begins, and translators are branch-matched to the audio they handle. |
| Delivery | Sourced to order, pilot batch before the full run |
What speech translation data is
Parallel data pairing source-language audio with target-language translation, used for speech-to-text and speech-to-speech translation models.
What buyers get wrong about it
Speech translation data needs all three components: audio, source-language transcription, and target-language translation. Miss one and it cannot be trained on — many suppliers deliver only two.
The specification field that decides the quote
Whether the translation is human or machine translation with human post-editing — cost and quality differ by an order of magnitude.
The language side: what Kurdish demands
The two main branches of Kurdish (Sorani and Kurmanji) have low mutual intelligibility, close to two separate languages, and they use different scripts. Public resources are so thin that even TTS datasets are rare — a textbook scarce language.
What we can put in this delivery
-
Read and conversational speech
Scripted recording for TTS, and unscripted conversation for recognition. Specified separately because they need different speaker pools.
-
Transcription to your convention
Orthographic or phonetic, with the guideline written before production and shared with you for review.
-
Speaker metadata
Age band, gender, region and dialect background per file, so you can slice the dataset rather than take it whole.
-
Consent documentation
Signed speaker consent covering the intended use, plus collection methodology and the annotation guideline.
-
Pilot batch
A small batch first, which you can reject. Misalignments surface after a few hours rather than at delivery.
-
Delivery in your format
Audio format, sampling rate, segmentation length and metadata schema set to your pipeline's requirements.
What arrives in a delivery
| Component | What it is |
|---|---|
| Audio files | Format, sampling rate and segmentation length set to your pipeline. Named to a convention you specify. |
| Transcription | Orthographic or phonetic, produced under a guideline you review before production starts. |
| Speaker metadata | Age band, gender, region and dialect background per file, plus a speaker identifier so the dataset can be sliced. |
| Recording conditions | Environment, device and, where relevant, measured signal-to-noise ratio per file. |
| Annotation guideline | The document the annotators worked from, so you can reproduce the conventions on your own data. |
| Consent records | Signed speaker consent covering your intended use, with the transfer mechanism addressed where required. |
| Collection methodology | How speakers were recruited, screened and scheduled — the part that tells you how biased the pool is. |
| Quality report | Pilot outcome, re-work log, and the annotator agreement figures where the task supports measuring them. |
Questions we get about Kurdish Speech Translation
How many distinct speakers can you provide for Kurdish Speech Translation?
It depends on the specification and the timeline, and we will give a real number rather than a target. For this pairing, speaker recruitment is usually the step that sets the schedule. The source branch, the transcript script, and the rule for state-language segments are all fixed before translation begins, and translators are branch-matched to the audio they handle.
Can you annotate to our own guideline instead of the default?
Yes, and for this pairing we would recommend it. Kurdish speech translation starts with two choices that are easy to get wrong. That is exactly the kind of decision a default guideline leaves open, and it is where annotators diverge. Send us your guideline, or we will draft one and you can review it before production starts.
Do you offer a sample before we commit to a full run?
Yes. Select a free sample in the request form and describe what you need. A pilot batch is the cheapest way to establish whether the quality bar is reachable for Kurdish Speech Translation before committing to the full volume.
Is the data licensed or owned outright?
Licensing terms are set per project, so tell us how the model will be used and whether it will be distributed. Consent documentation travels with the data either way, and we do not handle medical or clinical data or recorded telephone calls.
Other datasets in Kurdish
-
Kurdish Podcast Speech
Long-form podcast and interview audio, either solo monologue or two-person conversation, used for long-form speech recognition and speaker modeling.
-
Kurdish Multilingual Speech
Speech data covering multiple languages within one project, used for multilingual ASR, cross-lingual transfer, and language identification.
-
Kurdish Noisy Speech
Speech collected under background noise — street, in-car, restaurant, office and other real environments — used for noise-robust models and speech enhancement.
-
Kurdish Code-Switching Speech
Speech that mixes two or more languages inside a single utterance — Hinglish, Spanglish, Taglish — used for recognition in real spoken settings.
-
Kurdish Children Speech
Speech data from child speakers, grouped by age band, used for children's speech recognition and children's education products.
-
Kurdish Audiobook
Continuous long-form narration in audiobook style, steady in intonation and generous in duration, the main source material for high-quality TTS.
Speech Translation in other languages
-
Vietnamese Speech Translation
Southeast Asia
-
Filipino Speech Translation
Southeast Asia
-
Persian Speech Translation
Middle East & North Africa
-
Tamil Speech Translation
South Asia
-
Telugu Speech Translation
South Asia
-
Malayalam Speech Translation
South Asia
Request Kurdish Speech Translation
Tell us the language, the hours, and what the data needs to look like. You will get a real number and a real timeline — not a range. If we cannot source it well, we will tell you that instead.
- Pilot batch before the full run, so problems surface early.
- Consent documentation delivered with the data.
- No medical or clinical data. No recorded telephone calls.