Serbian (српски) review centers on this evidence: verify Serbian script consistency, dialect-standard forms, clitic order, inflected names, and neighboring-language passages. The Cyrl value for sr comes from CLDR likely-subtag expansion. It guides locale fallback; audio has no script, and Serbian still needs a project choice. Serbian uses both Cyrillic and Latin in current practice; the bare sr tag does not choose one for the project. Orthographic targets include letter choices, inflected endings, proper names, and transliterated foreign terms. Project decision: whether Serbian Cyrillic or Latin is required, plus Ekavian or Ijekavian treatment. Before batch editing sr, a reviewer must record whether Serbian Cyrillic or Latin is required, plus Ekavian or Ijekavian treatment and attach a source timestamp to disputed text.
Where this workflow fits
- Serbian interviews and oral histories
- Serbian lectures and training recordings
- Source-linked Serbian research review
Serbian orthography and speech checkpoints
verify Serbian script consistency, dialect-standard forms, clitic order, inflected names, and neighboring-language passages. Editorial decision: whether Serbian Cyrillic or Latin is required, plus Ekavian or Ijekavian treatment. Visual inspection should cover record the project decision about whether Serbian Cyrillic or Latin is required, plus Ekavian or Ijekavian treatment.
Script choice and source-linked review for српски
The Cyrl value for sr comes from CLDR likely-subtag expansion. It guides locale fallback; audio has no script, and Serbian still needs a project choice. Serbian uses both Cyrillic and Latin in current practice; the bare sr tag does not choose one for the project. For interviews containing rich inflection, clitics, place names, and code-switching, inspect verify Serbian script consistency, dialect-standard forms, clitic order, inflected names, and neighboring-language passages. Visually inspect letter choices, inflected endings, proper names, and transliterated foreign terms; record the project decision about whether Serbian Cyrillic or Latin is required, plus Ekavian or Ijekavian treatment. 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 sr hint maps to the reviewed sr provider root and preserves sr as the user's transcript language tag.
- CLDR Cyrl 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 sr · tiers fast, standard, precision
- Automatic detection
- Reviewed no
- Diarization
- Reviewed no
- Word timestamps
- Reviewed yes
Questions from the workflow
What must a Serbian editor decide before correcting the transcript?
case endings, aspect-bearing forms, short clitics, names, and dialect-to-standard decisions should be checked across clause boundaries. For Serbian, verify Serbian script consistency, dialect-standard forms, clitic order, inflected names, and neighboring-language passages. Project choice: whether Serbian Cyrillic or Latin is required, plus Ekavian or Ijekavian treatment. 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
- Serbian language and orthography editorial reference · checked 2026-07-20
- World Atlas of Language Structures Online · checked 2026-07-20