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