[GH-ISSUE #1375] [FEATURE REQUEST] - Multilingual #480

New issue

Open

opened 2026-02-27 08:17:29 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 08:17:29 +03:00

Owner

Originally created by @chris2fr on GitHub (Jan 2, 2026).
Original GitHub issue: https://github.com/lldap/lldap/issues/1375

Motivation

I would like to use this application with French and Arab audiences

Describe the solution you'd like

I would like a language switcher

Describe alternatives you've considered

There could be a configured language at statup, or I could modifiy the static code.

Additional context

How should we go about internationalization ? gettext ? I can code and help.

Originally created by @chris2fr on GitHub (Jan 2, 2026). Original GitHub issue: https://github.com/lldap/lldap/issues/1375 **Motivation** I would like to use this application with French and Arab audiences **Describe the solution you'd like** I would like a language switcher **Describe alternatives you've considered** There could be a configured language at statup, or I could modifiy the static code. **Additional context** How should we go about internationalization ? gettext ? I can code and help.

kerem added the

enhancement

label

2026-02-27 08:17:29 +03:00

kerem commented

2026-02-27 08:17:30 +03:00

Author

Owner

@nitnelave commented on GitHub (Jan 2, 2026):

As much as it would be a nice feature, I'm not sure we have the dev time available to make that happen, and I wouldn't want a half-baked implementation with (for instance) English error messages leaking through to the frontend.

What about browser ai translation? Is that enough for your users? How much do they have to interact with LLDAP?

@nitnelave commented on GitHub (Jan 2, 2026): As much as it would be a nice feature, I'm not sure we have the dev time available to make that happen, and I wouldn't want a half-baked implementation with (for instance) English error messages leaking through to the frontend. What about browser ai translation? Is that enough for your users? How much do they have to interact with LLDAP?

kerem commented

2026-02-27 08:17:30 +03:00

Author

Owner

@chris2fr commented on GitHub (Jan 3, 2026):

I'd bé happy to provide a PR.
Any particulier stratégie you'd like me to use?

@chris2fr commented on GitHub (Jan 3, 2026): I'd bé happy to provide a PR. Any particulier stratégie you'd like me to use?

kerem commented

2026-02-27 08:17:30 +03:00

Author

Owner

@nitnelave commented on GitHub (Jan 3, 2026):

I think it'll take more than just a simple PR. It complicates every future feature, since now we have to take internationalization into account. Plus, right to left languages like Arabic need a bit more care than just replacing strings. Then we have to figure out how to get the resources to the frontend (and backend), how to integrate that into the frontend code, the backend code (2 different frameworks), how to keep that up to date, what to use as fallbacks when we don't have translations for specific messages, ...

It's a rather complex feature, and I'm not familiar with the rust libraries needed, or even the industry best practices.

That's why I'm asking: is browser translation inadequate? How often do your users need to interact with LLDAP?

@nitnelave commented on GitHub (Jan 3, 2026): I think it'll take more than just a simple PR. It complicates every future feature, since now we have to take internationalization into account. Plus, right to left languages like Arabic need a bit more care than just replacing strings. Then we have to figure out how to get the resources to the frontend (and backend), how to integrate that into the frontend code, the backend code (2 different frameworks), how to keep that up to date, what to use as fallbacks when we don't have translations for specific messages, ... It's a rather complex feature, and I'm not familiar with the rust libraries needed, or even the industry best practices. That's why I'm asking: is browser translation inadequate? How often do your users need to interact with LLDAP?

kerem referenced this issue

2026-02-27 09:09:41 +03:00

[PR #480] [MERGED] Fix dex config example #770