Description
The new i18n system (I18n.t(), strings.json) translates UI labels correctly, but several user-facing strings are still hardcoded in English and bypass the translation system entirely.
Affected Strings
Frontend (frontend/js/chat.js)
appendError("Could not reach the backend.")Backend (backend/app.py)
"I don't have enough information in the indexed sources to answer that."
This fallback answer is returned when ChromaDB finds no relevant chunks, but it is always in English regardless of the user's selected language.
Impact
Users who switch to French, Spanish, Hindi, or Portuguese still see critical error and fallback messages in English, breaking the multilingual experience.
Fix Needed
- Add the missing strings to
frontend/i18n/strings.json for all 5 supported languages
- Route the frontend error string through
I18n.t() in chat.js
- In
app.py, pass the language parameter from the request into the fallback message and use a translated string
Description
The new i18n system (
I18n.t(),strings.json) translates UI labels correctly, but several user-facing strings are still hardcoded in English and bypass the translation system entirely.Affected Strings
Frontend (
frontend/js/chat.js)Backend (
backend/app.py)"I don't have enough information in the indexed sources to answer that."This fallback answer is returned when ChromaDB finds no relevant chunks, but it is always in English regardless of the user's selected language.
Impact
Users who switch to French, Spanish, Hindi, or Portuguese still see critical error and fallback messages in English, breaking the multilingual experience.
Fix Needed
frontend/i18n/strings.jsonfor all 5 supported languagesI18n.t()inchat.jsapp.py, pass thelanguageparameter from the request into the fallback message and use a translated string