History

Doxa Maps 7cd40a6e8e Pin wording: shared points and key-city clusters claim only what is certain A pin's position is generalised, so it does not tell a reader the locality or where a group is centred. - pins.sharedPoint in all 11 locales and ApproxPinNote.vue's fallback: the groups sharing the point are named and counted ("{n} groups share this dot"); the locality claim is gone. - keyCities map.note, map.sheetNote and list.caveat.row in all 11 locales: a cluster is of people-group pins, not centroids, and each pin marks a people group, not a town. - The key-cities and languages-per-city caveats in build-tabulator-tables.mjs and in every committed copy of those two tables (only that one field changes), derive-city-candidates.mjs's caveat, and the matching comments in key-cities, name-clusters and the poster generator. - check-approx-pin-note's pass line no longer calls pins localities. Two UI-strings baseline entries whose strings no longer exist in their files are dropped.		2026-10-02 09:21:54 +00:00
..
locales	Pin wording: shared points and key-city clusters claim only what is certain	2026-10-02 09:21:54 +00:00
CATALOGUES.md	Speak the reader's language on the UPG-100 map, its wall and the print HUD	2026-09-29 08:33:43 +00:00
index.js	Comments name no internal hosts or teams; the A9 leaf-hint comment every page carries is neutral	2026-09-30 22:36:47 +00:00
keyedError.js	Speak the reader's language on the UPG-100 map, its wall and the print HUD	2026-09-29 08:33:43 +00:00
README.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
useRegionsI18n.js	A country map you can drop on one page, without the dashboard around it	2026-09-29 01:38:07 +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.