Multi-language support

[IRHM]

Multi-language support.

Not sure how this will all pan out, but an overview of what I currently think we need to get done:

• Setup Weblate instance
• Weblate automations (getting translations into this repo in useable format)
• Integrate i18next for using translations in frontend app (involves moving all current strings into an en-us translation file and using them from there and as default fallback)
• [Feature request] Get posters/titles in localized version #442 (this might require structural changes depending on the implementation for caching)

Discussed in #800

^{Originally posted by kiwinh0 February 11, 2025}
When will we have multilanguage?
I would be willing to collaborate with several languages

[deadLocks21]

Hey, do you think I can start working on the i18next implementation, before you create an instance of Weblate or something?

[IRHM]

Hey, do you think I can start working on the i18next implementation, before you create an instance of Weblate or something?

Hi @deadLocks21, I believe you can and that would be a big help.

I think this will be the time consuming part, having to move every existing string out into a compatible json file and using that as reference instead: https://docs.weblate.org/en/latest/formats/i18next.html#js-i18next

You can check out the weblate docs for an overview to see how you want to set things up. I'm not 100% sure, but I believe once I set up Weblate, I just import the base translation file (english, that you will make) and it will set all base strings up for translation process.

Thanks for looking into contributing! Let me know if you decide to start work on this we can discuss if you have any questions and I can assign you.