Skip to content

i18n(nav): add 'The Bet' translation across all 22 locales#293

Merged
0800tim merged 1 commit into
mainfrom
i18n/nav-the-bet
Jun 5, 2026
Merged

i18n(nav): add 'The Bet' translation across all 22 locales#293
0800tim merged 1 commit into
mainfrom
i18n/nav-the-bet

Conversation

@0800tim

@0800tim 0800tim commented Jun 5, 2026

Copy link
Copy Markdown
Owner

Tim 2026-06-05 caught the dev-only MISSING_MESSAGE: Could not resolve nav.the_bet in messages for locale en next-intl error. PR #284 wired the nav entry against nav.the_bet but never added the catalogue entry. safeT was catching the miss and rendering the English literal fallback so the page never broke; this just makes the lookup find a real string.

22 locales updated. Romance/Germanic/Slavic/Turkic get a literal translation; CJK uses brand transliteration (ja/ko) or 豪赌 "big wager" (zh-CN); RTL uses the language's bet/wager noun.

Tim 2026-06-05 caught the dev-only next-intl error:

  > MISSING_MESSAGE: Could not resolve `nav.the_bet` in messages
  > for locale `en`.

The nav entry was wired in PR #284 against the key `nav.the_bet`
but the locale catalogues were never updated. `safeT` catches the
miss and renders the literal "The Bet" fallback so the page never
broke, but in dev mode next-intl throws and the overlay reports the
miss every render.

Translation spread:

* Romance / Germanic / Slavic / Turkic: literal "the bet" in the
  target language (La Apuesta, Le Pari, Die Wette, La Scommessa,
  A Aposta x2, De Weddenschap, Vadet, Veddemålet, Sázka, A Fogadás,
  Bahis, Oklada x2, Garov).
* CJK: ja / ko use a brand transliteration (ザ・ベット, 더 베트);
  zh-CN uses 豪赌 ("big wager") for punch since literal "the bet"
  reads flat.
* RTL: ar / fa use the language's bet/wager noun (الرهان, شرط‌بندی).
* mi: Te Whakapae (the contest / wager).

22 catalogues updated, every existing key preserved (Python JSON
round-trip with ensure_ascii=False so non-Latin scripts stay
readable in source).

Signed-off-by: Tim Thomas <0800tim@gmail.com>
@0800tim 0800tim merged commit 9daf8b4 into main Jun 5, 2026
11 of 12 checks passed
@github-actions

github-actions Bot commented Jun 5, 2026

Copy link
Copy Markdown

DRY-RUN — this verdict is informational; CI is not blocked.

Auto-triage: GREEN — auto-triage clear

Risk score: 0/100

Metric Value
Files changed 22
Lines added 44
Lines removed 22
Apps touched apps/web
New dependencies 0
New 3rd-party hosts 0

No flags raised by the automated scanners. A human reviewer will still take a look.

Labels applied: area:web, auto-triage:green

Posted by @vtorn/pr-triage-bot. How this works: docs/security/01-pr-triage-process.md. Disagree with the verdict? Comment /triage override <reason> and a maintainer will re-review.

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