Skip to content

fix: handle "auto" locale to prevent invalid language code sent to Gladia#14

Open
lrossillon-gladia wants to merge 2 commits intobigbluebutton:developmentfrom
lrossillon-gladia:fix/handle-auto-locale
Open

fix: handle "auto" locale to prevent invalid language code sent to Gladia#14
lrossillon-gladia wants to merge 2 commits intobigbluebutton:developmentfrom
lrossillon-gladia:fix/handle-auto-locale

Conversation

@lrossillon-gladia
Copy link
Copy Markdown

Summary

  • treat BBB locale auto as Gladia auto-detection instead of passing an invalid language code
  • omit the initial language argument and send an empty languages list on locale updates
  • handle auto in transcript locale resolution and add regression tests
  • add the required changelog entry

Testing

  • not run in this environment (uv is not installed in this shell)

Lazare Rossillon added 2 commits March 26, 2026 11:23
…adia

BBB core sends locale "auto" when the user selects "Auto detect" for
live transcription. This value was passed through to Gladia's API
verbatim, which rejected it since "auto" is not a valid ISO 639-1
language code. The old bbb-transcription-controller handled this by
stripping the language field so Gladia would fall back to server-side
auto-detection, but this handling was lost in the migration to LiveKit.

- _sanitize_locale() now returns None for "auto" locale
- start_transcription_for_user() omits the language param when None,
  triggering Gladia's built-in auto-detection
- update_locale_for_user() sends empty languages list for auto locale
- Transcript handlers in main.py resolve BBB locale via the translation
  map when original locale is "auto" instead of comparing against it
@prlanzarin
Copy link
Copy Markdown
Member

Thanks for the fix @lrossillon-gladia.

Could you please confirm if you already sent in the signed Contributor License Agreement? See https://docs.bigbluebutton.org/support/faq.html#why-do-i-need-to-sign-a-contributor-license-agreement-to-contribute-source-code
Thanks in advance!

@prlanzarin prlanzarin self-requested a review March 27, 2026 14:42
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.

2 participants