Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve i18n support #310

Closed
fraxken opened this issue Dec 4, 2023 · 1 comment
Closed

Improve i18n support #310

fraxken opened this issue Dec 4, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@fraxken
Copy link
Member

fraxken commented Dec 4, 2023

There is still a lot of room to improve the i18n support across the Web UI:

  • Moving i18n package translation locally here (cli and ui).
  • Find a way to support i18n in front-end JavaScript assets (see expandable component)

Other components impacted in the top of my mind:

  • home/overview (a lot of text injected from code)
  • network (for edges labels)
  • locker

I think the goal is to successfully tokenize everything.

@fraxken fraxken added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Dec 4, 2023
@PierreDemailly
Copy link
Member

image
CLI also needs i18n improvements, missing i18n for config & config create

Note that we cannot translate sade -> https://github.com/lukeed/sade/blob/8aa4a69e95fbfba88cf49082713900ecbe27f183/src/utils.js#L67
Maybe its an opportunity to build our own package in TopCli 👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants