[PR #22452] [MERGED] i18n: add pt-BR translations for newly added UI items and consistency pass #26707

New Issue

GiteaMirror · 2026-04-20T06:39:45-05:00

GiteaMirror commented

2026-04-20 06:39:45 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/22452
Author: @joaoback
Created: 3/8/2026
Status: ✅ Merged
Merged: 3/8/2026
Merged by: @tjbck

Base: dev ← Head: patch-31

📝 Commits (1)

b80e772 i18n: (pt-BR) add translations for newly added UI items + consistency pass

📊 Changes

1 file changed (+24 additions, -24 deletions)

View changed files

📝 src/lib/i18n/locales/pt-BR/translation.json (+24 -24)

📄 Description

i18n: (pt-BR) add translations for newly added UI items + consistency/quality pass

New pt-BR translations for items introduced in the latest releases, plus a consistency/quality pass across existing strings (grammar, tone, capitalization, pluralization). Placeholders and hotkeys preserved. No logic changes.

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.

This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.

Before submitting, make sure you've checked the following:

Target branch: Verify that the pull request targets the dev branch. PRs targeting main will be immediately closed.
Description: Provide a concise description of the changes made in this pull request down below.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Add docs in Open WebUI Docs Repository. Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps.
Dependencies: Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash.
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to make screenshots of the feature/fix and include them in the PR description.
Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
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?
Design & Architecture: Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes.
Git Hygiene: Keep PRs atomic (one logical change). Clean up commits and rebase on dev to ensure no unrelated commits (e.g. from main) are included. Push updates to the existing PR branch instead of closing and reopening.
Title 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

Add missing pt-BR translations for newly introduced UI items in recent releases and perform a consistency/quality pass across existing locale strings. This improves clarity, grammar, capitalization, tone, and pluralization for Brazilian Portuguese users, with no impact on application logic.

Added

New pt-BR strings for recently introduced menus, tooltips, settings, notifications, and helper texts.

Changed

Standardized tone to a more natural and consistent pt-BR voice across the interface.
Standardized capitalization, punctuation, and wording patterns.
Improved clarity of error/success messages, tooltips, and helper texts.
Harmonized terminology across the locale, such as:
- Model → Modelo
- Context window → Janela de contexto
- Workflow → Fluxo de trabalho
Preserved and repositioned placeholders and hotkeys where needed to better match natural pt-BR sentence structure.

Deprecated

N/A

Removed

N/A

Fixed

Minor typos, inconsistent pluralization, ambiguous wording, and stray whitespace in multiple strings.
Translation inconsistencies in recently added UI areas.
Validation of placeholders such as {name}, {count}, and keyboard shortcuts to ensure they remain intact and render correctly.

Security

N/A

Breaking Changes

BREAKING CHANGE: None. No translation keys were renamed or removed; only locale values were added or refined.

Additional Information

Scope is limited to the pt-BR locale files only.
No logic changes, behavior changes, or dependency changes were introduced.
Documentation update is not required for this change because it is limited to localization values and does not alter user-facing functionality, APIs, environment variables, or deployment behavior.
Manual validation was performed in the UI, including review of recently updated screens and message states.
If helpful, I can follow up with a separate PR proposing a pt-BR localization style guide/glossary for consistency across future contributions.

Screenshots or Videos

Manual UI review completed for:
- Settings
- Models
- Privacy
- Import/Export
- Workflows / Executions
- Playground / Prompt helpers
- Conversations / History bulk actions and confirmations
I can attach screenshots of the validated screens if maintainers would like them included.

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.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

_{🔄 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/22452 **Author:** [@joaoback](https://github.com/joaoback) **Created:** 3/8/2026 **Status:** ✅ Merged **Merged:** 3/8/2026 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `patch-31` --- ### 📝 Commits (1) - [`b80e772`](https://github.com/open-webui/open-webui/commit/b80e772eac48cd4f41712a7772f45f74820276d7) i18n: (pt-BR) add translations for newly added UI items + consistency pass ### 📊 Changes **1 file changed** (+24 additions, -24 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/i18n/locales/pt-BR/translation.json` (+24 -24) </details> ### 📄 Description # i18n: (pt-BR) add translations for newly added UI items + consistency/quality pass New **pt-BR** translations for items introduced in the latest releases, plus a consistency/quality pass across existing strings (grammar, tone, capitalization, pluralization). Placeholders and hotkeys preserved. No logic changes.  # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request. This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Verify that the pull request targets the `dev` branch. **PRs targeting `main` will be immediately closed.** - [x] **Description:** Provide a concise description of the changes made in this pull request down below. - [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:** Add docs in [Open WebUI Docs Repository](https://github.com/open-webui/docs). Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps. - [x] **Dependencies:** Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash. - [x] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to **make screenshots of the feature/fix and include them in the PR description**. - [x] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [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] **Design & Architecture:** Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes. - [x] **Git Hygiene:** Keep PRs atomic (one logical change). Clean up commits and rebase on `dev` to ensure no unrelated commits (e.g. from `main`) are included. Push updates to the existing PR branch instead of closing and reopening. - [x] **Title 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 Add missing **pt-BR** translations for newly introduced UI items in recent releases and perform a consistency/quality pass across existing locale strings. This improves clarity, grammar, capitalization, tone, and pluralization for Brazilian Portuguese users, with no impact on application logic. ### Added - New **pt-BR** strings for recently introduced menus, tooltips, settings, notifications, and helper texts. ### Changed - Standardized tone to a more natural and consistent **pt-BR** voice across the interface. - Standardized capitalization, punctuation, and wording patterns. - Improved clarity of error/success messages, tooltips, and helper texts. - Harmonized terminology across the locale, such as: - *Model* → **Modelo** - *Context window* → **Janela de contexto** - *Workflow* → **Fluxo de trabalho** - Preserved and repositioned placeholders and hotkeys where needed to better match natural pt-BR sentence structure. ### Deprecated - N/A ### Removed - N/A ### Fixed - Minor typos, inconsistent pluralization, ambiguous wording, and stray whitespace in multiple strings. - Translation inconsistencies in recently added UI areas. - Validation of placeholders such as `{name}`, `{count}`, and keyboard shortcuts to ensure they remain intact and render correctly. ### Security - N/A ### Breaking Changes - **BREAKING CHANGE**: None. No translation keys were renamed or removed; only locale values were added or refined. --- ### Additional Information - Scope is limited to the **pt-BR locale files** only. - No logic changes, behavior changes, or dependency changes were introduced. - Documentation update is not required for this change because it is limited to localization values and does not alter user-facing functionality, APIs, environment variables, or deployment behavior. - Manual validation was performed in the UI, including review of recently updated screens and message states. - If helpful, I can follow up with a separate PR proposing a **pt-BR localization style guide/glossary** for consistency across future contributions. ### Screenshots or Videos - Manual UI review completed for: - Settings - Models - Privacy - Import/Export - Workflows / Executions - Playground / Prompt helpers - Conversations / History bulk actions and confirmations - I can attach screenshots of the validated screens if maintainers would like them included. ### Contributor License Agreement  - [x] By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-20 06:39:45 -05:00

GiteaMirror closed this issue

2026-04-20 06:39:46 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#26707