Thanks to visit codestin.com
Credit goes to github.com

Skip to content

i18n: fix Russian wording and translate default prompt suggestions - #29797

Open
CommanderTvis wants to merge 1 commit into
open-webui:devfrom
CommanderTvis:i18n/ru-fixes
Open

i18n: fix Russian wording and translate default prompt suggestions#29797
CommanderTvis wants to merge 1 commit into
open-webui:devfrom
CommanderTvis:i18n/ru-fixes

Conversation

@CommanderTvis

@CommanderTvis CommanderTvis commented Sep 8, 2026

Copy link
Copy Markdown

Pull Request

Checklist

  • This PR targets the dev branch.
  • This PR links to a well-described, confirmed Issue or active Discussion: Closes #___ / Relates to #___.
  • A maintainer explicitly asked me to open this PR, or this PR only updates i18n/localization.
  • The change is one logical unit with no unrelated commits.
  • I matched nearby code patterns and avoided unnecessary new settings, abstractions, or dependencies.
  • I manually tested the changed workflow and any nearby behavior that could be affected.
  • 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.
  • I reviewed any AI-generated code before submitting it.
  • The PR title uses one of the prefixes listed below.

Summary

Follow-up to the recent ru-RU completion (#29586, #29601, #29625, #29794) based on reviewing the Russian UI end to end.

ru-RU wording fixes

  • * Engine → «Система …» instead of the literal «Механизм …» (Code Interpreter / Code Execution / Content Extraction / Image Generation)
  • «Удалить ВСЕ Чаты», «Удалить ВСЕ», «По умолчанию ВСЕ» → normal case
  • Untranslated "LLM"/"LLMs" inside Russian sentences → «языковая модель / языковые модели» (7 strings)
  • «Обмен с сообществом» → «Публикация в сообществе»
  • «Экспериментальное» → «Экспериментально» (label is a badge, not an adjective)
  • Filled the two remaining empty ru-RU strings (Formatting + its description)

Default prompt suggestions were never localized
The home-screen suggestions come from DEFAULT_PROMPT_SUGGESTIONS in backend config and were rendered raw, so they stayed in English in every locale. Suggestions.svelte now passes title and content through $i18n.t(); admin-defined suggestions that have no key fall through unchanged (i18next returns the input). The six default strings are registered in the component so i18n:parse keeps their keys — that is why every other locale gains 18 empty keys. Russian is translated; other locales can fill them as usual.

Testing

  • npm run i18n:parse → clean tree
  • npx eslint src/lib/components/chat/Suggestions.svelte → clean
  • Ran frontend + backend locally with ru-RU: Settings › Code Execution, Data Controls, Personalization, Admin › General, and the home screen suggestions all show the new strings; custom suggestions still render.

Changelog Entry

Added

  • i18n: default prompt suggestions on the home screen are now translatable (ru-RU translated).

Changed

  • i18n: Russian wording fixes (engine labels, "ВСЕ" casing, "LLMs", Community Sharing, Experimental badge).

Fixed

Removed

Security

Breaking Changes

Additional Context

The 63 non-Russian locale diffs are the 18 empty keys added by i18n:parse; no existing translations were touched there.

Contributor License Agreement

🤖 Generated with Claude Code

https://claude.ai/code/session_01J7AD9p4feC4e9pAt77dbdj

@CommanderTvis

Copy link
Copy Markdown
Author

🤖 Claude (via Claude Code): @EllaFr could you take a look at this one for review? Small ru-RU wording follow-up plus making the default prompt suggestions translatable.

@CommanderTvis
CommanderTvis force-pushed the i18n/ru-fixes branch 2 times, most recently from 85cb98b to 2baaae1 Compare September 8, 2026 18:40
@EllaFr

EllaFr commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Thank you for the ru-RU wording fixes; I’ll take a look.

Regarding prompt suggestion translations, we’ve added support for language-specific suggestions in current dev:

  1. Go to Models > Model Defaults > Configure > Prompt Suggestions.
  2. Click the new language dropdown (globe icon) and select a language.
  3. Enter the translated title and content, then save.
  4. When a user’s interface language matches that language (e.g., Russian), selecting that model will display the translated suggestions instead of the defaults.

Let me know if that's what you're referring to!

image

@CommanderTvis

CommanderTvis commented Sep 8, 2026

Copy link
Copy Markdown
Author

🤖 Claude (via Claude Code): Thanks — yes, I've seen the per-language suggestions in Model Defaults, and that covers the admin-configured case well.

The Suggestions.svelte change here is aimed at the other case: a fresh instance where nobody has configured anything. The six built-in defaults from DEFAULT_PROMPT_SUGGESTIONS then show up in English on a Russian UI, and they're the only untranslated thing on the home screen. Passing them through $i18n.t() makes the out-of-the-box defaults follow the interface language with no admin setup; anything configured via Model Defaults / the i18n map still takes precedence exactly as before, since those strings just don't have a key and fall through unchanged.

If you'd rather keep suggestions purely config-driven, I'm happy to drop that part.

Replace unnatural ru-RU phrasing ("Механизм … engine", shouting "ВСЕ",
untranslated "LLMs", "Обмен с сообществом", "Экспериментальное") and fill
the two remaining empty strings.

Default prompt suggestions come from backend config and were never passed
through i18n, so the home screen stayed in English regardless of locale.
Suggestions.svelte now translates titles and content; custom admin
suggestions fall through unchanged. The default strings are registered as
keys so `i18n:parse` keeps them, which adds the empty keys to every locale.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_01J7AD9p4feC4e9pAt77dbdj
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants