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

Feature request: i18n support #65

Open
Askadar opened this issue Jan 15, 2023 · 2 comments
Open

Feature request: i18n support #65

Askadar opened this issue Jan 15, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@Askadar
Copy link

Askadar commented Jan 15, 2023

Description
Hey, picked this project to add slightly custom wordle game to a site, but its user-base is using language other than English, so I'm going to add localization for it. At the same time I could create a PR here so it's straightforward to add support for other languages and make it easier for more people to play.
An extra step would be to have separate\custom loader for valid and selectable words in different locales. Otherwise it can be solved with simply replacing words_5 on-premise.

Reasoning
As described above, native locale support would make it easier for non-English speaking people to pick up this version of a game as well as play hosted version.

Implementation (optional)
Currently I'm looking into which i18n library to use, other than that I plan on adding directory with locales, current en-US (I presume) and the one I'm translating into. For i18n I'm planning to use either i18next since it's a robust library which I have experience with, or svelte-i18n since it seems to be more popular choice for svelte while i18next's svelte lib seems fairly unused.

@MikhaD let me know your thoughts on this, whether you're interested in having i18n at all, preferences for i18n lib\implementation and anything else I might need to know for this feature.

@Askadar Askadar added the enhancement New feature or request label Jan 15, 2023
@JasonLovesDoggo
Copy link

Just looking over both of those I would recommend you go with i18next

@MikhaD
Copy link
Owner

MikhaD commented Jan 23, 2023

Thanks both of you. This seems to be the solution I was looking for in #59 . I will look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants