Skip to content

[Feature]: Add English language support as the first step toward i18n #32

@0Chan-smc

Description

@0Chan-smc

What problem does this solve?

Currently, Ahakey Studio does not appear to support i18n or an English user interface. This makes it difficult for non-native speakers of the current language to understand menus, settings, error messages, and documentation inside the app.

As a result, users who are interested in the project may have trouble getting started, evaluating the app, or contributing to it. Adding English support would make the app more accessible to a broader international audience and could also help attract more users and contributors.

Proposed solution

Please consider adding English language support first, even if full i18n support is not implemented immediately.

A good first step could be:

  • Provide English translations for the main UI labels, menus, buttons, settings, and common messages.
  • Optionally add a language setting that allows users to switch to English.
  • Structure the text resources in a way that future translations can be added more easily.

I believe English support would be a practical first step because it can make the app usable for many more people while also laying the foundation for broader i18n support in the future.

Use case

This would benefit international users.

Related area

Desktop client

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions