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

Flatten & normalize i18n files to allow integration with crowd-sourced translation platforms #109

Closed
archived-m opened this issue May 10, 2021 · 1 comment
Assignees
Labels
[Concerns] i18n Internationalization [Contribute] Help wanted Extra attention is needed

Comments

@archived-m
Copy link
Contributor

Some of our translation files have nested keys, as well as arrays. To integrate with third party/open source solutions for translation interfaces so we can have this be community-managed, we should standardize these.

More specifically, we'd do well to have a single key file in English, where the other translations are provided through an integration as a result of the above.

Closely related to #77
Solutions to be explored & investigated. Assigning you here @wardbeyens since you're in the driver's seat of this.

@archived-m
Copy link
Contributor Author

@wardbeyens Can this be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Concerns] i18n Internationalization [Contribute] Help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants