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] Translations #28

Open
1 task done
YummYume opened this issue Jan 2, 2023 · 0 comments
Open
1 task done

[FEATURE] Translations #28

YummYume opened this issue Jan 2, 2023 · 0 comments
Assignees
Labels
back Concerns the back dependency Concerns a dependency feature Request for a feature front Concerns the front of the app on hold Is currently on hold priority 3 Somewhat important - Something achievable but not of absolute importance

Comments

@YummYume
Copy link
Contributor

YummYume commented Jan 2, 2023

Type of feature

Something new

The name of the feature

Translations

Feature description

Translating RankyList is one of the most important aspects to reach a wider audience. Here's how it would go down :

  • Static text would be translatable thanks to some kind of language selection,
  • Dynamic text written by people in tier lists would have a language option where they would need to select the language they are using. This would allow us to sort tier lists by language and also add an attribute lang on tier lists.

The second option is fairly easy to implement, we just need to know about where to ask for the user's language.

For the first option, although packages for translation already exist, I don't feel like it's a good idea to use them now. Instead, we should wait to see an official release from SvelteKit (see this issue).

We definitely want to render translations server-side to avoid loading them in the front end and also so it can work without Javascript.

Additional information

It should also be possible to select multiple languages when sorting of course, but only one language would be allowed per tier list.

About the possible libraries we could use :

  • svelte-i18n is the most popular but only does rendering on the client side and forces you to load translations on the client side, not a fan.
  • Svelte-intl-precompile seems closer to what we would want. It precompiles translations so they can be server-side rendered and spares the client side from doing all that work.

For now, unless we really need it, let's wait and see if SvelteKit releases anything for translations any time soon. I know it's on their roadmap (see this issue too).

Code of Conduct

  • I agree to follow this project's Code of Conduct
@YummYume YummYume added back Concerns the back dependency Concerns a dependency feature Request for a feature front Concerns the front of the app on hold Is currently on hold priority 3 Somewhat important - Something achievable but not of absolute importance labels Jan 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back Concerns the back dependency Concerns a dependency feature Request for a feature front Concerns the front of the app on hold Is currently on hold priority 3 Somewhat important - Something achievable but not of absolute importance
Projects
None yet
Development

No branches or pull requests

2 participants