gospel.tableTitles.<tab id> and gospel.columns.<English title>, requested by gospel-plugin (KEY-REQUEST-gospel-tables.md): under ar the tabs were Arabic and every heading and header above the table was English. Standards stay as they are (ISO 639-3, ISO3, JSON, CSV, ROP1, SUN; a bare "ISO" header gets no key and keeps its English). JESUS Film uses each locale's existing title; "Heart language" uses each locale's own-language wording. Reviewed against the data by gospel-plugin before insertion, which corrected five wrong-sense readings: ALIGNED (conditions met, not layout), Band (a coverage level), Basis (the level the answer came from), Code unlookupable (no source indexes it, not an invalid code), Scope (extent). Machine-drafted; not native-reviewed. |
||
|---|---|---|
| .. | ||
| locales | ||
| index.js | ||
| 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;
arrenders right-to-left (RTL_LOCALES). - Add a language by copying
locales/en/tolocales/<code>/— never by editingindex.js(except adding the code toSUPPORTED_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.