feat(i18n): add Russian locale

[bubelov]

It's not perfect but that's a solid start

Summary by CodeRabbit

Release Notes

• New Features
  • Russian language support is now available. Users can select Russian from the language switcher in the footer to experience the full interface in Russian.

[netlify]

✅ Deploy Preview for btcmap ready!

Name	Link
🔨 Latest commit	4e2e527
🔍 Latest deploy log	https://app.netlify.com/projects/btcmap/deploys/69a985e23a9c6d0008db89c4
😎 Deploy Preview	https://deploy-preview-793--btcmap.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 57 (🔴 down 38 from production) Accessibility: 97 (no change from production) Best Practices: 92 (🔴 down 8 from production) SEO: 98 (🔴 down 1 from production) PWA: 90 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds Russian language support to the application by introducing locale registration in the i18n system, extending the footer language-switcher UI with a new Russian button, and providing comprehensive Russian translations for all user-facing text throughout the application.

Changes

Cohort / File(s)	Summary
Footer Language Switcher src/components/layout/Footer.svelte	Adds a new RU language button that toggles the locale to 'ru', mirrors existing EN/PT/BG button styling, includes ARIA labels, and disables itself when Russian is active.
i18n Configuration src/lib/i18n/index.ts	Registers Russian ('ru') as a supported locale, updates SUPPORTED_LOCALES constant, and extends initial locale detection to recognize browser language preference for Russian.
Russian Translations src/lib/i18n/locales/ru.json	Introduces comprehensive Russian translation file with 1097 lines covering UI text across all application modules including home, navigation, search, categories, maps, merchants, payments, dashboards, leaderboards, communities, forms, and support sections.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• PR #701: Adds Russian locale support and RU button in the same location (i18n registration and footer language-switcher), indicating potential duplicate or related localization work
• PR #709: Modifies i18n system and locale resources, suggesting overlapping localization infrastructure changes
• PR #771: Updates footer language-switcher and i18n locale configuration, indicating related changes to language support

Suggested reviewers

• escapedcat

Poem

🐰 Whiskers twitch with joy so bright,
Russian words now set just right!
Buttons click and locales flow,
From Moscow to the web we go! 🌍✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimally informative and largely incomplete, lacking required template sections like issue reference, detailed change description, screenshots, and context.	Expand the description to include a related issue reference, detailed explanation of changes made (new locale file, SUPPORTED_LOCALES update, UI button), and any relevant context about completeness.
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat(i18n): add Russian locale' accurately summarizes the main change—adding Russian language support to the i18n system.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch translate-ru

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[qodo-code-review]

Review Summary by Qodo

Add Russian locale support with translations and language switcher

✨ Enhancement

Walkthroughs

Description

• Add Russian locale support with 1097 translation strings
• Register Russian language in i18n configuration
• Add Russian language switcher button to footer
• Implement browser language detection for Russian

Diagram

flowchart LR
  A["i18n Configuration"] -->|register| B["Russian Locale"]
  B -->|lazy load| C["ru.json Translation File"]
  D["Browser Language Detection"] -->|detect ru| B
  E["Footer Component"] -->|add button| F["Russian Language Switcher"]
  F -->|switch to| B

Loading

File Changes

1. src/lib/i18n/locales/ru.json Localization +1097/-0

Add complete Russian locale translation file

• Add comprehensive Russian translation file with 1097 strings
• Cover all UI sections including home, navigation, search, categories, merchant details, payments,
 boosts, comments, forms, and more
• Include translations for error messages, success messages, warnings, and accessibility labels
• Provide Russian translations for community features, leaderboards, and administrative functions

src/lib/i18n/locales/ru.json

---

2. src/lib/i18n/index.ts Configuration +3/-1

Register Russian locale and enable language detection

• Register Russian locale with lazy loading from ./locales/ru.json
• Add "ru" to SUPPORTED_LOCALES constant array
• Add Russian language detection in getInitialLocale() function to check for navigator.language
 starting with "ru"

src/lib/i18n/index.ts

---

3. src/components/layout/Footer.svelte ✨ Enhancement +14/-0

Add Russian language switcher to footer

• Add Russian language button next to Bulgarian language button
• Include separator span between Bulgarian and Russian buttons
• Implement click handler to switch language to 'ru'
• Add proper styling classes and aria-label for accessibility
• Set disabled state when Russian locale is already active

src/components/layout/Footer.svelte

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Missing RU switch translation 🐞 Bug ✓ Correctness

Description

The new RU footer button uses footer.switchToRussian for its aria-label, but that key is missing
from existing locales (en/pt-BR/bg). This will likely render a raw key string as the aria-label
(accessibility regression) for most users.

Code

src/components/layout/Footer.svelte[R108-114]

+			<span class="text-body dark:text-white/50"> / </span>
+			<button
+				type="button"
+				on:click={() => switchLanguage('ru')}
+				disabled={$locale === 'ru'}
+				aria-label={$_('footer.switchToRussian')}
+				class="

Evidence

Footer introduces a new RU button whose aria-label depends on footer.switchToRussian. i18n is
configured with fallbackLocale: "en", but en.json (and pt-BR.json/bg.json) do not define
switchToRussian, so there is no available translation in current or fallback locales.

src/components/layout/Footer.svelte[108-121]
src/lib/i18n/index.ts[37-41]
src/lib/i18n/locales/en.json[307-320]
src/lib/i18n/locales/pt-BR.json[295-308]
src/lib/i18n/locales/bg.json[305-318]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A new RU language switch button uses `$_('footer.switchToRussian')` for `aria-label`, but `switchToRussian` is missing from non-Russian locale JSON files. This causes the aria-label to fall back to a raw key string, harming accessibility.

## Issue Context
`svelte-i18n` is configured with `fallbackLocale: 'en'`. If the key is missing in the current locale and in `en`, the UI will not have a meaningful aria-label.

## Fix Focus Areas
- src/lib/i18n/locales/en.json[307-320]
- src/lib/i18n/locales/pt-BR.json[295-308]
- src/lib/i18n/locales/bg.json[305-318]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. RU country names fallback 🐞 Bug ✓ Correctness

Description

After enabling ru as a supported UI locale, country name localization will still fall back to the
provided (likely English/OSM) names because getCountryName only maps/loads en, pt-BR, and bg
locales.

Code

src/lib/i18n/index.ts[R7-10]

+register("ru", () => import("./locales/ru.json"));

-export const SUPPORTED_LOCALES = ["en", "pt-BR", "bg"] as const;
+export const SUPPORTED_LOCALES = ["en", "pt-BR", "bg", "ru"] as const;

Evidence

The PR makes ru a supported locale and registers it for UI translations. Country list UIs pass the
current $locale into getCountryName, but getCountryName maps locales through localeMap which
does not include ru, so it falls back to en behavior and returns the unlocalized fallback name.

src/lib/i18n/index.ts[4-10]
src/routes/countries/[section]/components/CountryCard.svelte[13-18]
src/lib/countryNames.ts[5-9]
src/lib/countryNames.ts[32-36]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
With `ru` now supported for UI translations, country names shown via `getCountryName(...)` will not be localized to Russian because `localeMap`/`localeLoaders` do not include `ru`.

## Issue Context
Country list and country pages pass the current `$locale` into `getCountryName`. For `ru`, `getCountryName` falls back to English behavior and returns the fallback name.

## Fix Focus Areas
- src/lib/countryNames.ts[5-21]
- src/lib/countryNames.test.ts[6-31]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[qodo-code-review]

1. Missing ru switch translation 🐞 Bug ✓ Correctness

The new RU footer button uses footer.switchToRussian for its aria-label, but that key is missing
from existing locales (en/pt-BR/bg). This will likely render a raw key string as the aria-label
(accessibility regression) for most users.

Agent Prompt

## Issue description
A new RU language switch button uses `$_('footer.switchToRussian')` for `aria-label`, but `switchToRussian` is missing from non-Russian locale JSON files. This causes the aria-label to fall back to a raw key string, harming accessibility.

## Issue Context
`svelte-i18n` is configured with `fallbackLocale: 'en'`. If the key is missing in the current locale and in `en`, the UI will not have a meaningful aria-label.

## Fix Focus Areas
- src/lib/i18n/locales/en.json[307-320]
- src/lib/i18n/locales/pt-BR.json[295-308]
- src/lib/i18n/locales/bg.json[305-318]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[escapedcat]

Long words breaking our design

