Skip to content

feat(omnivoice): add Vietnamese (vi) to the language list - #1202

Open
wei668899-luo wants to merge 1 commit into
jamiepine:mainfrom
wei668899-luo:feat/omnivoice-vietnamese
Open

wei668899-luo wants to merge 1 commit into
jamiepine:mainfrom
wei668899-luo:feat/omnivoice-vietnamese

Conversation

@wei668899-luo

Copy link
Copy Markdown

OmniVoice covers 600+ languages, but the API enum and the frontend language
table only carried the 23 codes that predate the engine, so Vietnamese was
advertised nowhere and a language=vi request was rejected by the request
patterns with a 422. The model card lists it as OmniVoice ID vi (ISO 639-3
vie, ~8.5k hours of training data), so unlike Arabic's arb no code override
is needed.

Widen the pattern on VoiceProfileCreate, GenerationRequest and SpeakRequest,
list vi in the omnivoice model config and add the label to the language table.
The new test in backend/tests/test_omnivoice_compat.py pins the API pattern
against the advertised engine list, so a language can no longer be advertised
by the engine and rejected by the request models at the same time.

OmniVoice covers 600+ languages, but the API enum and the frontend language
table only carried the 23 codes that predate the engine, so Vietnamese was
advertised nowhere and a language=vi request was rejected by the request
patterns with a 422. The model card lists it as OmniVoice ID `vi` (ISO 639-3
`vie`, ~8.5k hours of training data), so unlike Arabic's `arb` no code override
is needed.

Widen the pattern on VoiceProfileCreate, GenerationRequest and SpeakRequest,
list `vi` in the omnivoice model config and add the label to the language table.
The new test in backend/tests/test_omnivoice_compat.py pins the API pattern
against the advertised engine list, so a language can no longer be advertised
by the engine and rejected by the request models at the same time.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant