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
[X] I agree to follow this project's Code of Conduct
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 :
languageoption 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 attributelangon 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 :
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