Uzbek (o‘zbek) review centers on this evidence: inspect Uzbek apostrophe letters, suffixes, names, Russian borrowings, and script-consistent spelling after the project choice. CLDR expansion gives uz a likely Latn default (Latin script). Never reinterpret that web-locale fallback as detected recording metadata or Uzbek’s sole script. Uzbek projects may require Latin, Cyrillic, or Arabic-script conventions. Orthographic targets include diacritics, word boundaries, proper names, number expressions, and code-switched terms. Project decision: whether Latin, Cyrillic, or Arabic-script Uzbek is required by the audience. Before batch editing uz, a reviewer must record whether Latin, Cyrillic, or Arabic-script Uzbek is required by the audience and attach a source timestamp to disputed text.
Where this workflow fits
- Uzbek interviews and oral histories
- Uzbek lectures and training recordings
- Source-linked Uzbek research review
Uzbek orthography and speech checkpoints
inspect Uzbek apostrophe letters, suffixes, names, Russian borrowings, and script-consistent spelling after the project choice. Editorial decision: whether Latin, Cyrillic, or Arabic-script Uzbek is required by the audience. Visual inspection should cover record the project decision about whether Latin, Cyrillic, or Arabic-script Uzbek is required by the audience.
Script choice and source-linked review for o‘zbek
CLDR expansion gives uz a likely Latn default (Latin script). Never reinterpret that web-locale fallback as detected recording metadata or Uzbek’s sole script. Uzbek projects may require Latin, Cyrillic, or Arabic-script conventions. For cross-regional recordings with long suffix chains and borrowed names, inspect inspect Uzbek apostrophe letters, suffixes, names, Russian borrowings, and script-consistent spelling after the project choice. Visually inspect diacritics, word boundaries, proper names, number expressions, and code-switched terms; record the project decision about whether Latin, Cyrillic, or Arabic-script Uzbek is required by the audience. 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 uz hint maps to the reviewed uz provider root and preserves uz as the user's transcript language tag.
- CLDR Latn 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 uz · tiers fast, standard, precision
- Automatic detection
- Reviewed no
- Diarization
- Reviewed no
- Word timestamps
- Reviewed yes
Questions from the workflow
What must a Uzbek editor decide before correcting the transcript?
vowel harmony cues, suffix boundaries, names, and Russian-, Persian-, or English-derived vocabulary should follow the chosen orthography. For Uzbek, inspect Uzbek apostrophe letters, suffixes, names, Russian borrowings, and script-consistent spelling after the project choice. Project choice: whether Latin, Cyrillic, or Arabic-script Uzbek is required by the audience. 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
- Uzbek language and orthography editorial reference · checked 2026-07-20
- World Atlas of Language Structures Online · checked 2026-07-20