[Feature] Multi-language Support (i18n)

[llaumgui]

Add internationalization (i18n) support to allow users to switch the interface language.

Motivation

• User Experience: Provides a localized experience for non-English users.
• Accessibility & Reach: Broadens adoption in global communities and multi-lingual teams.

[themartz90]

Hey, thanks for the suggestion! 😉
I like the idea, but I want to understand the scope before committing to it.
Jellydash currently has English text in Twig templates, PHP-generated labels and JavaScript-rendered content. Proper internationalization would need shared translation catalogs, English fallback, plural handling, localized dates and a way to provide translated strings to both Twig and JavaScript. I would want to build that foundation properly rather than maintain separate translated templates.
Which language or languages are you interested in? Would you also be interested in contributing or maintaining one of the translations once the underlying system exists?
I’m keeping this open while the current pull requests settle, but I don’t want to promise an implementation or timeline...

[llaumgui]

I whish like a french version. I can help to translate .po or other translation system.

[themartz90]

Thanks, French and your offer to help with the translation are useful context! I’ll keep this open for when I am ready to design the underlying internationalization system. I have not decided on .po or another catalog format yet, and I cannot promise a timeline. 🙂