Skip to content

i18n: Russian translates 114 status and error messages that no catalog had - #7482

Merged
bflatastic merged 3 commits into
storytold:mainfrom
dotCooCoo:fix/ru-missing-message-rows
Nov 14, 2026
Merged

bflatastic merged 3 commits into
storytold:mainfrom
dotCooCoo:fix/ru-missing-message-rows

Conversation

@dotCooCoo

Copy link
Copy Markdown
Contributor

What and why

On main at 1e4e353, untranslated_report (crates/ui-egui/src/i18n/tests.rs) lists 167 status and error messages under "messages, all 23 languages checked": no complete-message catalog has a row for them. With the interface in Russian, these messages were shown in English.

This is the Russian part of the missing message rows, as #7423 (French), #7430 (Spanish) and #7463 (Japanese). #7337 adds Russian rows for the messages that other catalogs already translate; none of its rows is among these 114. No other open pull request that changes ru.tsv adds one of these 114 messages, #7468 included, and git merge-tree with #7468's head merges without a conflict.

How it was tested

The change adds catalog rows only, so it has no new test. untranslated_report is a report that does not fail on a gap. After the change, its "messages, all 23 languages checked" list has 53 entries, each of them a row that #7211, #7378 or #7405 adds, and its Russian message list holds none of the 114 messages.

Focused checks on the final tree, which merges main at e56d1c7:

  • cargo fmt --all -- --check
  • cargo clippy -p vectorcraft-ui-egui --all-targets -- -D warnings
  • cargo check --workspace --tests
  • cargo test -p vectorcraft-ui-egui --lib i18n: 115 passed, 0 failed.
  • cargo xtask brands; cargo xtask layers (30 crates, no layering violations); cargo xtask assets (337 asset files attributed).
  • cargo xtask ci runs in this pull request's CI.

Checklist

  • cargo xtask ci passes (fmt, clippy, tests, assets, brands, layers, wasm).
  • No panics in shipped code: no unwrap(), expect(), panic!, unreachable!, todo! or
    unimplemented! outside tests, and no unchecked indexing on data from files, parameters or
    messages. Errors are returned as Result and shown to the user
    (why and how).
  • Clean-room: nothing copied from Adobe products or GPL/AGPL code (AGENTS.md).
  • Every new asset has a row in ASSETS.md.

…g had

untranslated_report lists 167 messages under "messages, all 23 languages
checked". ru.tsv gains an @msg row for 114 of them, in one block at the end
of the file: image export and encoding errors, color profiles, color books
and swatch exchange files, binary DXF and DWG import, 3D and Revolve limits,
and script, zip, line and file errors. Placeholders, parameter names and
literal values stay as the English writes them.

The other 53 are left to the open pull requests that translate them
(composite fonts, SVG filters, read roots and graph design).
@coderabbitai

coderabbitai Bot commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters: 1

  • crates/ui-egui/src/i18n/ru.tsv is excluded by !**/*.tsv

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@bflatastic

Copy link
Copy Markdown
Member

Merged, thanks @dotCooCoo! It passed its CI checks.

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