Skip to content

ru: fix 25 factually wrong fuzzy entries#3184

Open
yabanci wants to merge 1 commit into
google:mainfrom
yabanci:chore/ru-fix-fuzzy
Open

ru: fix 25 factually wrong fuzzy entries#3184
yabanci wants to merge 1 commit into
google:mainfrom
yabanci:chore/ru-fix-fuzzy

Conversation

@yabanci
Copy link
Copy Markdown

@yabanci yabanci commented May 21, 2026

This PR fixes a narrow set of po/ru.po entries where the existing fuzzy translation is factually wrong — different concept, swapped link, wrong day number, broken markdown, etc. — not where it's merely stylistically outdated. The other ~50 fuzzy entries are left with their #, fuzzy flag untouched for @baltuky (the original translator) to revisit on their own pace.

Scope

Wrong chapter titles in SUMMARY

msgid was now
Associated Types Скалярные типы Ассоциированные типы
Shared Types (C++ interop) Скалярные типы Общие типы
Try Conversions Неявные преобразования Преобразования через Try
Marker Traits Небезопасные типажи Маркерные типажи
Shared References Заимствование (= different section) Общие ссылки

msgmerge nearest-match garbage. Six chapter-link entries had been overwritten with the recurring "Больше информации об использовании шаблонов..." boilerplate or with an unrelated link — replaced with correct ones: [Static], [Pattern Matching], [Matching Values], [Deriving], [Strings], [Marker Traits] (which pointed at the Arrays link).

Wrong body translations

  • Native support for Rust slices in C++ → was "Встроенная поддержка тестирования" (slices ≠ testing)
  • `while let` expressions and `let else` expressions → both were "Выражение if let"
  • while-let (anchor) → was "Выражение while let" (anchor name vs section title)
  • Lives for the entire duration of the program → was "Функция main является точкой входа в программу"
  • Storing Books → was "Строки" (Books ≠ Strings)
  • An exercise on pattern matching. → was about enums + pattern matching
  • Welcome to Day 4 → was "Добро пожаловать в День 1"
  • Can be scaled down to very constrained devices such as microcontrollers. → was "...мобильные телефоны" (microcontrollers ≠ phones)
  • Some things to try: → was "Примечания:" (notes ≠ things to try)

Wrong code literals

  • "Welcome to RustOS 3.14" → was "Добро пожаловать в День 1"
  • "Hello " → was "Привет, мир!" (different literal)

Broken markdown links (literally not rendering as links)

  • Two After looking at the exercises... [solutions](solutions-*.md) entries had \\[solutions\\] with escaped brackets and no working link target.

Terminology

Followed the existing glossary in ru.po (Trait → Типаж, Borrow → Заимствование, Closure → Замыкание, Slice → Срез, Lifetime → Время жизни) and the established RU Rust canon for the new replacements (Marker Traits → Маркерные типажи; #[derive] → Вывод типажей). Shared/Exclusive References intentionally kept as Общие/Эксклюзивные ссылки, matching the modern shared/exclusive terminology that this course uses (not the older immutable/mutable framing) — happy to switch if reviewers prefer the canonical RU Book "неизменяемые/изменяемые".

Verification

$ msgfmt --statistics -o /dev/null po/ru.po
574 translated messages, 50 fuzzy translations, 3136 untranslated messages.

(Before: 552 translated, 72 fuzzy, 3136 untranslated. Δ = +22 translated, −22 fuzzy.)

@google-cla
Copy link
Copy Markdown

google-cla Bot commented May 21, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@yabanci
Copy link
Copy Markdown
Author

yabanci commented May 21, 2026

@googlebot I signed it!

@yabanci yabanci force-pushed the chore/ru-fix-fuzzy branch 2 times, most recently from b19dc69 to 234681c Compare May 21, 2026 12:17
Limited to entries where the existing translation is incorrect (not
stylistic disagreement). Other fuzzy entries left untouched for the
original translator to revisit.

Wrong chapter titles in SUMMARY:
- Associated Types: was 'Скалярные типы' (different concept)
- Shared Types (C++ interop): was 'Скалярные типы'
- Try Conversions: was 'Неявные преобразования' (different class of conversions)
- Marker Traits: was 'Небезопасные типажи' (Marker ≠ Unsafe)
- Shared References: was 'Заимствование' (name of a different section)

msgmerge nearest-match garbage (chapter-link entries had all been
overwritten with 'Больше информации об использовании шаблонов...'):
- [Static] (5 minutes), [Pattern Matching] (1 hour), [Matching Values]
  (10 minutes), [Deriving] (3 minutes), [Strings] (10 minutes)
- [Marker Traits] (2 minutes) had been overwritten with the link for Arrays

Wrong body translations:
- 'Native support for Rust slices in C++': was 'Встроенная поддержка тестирования'
- 'while let expressions' and 'let else expressions': both were 'Выражение if let'
- 'while-let' (anchor): was 'Выражение while let' (section title vs anchor)
- 'Lives for the entire duration of the program': was 'Функция main является точкой входа в программу'
- 'Storing Books': was 'Строки' (Books ≠ Strings)
- 'An exercise on pattern matching.': was about enums + pattern matching
- 'Welcome to Day 4': was 'Добро пожаловать в День 1'
- 'Can be scaled down to very constrained devices such as microcontrollers':
  was '...мобильные телефоны' (microcontrollers ≠ phones)
- 'Some things to try:': was 'Примечания:' (notes ≠ things to try)

Wrong code literals:
- '"Welcome to RustOS 3.14"': was '"Добро пожаловать в День 1"'
- '"Hello "': was '"Привет, мир!"' (different literal)

Broken markdown links (rendering literally broken):
- 'After looking at the exercises, you can look at the [solutions]...':
  was '...изучить предоставленные \\[solutions\\]' (escaped brackets, no link)
@yabanci yabanci force-pushed the chore/ru-fix-fuzzy branch from 234681c to b10bfec Compare May 21, 2026 12:33
@yabanci yabanci changed the title ru: resolve all 97 fuzzy entries ru: fix 25 factually wrong fuzzy entries May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant