i18n locale detection does not fall back gracefully for unsupported locales

[hman38705]

Labels: frontend, i18n
Priority: Low

Description

frontend/src/lib/i18n.ts handles internationalization but may not gracefully fall back to English when an unsupported locale is detected from the browser. This could result in missing translation keys being rendered as raw keys.

Context

frontend/I18N_GUIDE.md documents the i18n approach. The fallback behavior should be explicit and tested.

Acceptance Criteria

• Unsupported locales fall back to en without errors
• Missing translation keys log a warning in development and render the key in production
• Unit tests in i18n.test.ts cover fallback scenarios

[oncleweynom]

@oncleweynom has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi maintainer would want to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @oncleweynom to this issue.

[drips-wave]

Congratulations, @oncleweynom! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @oncleweynom: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