Urdu (اردو) review centers on this evidence: review Urdu-specific Arabic-derived letters, izafat where written, right-to-left punctuation, names, numbers, and English spans. The Arab value for ur comes from CLDR likely-subtag expansion. It guides locale fallback; audio has no script, and Urdu still needs a project choice. Confirm the actual orthography and script with the project owner before normalizing any text. Orthographic targets include right-to-left punctuation, connected letter forms, optional vowel marks, and mixed-script spans. Project decision: which Urdu spelling, spacing, and transliteration conventions are authoritative. Before batch editing ur, a reviewer must record which Urdu spelling, spacing, and transliteration conventions are authoritative and attach a source timestamp to disputed text.
Where this workflow fits
- Urdu interviews and oral histories
- Urdu lectures and training recordings
- Source-linked Urdu research review
Urdu orthography and speech checkpoints
review Urdu-specific Arabic-derived letters, izafat where written, right-to-left punctuation, names, numbers, and English spans. Editorial decision: which Urdu spelling, spacing, and transliteration conventions are authoritative. Visual inspection should cover record the project decision about which Urdu spelling, spacing, and transliteration conventions are authoritative.
Script choice and source-linked review for اردو
The Arab value for ur comes from CLDR likely-subtag expansion. It guides locale fallback; audio has no script, and Urdu still needs a project choice. Confirm the actual orthography and script with the project owner before normalizing any text. For multilingual interviews with names, honorifics, and English code-switching, inspect review Urdu-specific Arabic-derived letters, izafat where written, right-to-left punctuation, names, numbers, and English spans. Visually inspect right-to-left punctuation, connected letter forms, optional vowel marks, and mixed-script spans; record the project decision about which Urdu spelling, spacing, and transliteration conventions are authoritative. Replay a complete clause around every uncertain name, quantity, interruption, or ending.
Frozen deployment boundary
This page is published only because its language is present in capability snapshot m10-2026-07-20.1. It does not extend that catalog or claim a measured accuracy score.
- The ur hint maps to the reviewed ur provider root and preserves ur as the user's transcript language tag.
- CLDR Arab is a likely/default locale hint, not an audio property; capability flags remain per language and model while editors confirm the project's real script and orthography.
Reviewed provider capability
assemblyai · universal-2
root ur · tiers fast, standard, precision
- Automatic detection
- Reviewed no
- Diarization
- Reviewed no
- Word timestamps
- Reviewed yes
Questions from the workflow
What must a Urdu editor decide before correcting the transcript?
vowel signs, consonant clusters, inflected forms, names, and borrowed speech should follow the selected standard rather than an automatic transliteration. For Urdu, review Urdu-specific Arabic-derived letters, izafat where written, right-to-left punctuation, names, numbers, and English spans. Project choice: which Urdu spelling, spacing, and transliteration conventions are authoritative. Keep unresolved forms beside their source timestamps.
Reviewed sources
- IANA Language Subtag Registry · checked 2026-07-20
- AssemblyAI model and supported-language documentation · checked 2026-07-20
- AssemblyAI pre-recorded audio supported languages · checked 2026-07-20
- Unicode CLDR likely-subtags language and script data · checked 2026-07-20
- Urdu language and orthography editorial reference · checked 2026-07-20
- World Atlas of Language Structures Online · checked 2026-07-20