Punjabi (ਪੰਜਾਬੀ) review centers on this evidence: verify Punjabi vowel signs or Arabic-derived letters, tonal spelling cues, names, honorifics, and Punjabi–English switches after choosing a script. CLDR expansion gives pa a likely Guru default (Gurmukhi script). Never reinterpret that web-locale fallback as detected recording metadata or Punjabi’s sole script. Punjabi requires an explicit Gurmukhi-versus-Shahmukhi decision; the bare pa tag does not choose the project’s region or script. Orthographic targets include vowel signs, consonant combinations, names, number forms, and code-switching. Project decision: whether Gurmukhi or Shahmukhi Punjabi and which regional standard is required. Before batch editing pa, a reviewer must record whether Gurmukhi or Shahmukhi Punjabi and which regional standard is required and attach a source timestamp to disputed text.
Where this workflow fits
- Punjabi interviews and oral histories
- Punjabi lectures and training recordings
- Source-linked Punjabi research review
Punjabi orthography and speech checkpoints
verify Punjabi vowel signs or Arabic-derived letters, tonal spelling cues, names, honorifics, and Punjabi–English switches after choosing a script. Editorial decision: whether Gurmukhi or Shahmukhi Punjabi and which regional standard is required. Visual inspection should cover record the project decision about whether Gurmukhi or Shahmukhi Punjabi and which regional standard is required.
Script choice and source-linked review for ਪੰਜਾਬੀ
CLDR expansion gives pa a likely Guru default (Gurmukhi script). Never reinterpret that web-locale fallback as detected recording metadata or Punjabi’s sole script. Punjabi requires an explicit Gurmukhi-versus-Shahmukhi decision; the bare pa tag does not choose the project’s region or script. For multilingual interviews with names, honorifics, and English code-switching, inspect verify Punjabi vowel signs or Arabic-derived letters, tonal spelling cues, names, honorifics, and Punjabi–English switches after choosing a script. Visually inspect vowel signs, consonant combinations, names, number forms, and code-switching; record the project decision about whether Gurmukhi or Shahmukhi Punjabi and which regional standard is required. 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 pa hint maps to the reviewed pa provider root and preserves pa as the user's transcript language tag.
- CLDR Guru 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 pa · tiers fast, standard, precision
- Automatic detection
- Reviewed no
- Diarization
- Reviewed no
- Word timestamps
- Reviewed yes
Questions from the workflow
What must a Punjabi editor decide before correcting the transcript?
vowel signs, consonant clusters, inflected forms, names, and borrowed speech should follow the selected standard rather than an automatic transliteration. For Punjabi, verify Punjabi vowel signs or Arabic-derived letters, tonal spelling cues, names, honorifics, and Punjabi–English switches after choosing a script. Project choice: whether Gurmukhi or Shahmukhi Punjabi and which regional standard is required. 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
- Punjabi language and orthography editorial reference · checked 2026-07-20
- World Atlas of Language Structures Online · checked 2026-07-20