History

Doxa Maps 298c71c83b The packet-variant control is translated: three button keys in the other ten locales The Prayer List caret landed its labels in English only, so check:i18n-parity failed.		2026-09-28 16:49:31 +00:00
..
locales	The packet-variant control is translated: three button keys in the other ten locales	2026-09-28 16:49:31 +00:00
index.js	i18n: a page the plugin owns gets <html lang> = the locale, not only dir=rtl	2026-09-28 08:31:18 +00:00
README.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00

README.md

library/i18n/ — the map's translations

One of the three customization seams (colors/, api/, i18n/). This one owns every user-facing string. Translations are one folder per locale, one JSON file per area, inlined at build time into a Vue I18n instance (one per <doxa-map>, so embeds don't bleed state).

  i18n/
  ┌───────────────────────────────┐
  │ index.js   ← engine, don't edit │
  │ locales/                        │
  │   en/  buttons.json legend.json …│  ← en is the source of truth + fallback
  │   es/ ar/ zh/ …  (same keys)     │  ← 11 shipped locales, drop in your own
  └───────────────────────────────┘
     filename → namespace:  buttons.json → $t('buttons.prayForThem')

11 shipped locales; ar renders right-to-left (RTL_LOCALES).
Add a language by copying locales/en/ to locales/<code>/ — never by editing index.js (except adding the code to SUPPORTED_LOCALES).
Missing keys fall back to English silently.

Adding or overriding a locale? The full contract (locale matrix, checklist, integration) is in ../../documentation/architecture/i18n.md.