Belarusian (беларуская) review centers on this evidence: check ў, apostrophes, inflected endings, names, and genuinely Belarusian forms that a Russian-looking draft may flatten. The Cyrl value for be comes from CLDR likely-subtag expansion. It guides locale fallback; audio has no script, and Belarusian still needs a project choice. Confirm the actual orthography and script with the project owner before normalizing any text. Orthographic targets include letter choices, inflected endings, proper names, and transliterated foreign terms. Project decision: which Belarusian standard and treatment of Russian code-switching is approved. Before batch editing be, a reviewer must record which Belarusian standard and treatment of Russian code-switching is approved and attach a source timestamp to disputed text.
Where this workflow fits
- Belarusian interviews and oral histories
- Belarusian lectures and training recordings
- Source-linked Belarusian research review
Belarusian orthography and speech checkpoints
check ў, apostrophes, inflected endings, names, and genuinely Belarusian forms that a Russian-looking draft may flatten. Editorial decision: which Belarusian standard and treatment of Russian code-switching is approved. Visual inspection should cover record the project decision about which Belarusian standard and treatment of Russian code-switching is approved.
Script choice and source-linked review for беларуская
The Cyrl value for be comes from CLDR likely-subtag expansion. It guides locale fallback; audio has no script, and Belarusian still needs a project choice. Confirm the actual orthography and script with the project owner before normalizing any text. For interviews containing rich inflection, clitics, place names, and code-switching, inspect check ў, apostrophes, inflected endings, names, and genuinely Belarusian forms that a Russian-looking draft may flatten. Visually inspect letter choices, inflected endings, proper names, and transliterated foreign terms; record the project decision about which Belarusian standard and treatment of Russian code-switching is approved. 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 be hint maps to the reviewed be provider root and preserves be 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 be · tiers fast, standard, precision
- Automatic detection
- Reviewed no
- Diarization
- Reviewed no
- Word timestamps
- Reviewed yes
Questions from the workflow
What must a Belarusian 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 Belarusian, check ў, apostrophes, inflected endings, names, and genuinely Belarusian forms that a Russian-looking draft may flatten. Project choice: which Belarusian standard and treatment of Russian code-switching is approved. 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
- Belarusian language and orthography editorial reference · checked 2026-07-20
- World Atlas of Language Structures Online · checked 2026-07-20