mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
[GH-ISSUE #16394] feat: Localization support for functions #17886
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#17886
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Ithanil on GitHub (Aug 8, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16394
Check Existing Issues
Problem Description
The ability to add custom functions like filters and actions brings a lot of value to Open WebUI. However, especially when used in an organization with users of different native languages, the fact that the user facing buttons and tooltips do not support localization makes them hard to use without breaking language consistency for some users.
Desired Solution you'd like
Provide a mechanism to provide localization for UI elements of functions.
Alternatives Considered
Using i18n on e.g. function titles, but doesn't work.
Additional Context
No response
@Classic298 commented on GitHub (Apr 15, 2026):
@Ithanil i want to share with you what we do:
for actions, everytime the action is triggered, we run an event emitter execute type event which runs JS and detects the UI language of the user and then before doing anything else takes respective localized text strings from within the action code depending on the detected language and uses that
works absolutely flawlessly, we can customize the entire action depending on the user's language, same for tools
since actions, tools and filters are HIGHLY customizable, basically custom python code - i am not sure how open webui would go about implementing localization for these things at all, since every single tool and action and Rich UI has a different code, different strings and different ways to output data. Files, rich UI, triggered downloads, edited messages and more. I think its practically impossible to implement therefore i wanted you to say that this is a very easy way to implement localization