Shona (chiShona) review centers on this evidence: review Shona noun-class prefixes, agreement, vowel sequences, names, ideophones, and English code-switching. CLDR expansion gives sn a likely Latn default (Latin script). Never reinterpret that web-locale fallback as detected recording metadata or Shona’s sole script. Confirm the actual orthography and script with the project owner before normalizing any text. Orthographic targets include diacritics, word boundaries, proper names, number expressions, and code-switched terms. Project decision: whether tone or dialect detail is annotated beyond standard Shona spelling. Before batch editing sn, a reviewer must record whether tone or dialect detail is annotated beyond standard Shona spelling and attach a source timestamp to disputed text.
Where this workflow fits
- Shona interviews and oral histories
- Shona lectures and training recordings
- Source-linked Shona research review
Shona orthography and speech checkpoints
review Shona noun-class prefixes, agreement, vowel sequences, names, ideophones, and English code-switching. Editorial decision: whether tone or dialect detail is annotated beyond standard Shona spelling. Visual inspection should cover record the project decision about whether tone or dialect detail is annotated beyond standard Shona spelling.
Script choice and source-linked review for chiShona
CLDR expansion gives sn a likely Latn default (Latin script). Never reinterpret that web-locale fallback as detected recording metadata or Shona’s sole script. Confirm the actual orthography and script with the project owner before normalizing any text. For community research where noun-class agreement and code-switching carry meaning, inspect review Shona noun-class prefixes, agreement, vowel sequences, names, ideophones, and English code-switching. Visually inspect diacritics, word boundaries, proper names, number expressions, and code-switched terms; record the project decision about whether tone or dialect detail is annotated beyond standard Shona spelling. 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 sn hint maps to the reviewed sn provider root and preserves sn 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 sn · tiers fast, standard, precision
- Automatic detection
- Reviewed no
- Diarization
- Reviewed no
- Word timestamps
- Reviewed yes
Questions from the workflow
What must a Shona editor decide before correcting the transcript?
noun-class prefixes, agreement markers, names, and borrowed terms must stay connected to surrounding words; ordinary spelling may omit tonal detail. For Shona, review Shona noun-class prefixes, agreement, vowel sequences, names, ideophones, and English code-switching. Project choice: whether tone or dialect detail is annotated beyond standard Shona spelling. 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
- Shona language and orthography editorial reference · checked 2026-07-20
- World Atlas of Language Structures Online · checked 2026-07-20