But it's better than nothing and we can think about how to solve this.
Either for now just wrap it differently or a more complex solution.
I think wrapping can be a good first step for now.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/lib/i18n/locales/ru.json`:
- Line 536: Replace the misspelled and spacing errors in ru.json: change
"обьединяйтесь" to "объединяйтесь" in the value for the "description" entry that
currently contains "Возьмите на себя поддержку локальных данных и помогите
стимулировать распространение биткойна. Присоединяйтесь, добавляйте бизнес,
обьединяйтесь."; also remove the extra space in the hyphenated phrase "биткоин-
дружественными" (make it "биткоин-дружественными") wherever that exact string
appears. Search for those exact substrings in src/lib/i18n/locales/ru.json and
update the JSON values accordingly, ensuring punctuation and encoding remain
valid.
- Around line 1-1097: Locale parity check found two discrepancies: add the
missing translation key "dashboard.totalAreas" to ru.json with an appropriate
Russian string (matching the en.json meaning) and remove the extra key
"footer.switchToRussian" from ru.json so the keys match en.json; update the
"dashboard" object to include "totalAreas" and delete "footer.switchToRussian"
to restore parity and avoid runtime fallback/inconsistency issues.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0b5cd45f-63c1-486d-8d15-160e2d73d9ac

📥 Commits

Reviewing files that changed from the base of the PR and between 2b601aa and 4e2e527.

📒 Files selected for processing (3)

• src/components/layout/Footer.svelte
• src/lib/i18n/index.ts
• src/lib/i18n/locales/ru.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

python - <<'PY'
import json
import re
from pathlib import Path

base = Path("src/lib/i18n/locales")
files = ["en.json", "pt-BR.json", "bg.json", "ru.json"]

def flatten(obj, prefix=""):
    out = {}
    if isinstance(obj, dict):
        for k, v in obj.items():
            key = f"{prefix}.{k}" if prefix else k
            out.update(flatten(v, key))
    else:
        out[prefix] = obj
    return out

loaded = {}
for f in files:
    p = base / f
    if p.exists():
        loaded[f] = json.loads(p.read_text(encoding="utf-8"))

if "en.json" not in loaded or "ru.json" not in loaded:
    raise SystemExit("Missing en.json or ru.json")

en = flatten(loaded["en.json"])
for fname, data in loaded.items():
    flat = flatten(data)
    missing = sorted(set(en) - set(flat))
    extra = sorted(set(flat) - set(en))

    print(f"\n== {fname} ==")
    print(f"missing keys vs en: {len(missing)}")
    for k in missing[:30]:
        print(f"  - {k}")

    print(f"extra keys vs en: {len(extra)}")
    for k in extra[:30]:
        print(f"  + {k}")

    mismatches = []
    for k in set(en).intersection(flat):
        if isinstance(en[k], str) and isinstance(flat[k], str):
            en_vars = set(re.findall(r"\{([a-zA-Z0-9_]+)\}", en[k]))
            cur_vars = set(re.findall(r"\{([a-zA-Z0-9_]+)\}", flat[k]))
            if en_vars != cur_vars:
                mismatches.append((k, sorted(en_vars), sorted(cur_vars)))

    print(f"placeholder mismatches vs en: {len(mismatches)}")
    for k, a, b in mismatches[:30]:
        print(f"  * {k}: en={a}, {fname}={b}")
PY

Repository: teambtcmap/btcmap.org

Length of output: 2758

---

Locale parity check reveals issues in ru.json that need correction.

Verification found:

• Missing key: dashboard.totalAreas (exists in en.json but not in ru.json) — could cause runtime fallback issues if referenced
• Extra key: footer.switchToRussian (in ru.json but not in en.json) — inconsistent with en.json structure

While placeholder coverage is correct (0 mismatches), these key discrepancies should be resolved to maintain consistency across locales and prevent potential runtime issues.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/lib/i18n/locales/ru.json` around lines 1 - 1097, Locale parity check
found two discrepancies: add the missing translation key "dashboard.totalAreas"
to ru.json with an appropriate Russian string (matching the en.json meaning) and
remove the extra key "footer.switchToRussian" from ru.json so the keys match
en.json; update the "dashboard" object to include "totalAreas" and delete
"footer.switchToRussian" to restore parity and avoid runtime
fallback/inconsistency issues.

[escapedcat]

@bubelov wanna address these comments? This one and the other one

[coderabbitai]

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

[bubelov]

@escapedcat nah, missing key was added later, it can be added in a follow up direct push (no need to bother anyone with prs if no real code is affected). ".switchToRussian" is probably a no op in ru.json and ъ is used interchangeably with ь unless you're a silver age poet or something

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix user-facing Russian copy typos.

Line 536 has a typo (обьединяйтесь → объединяйтесь), and Line 1053 has an extra space in a hyphenated phrase (биткоин- дружественными).

✏️ Proposed text fix

-		"description": "Возьмите на себя поддержку локальных данных и помогите стимулировать распространение биткойна. Присоединяйтесь, добавляйте бизнес, обьединяйтесь.",
+		"description": "Возьмите на себя поддержку локальных данных и помогите стимулировать распространение биткойна. Присоединяйтесь, добавляйте бизнес, объединяйтесь.",
...
-		"description": "BTC Map - бесплатный проект с открытым исходным кодом, поддерживаемый волонтёрами-биткоинерами и биткоин- дружественными торговцами по всему миру.",
+		"description": "BTC Map - бесплатный проект с открытым исходным кодом, поддерживаемый волонтёрами-биткоинерами и биткоин-дружественными торговцами по всему миру.",

Also applies to: 1053-1053

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/lib/i18n/locales/ru.json` at line 536, Replace the misspelled and spacing
errors in ru.json: change "обьединяйтесь" to "объединяйтесь" in the value for
the "description" entry that currently contains "Возьмите на себя поддержку
локальных данных и помогите стимулировать распространение биткойна.
Присоединяйтесь, добавляйте бизнес, обьединяйтесь."; also remove the extra space
in the hyphenated phrase "биткоин- дружественными" (make it
"биткоин-дружественными") wherever that exact string appears. Search for those
exact substrings in src/lib/i18n/locales/ru.json and update the JSON values
accordingly, ensuring punctuation and encoding remain valid.

[bubelov]

Yeah language switch won't scale for sure, we'll need a drop down. I didn't test it though because it did auto detect the locale. It's useful for debugging language-related design issues though

[dadofsambonzuki]

I think we're in drop down territory now.

[escapedcat]

I think we're in drop down territory now.

Alright, let it break. I'll do a follow up to come up with a good solution.