Skip to content

Add Russian (ru) translation - #704

Open
mushketer888 wants to merge 1 commit into
barebaric:mainfrom
mushketer888:feat/russian-translation
Open

mushketer888 wants to merge 1 commit into
barebaric:mainfrom
mushketer888:feat/russian-translation

Conversation

@mushketer888

@mushketer888 mushketer888 commented Nov 13, 2026 •

Copy link
Copy Markdown

What does this PR change?

Adds complete Russian (ru) gettext catalogs for the main app with no untranslated or fuzzy strings. Registers the language: "ru" in SUPPORTED_LANGUAGES, a "Russian" label in the language selector, and an AppStream summary.

Why did you choose this specific architectural approach?

Mirrors the existing per-language structure (like uk/de), so no loading changes were needed. SUPPORTED_LANGUAGES
registration is required, otherwise normalize_language_code() rejects ru and the catalogs stay unreachable.

How did you manually test this locally?

  1. Built from source (MSYS2/UCRT64) and ran the app with LANGUAGE=ru; UI renders in Russian.
  2. Confirmed normalize_language_code('ru_RU') → ru and "Russian" appears in the selector.
  3. Used the app in Russian for a while.

Checklist

  • I am not an AI. I have manually read the code and understand it.
  • I take full responsibility for the quality and architectural fit of
    this code.
  • I agree to publish this code under the MIT license.

Add complete Russian gettext catalogs for the main application and all
six addons that ship locale catalogs:

- rayforge/locale/ru/LC_MESSAGES/rayforge.po (2341 entries)
- ai_workpiece_generator (11), automation (8), laser_essentials (193),
  post_processors (79), print_and_cut (47), sketcher (217)

All msgids from the current POT files are translated with no fuzzy or
untranslated entries. Placeholder tokens and python-brace-format flags
are preserved in every message, including plural forms.

Register the new language so it is reachable: add 'ru' to
SUPPORTED_LANGUAGES (language selector, system language detection)
with its label, and a Russian summary to the AppStream metainfo.
@github-actions

Copy link
Copy Markdown

This pull request was closed automatically because its description does not follow the pull request template. Problems found:

  • section "What does this PR change?" is not filled out
  • section "Why did you choose this specific architectural approach?" is missing

Please edit the pull request description to answer every section and to tick every checkbox; as soon as it complies, the pull request is reopened automatically. See CONTRIBUTING.md.

@github-actions github-actions Bot closed this Nov 13, 2026
@github-actions github-actions Bot added the invalid-template Does not follow the pull request template label Nov 13, 2026
@github-actions github-actions Bot removed the invalid-template Does not follow the pull request template label Nov 13, 2026
@github-actions github-actions Bot reopened this Nov 13, 2026
@github-actions

Copy link
Copy Markdown

The description now follows the pull request template, so this pull request was reopened automatically.

This branch was previously deployed

1 inactive deployment
pypi — 3c8e1f06 Deployed Nov 13, 2026 by mushketer888 via Build and Publish Wheel #2635
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.

1 participant