Skip to content

feat: Implementing Localization (i18n) Suppor #23

@Demitry235

Description

@Demitry235

Hello! You requested to open an issue before starting work on major changes, so here I am.

I want to take on the task of implementing localization support for the Kyber Launcher to make it more accessible to the international community. Since this is a significant change to how strings are handled, I would like to discuss my proposed plan before I begin:

  • Architecture: Transitioning to Flutter's native localization system (flutter_localizations). This involves enabling generate: true in pubspec.yaml and moving strings into .arb files (e.g., lib/l10n/app_en.arb).
  • Language Selection: Adding a language selector in the "Language & Accessibility" settings page.
  • State Management: Updating AppLocale to handle locale switching and ensuring the selection is persisted via Hive.
  • Refactoring: Gradually replacing hardcoded strings throughout the project with localization keys (e.g., AppLocalizations.of(context)!.key).

Please let me know if this approach is acceptable to you or if you have any specific preferences regarding how localization should be implemented in this project.

P.S. Unfortunately, I am more of an enthusiast than a professional programmer (as you might have noticed from the code style/formatting of my first PR). Regarding my previous PR: I wasn't sure about the correct workflow. Was I right to push the fixes as new commits to the same PR, or should I have opened a new one?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions