Basque (euskara) review centers on this evidence: review case suffixes, auxiliary sequences, ergative marking, place names, and Spanish or French insertions in context. For underspecified eu, CLDR supplies Latn (Latin script) as a likely/default web-locale hint—not an audio attribute or exclusive Basque orthography. 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 regional forms remain verbatim or are normalized to standard Basque. Before batch editing eu, a reviewer must record whether regional forms remain verbatim or are normalized to standard Basque and attach a source timestamp to disputed text.
Where this workflow fits
- Basque interviews and oral histories
- Basque lectures and training recordings
- Source-linked Basque research review
Basque orthography and speech checkpoints
review case suffixes, auxiliary sequences, ergative marking, place names, and Spanish or French insertions in context. Editorial decision: whether regional forms remain verbatim or are normalized to standard Basque. Visual inspection should cover record the project decision about whether regional forms remain verbatim or are normalized to standard Basque.
Script choice and source-linked review for euskara
For underspecified eu, CLDR supplies Latn (Latin script) as a likely/default web-locale hint—not an audio attribute or exclusive Basque orthography. Confirm the actual orthography and script with the project owner before normalizing any text. For regional interviews containing Spanish or French names and switches, inspect review case suffixes, auxiliary sequences, ergative marking, place names, and Spanish or French insertions in context. Visually inspect diacritics, word boundaries, proper names, number expressions, and code-switched terms; record the project decision about whether regional forms remain verbatim or are normalized to standard Basque. 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 eu hint maps to the reviewed eu provider root and preserves eu 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 eu · tiers fast, standard, precision
- Automatic detection
- Reviewed no
- Diarization
- Reviewed no
- Word timestamps
- Reviewed yes
Questions from the workflow
What must a Basque editor decide before correcting the transcript?
long case-marked forms, auxiliaries, names, and neighboring-language insertions should remain tied to grammatical context. For Basque, review case suffixes, auxiliary sequences, ergative marking, place names, and Spanish or French insertions in context. Project choice: whether regional forms remain verbatim or are normalized to standard Basque. 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
- Basque language and orthography editorial reference · checked 2026-07-20
- World Atlas of Language Structures Online · checked 2026-07-20