From 5d1c43bfaf28e192b039603669790378bcf827ae Mon Sep 17 00:00:00 2001 From: German Khokhlov Date: Mon, 12 Oct 2026 14:08:38 +0400 Subject: [PATCH] docs(i18n): clarify where a placeholder may go Co-Authored-By: Claude Opus 5.5 --- docs/TRANSLATORS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/TRANSLATORS.md b/docs/TRANSLATORS.md index 567309aa1..ffef75735 100644 --- a/docs/TRANSLATORS.md +++ b/docs/TRANSLATORS.md @@ -50,7 +50,7 @@ Edit `src/i18n/locales/.json` and run `npm run i18n`. To see your change, ## Rules -- Keep every `{placeholder}` exactly as in the English; you may move it. +- Keep every `{placeholder}` name exactly as in the English: do not rename, drop or add one. Its position inside the sentence follows the grammar of your language, e.g. `"{accepted} of {raw} records accepted"` → `"принято записей: {accepted} из {raw}"`. - UPPERCASE English stays UPPERCASE. Short labels, chips and HUD readouts should stay short; prefer an abbreviation over a wrapped line. - Keep the separators `·`, `—`, `→`, `↗`, `…`. - Leave product, provider and data names in their original form: Google Maps, Cesium ion, OpenAI, ChatGPT, NASA FIRMS, USGS, OpenSky, ADS-B, AIS, CCTV, HUD, TomTom, OpenStreetMap, Mapillary, and keyboard keys (Space, Esc, H, 1–9).