Skip to content

i18n: complete missing translations and make locale switching consistent #162

Description

@ermeme

Description

The app already ships multiple languages, but some screens still render strings in English after switching locale while others correctly use the selected language. That suggests the internationalization layer is incomplete or inconsistent.

We should audit the i18n setup and make locale switching work consistently across the UI.

Expected behavior

  • Selecting a supported language should translate the entire UI as much as possible.
  • Missing keys should be identified and filled in.
  • Fallback behavior should be intentional and consistent, not accidental.

Scope

  • Audit translation keys across the app
  • Find untranslated strings or hardcoded English copy in localized screens
  • Check locale switching and fallback behavior
  • Add/adjust tests where practical

Notes

This is a UX/parity issue, not a protocol change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: uiFlutter screens, UI providers, UXbugSomething isn't workingpriority: mediumMedium priority

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions