[PR #12966] [MERGED] i18n: Update es-ES (Spanish) translation.json #23064

New Issue

GiteaMirror · 2026-04-20T04:36:20-05:00

GiteaMirror commented

2026-04-20 04:36:20 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/12966
Author: @damianmr
Created: 4/17/2025
Status: ✅ Merged
Merged: 4/17/2025
Merged by: @tjbck

Base: dev ← Head: dev

📝 Commits (1)

b1629d8 i18n: Update es-ES (Spanish) translation.json

📊 Changes

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

View changed files

📝 src/lib/i18n/locales/es-ES/translation.json (+96 -96)

📄 Description

Pull Request Checklist

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

Target branch: Please verify that the pull request targets the dev branch.
Description: See below
Changelog: Yes
Code review: I did a self-review based on other existing keys in the same file.
Prefix: yes, used i18n

Changelog Entry

Description

I noticed a few accessibility problems with the spelling used in the Spanish translation file. In multiple places the project was using terminology like "usuari@" to convey the meaning of "usuario" or "usuaria" (m. and f. forms of "user" in Spanish). This creates a few grammatical problems like:

Accessibility Issues (e.g., screen readers):

The use of special characters like “@” is not compatible with most screen readers. These tools often either skip the character entirely or read it out loud as “arroba” (Spanish for at), which breaks the intended meaning and disrupts the user experience for visually impaired users.

Not grammatically valid in Spanish:

“Usuari@” is not recognized as a proper word in Spanish grammar. It’s a typographical invention and not supported by the Real Academia Española (RAE), making it inappropriate for formal or standardized documentation or user interfaces.

Inconsistency with internationalization (i18n) standards:

The use of non-standard characters may introduce friction for translators, localization tools, and contributors unfamiliar with such conventions. In particular, the Spanish translation file was an outlier among other gender-specific Iberian languages (see gl-ES, pt-PT, ca-ES translation files)

Poor readability and UX impact:

Many users may not understand or be familiar with the “@” as a gender marker. It can be distracting or perceived as unprofessional in some contexts.

I also removed the "formal" voice (usted, which is a formal you) from a few translation keys. Most of the file is using an informal voice, anyway (tu for you). The informal voice isn't bad at all, more on the contrary, personally, I think it's better because it makes look the system more welcoming, warm and modern. In any case, the file is now more consistent (it's using the informal voice everywhere).

I also added a few missing translation keys that were added recently and updated some translations that seemed to have been translated with an automatic tool.

_{🔄 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/12966 **Author:** [@damianmr](https://github.com/damianmr) **Created:** 4/17/2025 **Status:** ✅ Merged **Merged:** 4/17/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `dev` --- ### 📝 Commits (1) - [`b1629d8`](https://github.com/open-webui/open-webui/commit/b1629d8660e34d4892a288e5435d49ddc8388f0f) i18n: Update es-ES (Spanish) translation.json ### 📊 Changes **1 file changed** (+96 additions, -96 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/i18n/locales/es-ES/translation.json` (+96 -96) </details> ### 📄 Description # Pull Request Checklist **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** See below - [x] **Changelog:** Yes - [x] **Code review:** I did a self-review based on other existing keys in the same file. - [x] **Prefix:** yes, used `i18n` # Changelog Entry ### Description I noticed a few accessibility problems with the spelling used in the Spanish translation file. In multiple places the project was using terminology like "usuari@" to convey the meaning of "usuario" or "usuaria" (m. and f. forms of "user" in Spanish). This creates a few grammatical problems like: #### Accessibility Issues (e.g., screen readers): The use of special characters like “@” is not compatible with most screen readers. These tools often either skip the character entirely or read it out loud as “arroba” (Spanish for `at`), which breaks the intended meaning and disrupts the user experience for visually impaired users. #### Not grammatically valid in Spanish: “Usuari@” is not recognized as a proper word in Spanish grammar. It’s a typographical invention and not supported by the Real Academia Española (RAE), making it inappropriate for formal or standardized documentation or user interfaces. #### Inconsistency with internationalization (i18n) standards: The use of non-standard characters may introduce friction for translators, localization tools, and contributors unfamiliar with such conventions. In particular, the Spanish translation file was an outlier among other gender-specific Iberian languages (see `gl-ES`, `pt-PT`, `ca-ES` translation files) #### Poor readability and UX impact: Many users may not understand or be familiar with the “@” as a gender marker. It can be distracting or perceived as unprofessional in some contexts. I also removed the "formal" voice (`usted`, which is a formal `you`) from a few translation keys. Most of the file is using an informal voice, anyway (`tu` for `you`). The informal voice isn't bad at all, more on the contrary, personally, I think it's better because it makes look the system more welcoming, warm and modern. In any case, the file is now more consistent (it's using the informal voice everywhere). I also added a few missing translation keys that were added recently and updated some translations that seemed to have been translated with an automatic tool. --- <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 04:36:20 -05:00

GiteaMirror closed this issue

2026-04-20 04:36:20 -05:00

GiteaMirror referenced this issue

2026-04-20 06:48:55 -05:00

[PR #23064] [CLOSED] fix: pin 49 unpinned action(s),extract 4 unsafe expression(s) to env vars #27006

GiteaMirror referenced this issue

2026-04-25 14:27:43 -05:00

[PR #23064] [CLOSED] fix: pin 49 unpinned action(s),extract 4 unsafe expression(s) to env vars #42636

GiteaMirror referenced this issue

2026-04-30 02:32:57 -05:00

[PR #23064] [CLOSED] fix: pin 49 unpinned action(s),extract 4 unsafe expression(s) to env vars #50054