fix(voice): Gemini voice messages follow a language change

The Gemini session translated each status and error message once, when it
happened, so after a language change the voice control kept showing it in
the old language. The state event now also carries the English catalog text
as sourceDetail, and the control words it when shown. The local server's
known token errors stay catalog text until then instead of being translated
on arrival.
This commit is contained in:
Sameh Khamis committed 2026-11-10 18:04:52 -08:00
1 parent 962f7293c6
commit b1c5de0ed1
5 files changed
+77 -8

No files matched your search

+7 -2
View File
@@ -71,7 +71,9 @@ export function geminiSocketUrl({ token, websocketUrl }) {
return url.href;
}
// Known local-server failures are translated; unexpected diagnostics stay intact.
// The local server's known failures, marked for translation. Each is kept as
// its English catalog text, which the status words when it is shown, so a
// language change words it again; unexpected diagnostics stay intact.
function tokenErrorMessage(error) {
switch (error) {
case msg('Gemini voice could not connect. Try again.'):
@@ -85,7 +87,6 @@ function tokenErrorMessage(error) {
case msg('Token request is too large'):
case msg('Use an empty JSON token request'):
case msg('Method not allowed'):
return t(error);
default:
return error;
}
@@ -369,10 +370,14 @@ export class GeminiSessionController {
detail = this.input.pushToTalkKeyHeld
? msg('Release Space to send')
: msg('Hold Space to talk');
// `detail` is worded in the current language; `sourceDetail` keeps the
// English catalog text, so a view can word it again after a language
// change.
const event = {
type: 'state',
state: status,
detail: translateKnown(detail),
...(typeof detail === 'string' && { sourceDetail: detail }),
};
if (recovery) event.recovery = translateKnown(recovery);
if (missingKey) event.missingKey = true;