Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:
Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work
The present PR would solve the issue at least in the regular user-facing chat interface by just trying to apply i18n translation to tool/filter-related UI elements. That means an administrator merely needs to edit the locales to provide translations for custom elements.
This is just a suggestion/draft, because:
I guess there are more places in the overall UI where the i18n would have to be applied. Also, currently only tools&filters are considered.
Hard-applying i18n will be fine in most cases, however it could be a breaking change in some cases where suddenly unexpected translation happens.
Happy if this inspires you @tjbck to implement your own version of this or tell me what you want to see for a merge.
Screenshots or Videos
Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/open-webui/open-webui/pull/17152
**Author:** [@Ithanil](https://github.com/Ithanil)
**Created:** 9/2/2025
**Status:** 🔄 Open
**Base:** `dev` ← **Head:** `translate_filter_tools_chat`
---
### 📝 Commits (1)
- [`c92b404`](https://github.com/open-webui/open-webui/commit/c92b40499bc70d26b19f6bb084f9bc0f89ed47a0) apply i18n translation to filter and tool names/descriptions in chat UI
### 📊 Changes
**3 files changed** (+6 additions, -6 deletions)
<details>
<summary>View changed files</summary>
📝 `src/lib/components/chat/MessageInput.svelte` (+2 -2)
📝 `src/lib/components/chat/MessageInput/InputMenu.svelte` (+2 -2)
📝 `src/lib/components/chat/ToolServersModal.svelte` (+2 -2)
</details>
### 📄 Description
# Pull Request Checklist
### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request.
**Before submitting, make sure you've checked the following:**
- [x] **Target branch:** Please verify that the pull request targets the `dev` branch.
- [x] **Description:** Provide a concise description of the changes made in this pull request.
- [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description.
- [x] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources?
- [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation?
- [x] **Testing:** Have you written and run sufficient tests to validate the changes?
- [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
- [x] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following:
- **BREAKING CHANGE**: Significant changes that may affect compatibility
- **build**: Changes that affect the build system or external dependencies
- **ci**: Changes to our continuous integration processes or workflows
- **chore**: Refactor, cleanup, or other non-functional code changes
- **docs**: Documentation update or addition
- **feat**: Introduces a new feature or enhancement to the codebase
- **fix**: Bug fix or error correction
- **i18n**: Internationalization or localization changes
- **perf**: Performance improvement
- **refactor**: Code restructuring for better maintainability, readability, or scalability
- **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- **test**: Adding missing tests or correcting existing tests
- **WIP**: Work in progress, a temporary label for incomplete or ongoing work
# Changelog Entry
### Description
Motivation: https://github.com/open-webui/open-webui/issues/16394
The present PR would solve the issue at least in the regular user-facing chat interface by just trying to apply i18n translation to tool/filter-related UI elements. That means an administrator merely needs to edit the locales to provide translations for custom elements.
This is just a suggestion/draft, because:
1) I guess there are more places in the overall UI where the i18n would have to be applied. Also, currently only tools&filters are considered.
2) Hard-applying i18n will be fine in most cases, however it could be a breaking change in some cases where suddenly unexpected translation happens.
Happy if this inspires you @tjbck to implement your own version of this or tell me what you want to see for a merge.
### Screenshots or Videos
<img width="257" height="201" alt="Screenshot From 2025-09-02 20-33-43" src="https://github.com/user-attachments/assets/dd617e9f-383f-4a1d-b780-d64f21e1a9a5" />
<img width="257" height="201" alt="Screenshot From 2025-09-02 20-33-19" src="https://github.com/user-attachments/assets/1af687ef-acda-4349-af97-0254e3b863ac" />
### Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/17152
Author: @Ithanil
Created: 9/2/2025
Status: 🔄 Open
Base:
dev← Head:translate_filter_tools_chat📝 Commits (1)
c92b404apply i18n translation to filter and tool names/descriptions in chat UI📊 Changes
3 files changed (+6 additions, -6 deletions)
View changed files
📝
src/lib/components/chat/MessageInput.svelte(+2 -2)📝
src/lib/components/chat/MessageInput/InputMenu.svelte(+2 -2)📝
src/lib/components/chat/ToolServersModal.svelte(+2 -2)📄 Description
Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:
devbranch.Changelog Entry
Description
Motivation: https://github.com/open-webui/open-webui/issues/16394
The present PR would solve the issue at least in the regular user-facing chat interface by just trying to apply i18n translation to tool/filter-related UI elements. That means an administrator merely needs to edit the locales to provide translations for custom elements.
This is just a suggestion/draft, because:
Happy if this inspires you @tjbck to implement your own version of this or tell me what you want to see for a merge.
Screenshots or Videos
Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.