Pull Request

Thanks for wanting to improve Open WebUI. The most useful contribution is usually a clear, well-written Issue, not an unsolicited code pull request.

Open a code pull request only when a maintainer asks for one, or when the change is only i18n/localization. For real, reproducible bugs, start with a well-described Issue. For feature requests, UI/UX changes, behavior changes, architecture changes, suspected fixes, or unconfirmed approaches, start with an active Discussion.

Before continuing, make sure the linked Issue or Discussion explains the user-facing problem, the expected outcome, the affected workflow, and any examples, logs, screenshots, constraints, or reproduction details needed for maintainers to evaluate it.

If you have implementation notes, include them as reference in the Issue or Discussion. If you want to share code as reference, include it there as a local diff, patch, or branch note. Do not open a pull request for reference code.

Unsolicited PRs may be closed without review, especially when they introduce product, architecture, compatibility, dependency, or maintenance decisions that have not been discussed.

Checklist

• [v ] This PR targets the dev branch.
• [ v] This PR links to a well-described, confirmed Issue or active Discussion: Closes #___ / Relates to #___.
• [v ] A maintainer explicitly asked me to open this PR, or this PR only updates i18n/localization.
• [v ] The change is one logical unit with no unrelated commits.
• [v ] I matched nearby code patterns and avoided unnecessary new settings, abstractions, or dependencies.
• [v ] I manually tested the changed workflow and any nearby behavior that could be affected.
• [v ] I updated relevant docs, including the Open WebUI Docs Repository, if needed.
• I added screenshots for UI changes, and a recording when motion or interaction matters.
• [v ] I reviewed any AI-generated code before submitting it.
• [v ] The PR title uses one of the prefixes listed below.

Title Prefix

Use one of the following prefixes:

• BREAKING CHANGE: Changes affecting backward compatibility
• build: Build system or dependency changes
• ci: CI/CD workflow changes
• chore: Refactoring, cleanup, or non-functional changes
• docs: Documentation additions or updates
• feat: New features or enhancements
• fix: Bug fixes or corrections
• i18n: Internationalization or localization changes
• perf: Performance improvements
• refactor: Code restructuring

Summary

#14066
added and updated empty i18n lines

Testing

List the exact manual checks you ran. Include commands, setup details, screenshots, or recordings where helpful.

Changelog Entry

Added

Changed

Fixed

Removed

Security

Breaking Changes

Additional Context

Add anything maintainers should know before review.

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.