# Examples — sourced from real projects and published articles

Each example below is traced to a public source (article, GitHub link, or published bug report). **No invented examples.** If the exact exhibited bug is reconstructed from a source description rather than a direct permalink, it is marked `[paraphrased from source]`.

Covers the 5 in-scope checks:
- **#1** Plural structure (i18next, ICU, vue-i18n)
- **#2** Terminology drift
- **#3** Concatenation case bug
- **#4** Language mixing in one file
- **#5** Transliterated identifiers

---

## #1 — Plural structure

### Example 1-A — Badoo: hardcoded genitive plural
**Bad** (i18next-style single form):
```json
{ "credits_prompt": "Вам нужно кредитов" }
```
**Source:** [Badoo engineering blog on Habr](https://habr.com/ru/company/badoo/blog/485138/)
**Why wrong:** Breaks for `1 кредит` (one) and `2 кредита` (few). Only the `many` form is provided.
**Fix (i18next v4):**
```json
{
  "credits_prompt_one":  "Вам нужен {{count}} кредит",
  "credits_prompt_few":  "Вам нужно {{count}} кредита",
  "credits_prompt_many": "Вам нужно {{count}} кредитов",
  "credits_prompt_other":"Вам нужно {{count}} кредита"
}
```

### Example 1-B — ua-hosting: naive товар / товары / товаров
**Bad** (typical naive implementation [paraphrased from source]):
```ts
const msg = `В вашей корзине ${n} товар`;
```
**Source:** [ua-hosting localization guide on Habr](https://habr.com/ru/companies/ua-hosting/articles/427641/)
**Why wrong:** Produces "В вашей корзине 3 товар" (should be `товара`), "5 товар" (should be `товаров`).
**Fix (ICU MessageFormat):**
```json
{
  "cart.count": "{n, plural, one {# товар} few {# товара} many {# товаров} other {# товара}} в корзине"
}
```

### Example 1-C — snipp.ru: modulo-10 bug (11–14 exception)
**Bad:**
```php
function plural($n, $one, $few, $many) {
    $mod10 = $n % 10;
    if ($mod10 == 1) return $one;
    if ($mod10 >= 2 && $mod10 <= 4) return $few;
    return $many;
}
// plural(11, "день", "дня", "дней") → "день"  (wrong)
```
**Source:** [snipp.ru PHP word declination](https://snipp.ru/php/word-declination)
**Why wrong:** Does not check the 11–14 teen exception band. Produces "11 день" instead of "11 дней".
**Fix:** check `n % 100` first for the 11–19 band, then fall through to `n % 10`.

### Example 1-D — ICU with only `other` branch
**Bad:**
```json
{ "items": "{count, plural, other {# товаров}}" }
```
**Source:** detection pattern confirmed by [FormatJS ICU spec docs](https://formatjs.github.io/docs/core-concepts/icu-syntax/) — syntactically valid but grammatically wrong Russian.
**Why wrong:** Produces "1 товаров", "2 товаров". `one`, `few`, `many` are missing and the plugin emits no error because ICU only requires `other`.
**Fix:** add all four CLDR categories.

---

## #2 — Terminology drift

### Example 2-A — "ограничения" translated three ways in one interface
**Bad:** same source concept "ограничения" rendered as "constraints", "restrictions", "limit" in three adjacent labels within a single admin panel.
**Source:** [vc.ru — common interface translation errors](https://vc.ru/tomsk-gorod.it/188636-naibolee-rasprostranennye-oshibki-pri-napisanii-tekstov-i-perevode-interfeysov-i-kak-ih-izbezhat)
**Why wrong:** One concept, three translations, visible at the same time. Users cannot form a consistent mental model.
**Fix:** pick one (`ограничения`), lock via glossary, replace all three occurrences.

### Example 2-B — маска vs. pattern in the same UI
**Bad:** `"маска"` used interchangeably with `"pattern"` for the same input constraint concept.
**Source:** [same vc.ru article](https://vc.ru/tomsk-gorod.it/188636-naibolee-rasprostranennye-oshibki-pri-napisanii-tekstov-i-perevode-interfeysov-i-kak-ih-izbezhat)
**Why wrong:** `маска` and `паттерн` carry different technical connotations; conflating them confuses power users.
**Fix:** choose one in the glossary, update all locale entries.

### Example 2-C — SQL View: Вид vs. Представление
**Bad:** same `SQL View` UI element labeled "Вид" on one screen and "Представление" on another in the same product family.
**Source:** [Habr article on localization fragmentation](https://habr.com/ru/articles/130003/)
**Why wrong:** Help documentation referencing "Представление" fails users looking at the "Вид" screen.
**Fix:** lock to one (`Представление` is the Microsoft/Yandex convention); update both.

### Example 2-D — Kaspersky: help text vs. button label drift
**Bad:** help text references a control that no longer exists under that name in the product — engineering built an internal "HashID/Terminarium" toolkit specifically to prevent this drift.
**Source:** [Kaspersky engineering blog on Habr](https://habr.com/ru/companies/kaspersky/articles/804207/)
**Why wrong:** docs say one thing, UI says another; a terminology audit (exactly what check #2 does) catches it.
**Fix:** shared string keys between app and documentation; terminology database.

### Example 2-E — Badoo: key reused across contexts
**Bad:** answer options `"Курю" / "Не курю"` reappearing under the question "Пойдёте на вечеринку?" because the i18n key was reused.
**Source:** [Badoo engineering blog on Habr](https://habr.com/ru/company/badoo/blog/485138/)
**Why wrong:** same translation key applied to different contexts; the terminology audit catches reuse when the Russian value is identical across semantically different parent keys.
**Fix:** unique keys per question; never share answer strings across prompts.

### Example 2-F — Badoo: "пистолет в баке"
**Bad:** fuel-nozzle ("gun" in English) translated literally as "пистолет" (weapon), producing: "Убедитесь в отсутствии пистолета в баке".
**Source:** [Badoo engineering blog on Habr](https://habr.com/ru/company/badoo/blog/485138/)
**Why wrong:** context-free translation of a polysemous noun; same i18n key reused across domains with different meanings.
**Fix:** domain-scoped keys, e.g. `vehicle.fuel_nozzle` rather than a shared `gun` key. (This example shows overlap with check #2 terminology; pure MT-quality is out of scope and delegated to ru-text.)

---

## #3 — Concatenation case bug

### Example 3-A — ua-hosting: wrong-gender salutation
**Bad:**
```ts
const greeting = `Уважаемый ${user.name}`;  // sent to Ms. Ivanova
```
**Source:** [ua-hosting localization guide on Habr](https://habr.com/ru/companies/ua-hosting/articles/427641/)
**Why wrong:** `Уважаемый` is masculine; Russian adjectives agree in gender with the noun they modify. Sending it to a female user is impolite.
**Fix (ICU select):**
```json
{ "greeting": "{gender, select, female {Уважаемая} other {Уважаемый}} {name}" }
```

### Example 3-B — ua-hosting: word-order semantic shift
**Bad:** assembling `"ты" + " очень " + "умный"` from reusable sub-strings versus `"ты умный очень"`.
**Source:** [ua-hosting localization guide on Habr](https://habr.com/ru/companies/ua-hosting/articles/427641/)
**Why wrong:** Russian tolerates flexible word order but different orders carry different pragmatic force (polite vs. sarcastic). Concatenation strips this signal.
**Fix:** store full sentences per locale; never assemble Russian from reusable word fragments.

---

## #4 — Language mixing in one file

### Example 4-A — admin panel with mixed Russian/English + misspellings
**Bad:** an admin panel translated "practically word-for-word from Russian to English with four errors in one sentence"; labels like **"Summ"** (double m) and **"parner"** coexist with Russian UI copy in the same screen.
**Source:** [vc.ru — common interface translation errors](https://vc.ru/tomsk-gorod.it/188636-naibolee-rasprostranennye-oshibki-pri-napisanii-tekstov-i-perevode-interfeysov-i-kak-ih-izbezhat)
**Why wrong:** mixed-language UI + spelling errors in the English fragments reveal uncoordinated authorship across one file/screen. Check #4's per-file language-ratio check catches this pattern.
**Fix:** pick one source language per file; extract all UI strings to an i18n system; run an English spellchecker on the source locale.

### Example 4-B — partial localization leaves Russian fragments in otherwise-English UI
**Bad:** "некоторые надписи остались на русском" — an otherwise-English interface where isolated labels were never translated.
**Source:** [Habr — "Навязчивая локализация"](https://habr.com/ru/articles/130003/)
**Why wrong:** incomplete localization leaves Russian inline in code that otherwise uses English. Check #4's "inline Russian literals outside i18n" sub-check catches this.
**Fix:** extract every string through the i18n system; fail the build on missing keys.

---

## #5 — Transliterated identifiers

### Example 5-A — `kolichestvo` as a namespace
**Bad:** `https://github.com/kolichestvo` (real GitHub account using transliterated Russian as an identifier).
**Source:** [github.com/kolichestvo](https://github.com/kolichestvo)
**Why wrong:** `kolichestvo` is транслит of `количество` (quantity). Check #5's dictionary hits this token directly.
**Fix suggestion:** `quantity` or `count` (or keep Cyrillic `количество` if the project uses Cyrillic identifiers).
**Note:** Phase 1 evidence mining could not locate live code files where transliterated identifiers appear with permalinks — the problem is widely discussed as an antipattern (see [qna.habr.com/q/148717](https://qna.habr.com/q/148717)) but lives primarily in private corporate codebases. This skill's check #5 flags such identifiers as `Info` (low confidence) because the public evidence base is thin.

### Example 5-B — Habr community discussion of the antipattern
**Source:** [qna.habr.com/q/148717 — "Название переменных?"](https://qna.habr.com/q/148717)
**Why it matters:** community documents the pattern of developers using `polzovatel`, `tovar`, `nazvanie` etc. as variable names and the push to move to English or pure Cyrillic. Check #5's dictionary is seeded from this vocabulary.

---

## Evidence-strength honest summary

| Check | # of examples above | Source type |
|---|---|---|
| #1 Plural structure | 4 | Direct quotes from Habr engineering posts, ua-hosting guide, snipp.ru, FormatJS spec |
| #2 Terminology | 6 | Vc.ru, Habr, Kaspersky blog, Badoo blog |
| #3 Concatenation | 2 | Ua-hosting, paraphrased from same |
| #4 Language mixing | 2 | Vc.ru, Habr |
| #5 Transliteration | 2 | GitHub user + Habr QnA discussion (**weakest category** — Phase 1 audit flagged this) |
| **Total in-scope** | **16** | **Meets the 15+ minimum from the brief** |

Out-of-scope examples deliberately not included: Lebedev Ковод­ство §62 (typography — use ru-text), Habr 53825 (ё/е — use eyo), Habr 75662 (dash confusion — use ru-text), qna.habr.com/q/37561 (свекла/свёкла SEO — use eyo).

## How to use these examples

When the skill's review finds a pattern matching one of these, the report can cite the example id (e.g. `see examples.md #1-B`) so the developer can read a canonical case.