db3ef22481
The tab label in both shells (doxa-maps-spa, posterverse) x11 in each language's own grammar (de 'UPG100-Poster', es 'Carteles UPG100', zh 'UPG100 海报', …), upgMap displayName and wallHeading x11, the three meta labels, the nav item and the dev title; the spa's default tab label, the posterverse description, the UPG-100 legend's count column and the poster-sections noun. Values only: ids, keys, paths and file names stay. |
||
|---|---|---|
| .. | ||
| ar | ||
| de | ||
| en | ||
| es | ||
| fr | ||
| hi | ||
| it | ||
| pt | ||
| ro | ||
| ru | ||
| zh | ||
| README.md | ||
Locale catalogues
One folder per locale, one JSON file per top-level area. SUPPORTED_LOCALES in
library/i18n/index.js is the list the runtime will actually try to resolve; the folders
here are what happens to exist on disk. A missing area file is fine — those namespaces
resolve through fallbackLocale: 'en'.
Nothing in these files is a comment. Every string ships to every reader of that locale,
so notes about the catalogue belong here, not in a _note key. An English _note inside
ar/gospel.json was downloaded by every Arabic reader and — because it was text present in
ar and absent from en — it also satisfied a gate probing for "does this bundle contain
Arabic translations?", hiding the fact that every Arabic character had been stripped. A
value that no reader is meant to see is a value no check should be able to count.
gospel.json holds SHORT UI LABELS ONLY
The explanatory prose on the gospel-resources surfaces stays in English on purpose and is
not in this area. It carries doctrinal and statistical precision — which pools were
searched, what "nothing found" does and does not claim, why Open Bible Stories is not
Scripture — and a mistranslated caveat there would read as authoritative. gospel.prose.english
is the one translated line that says so.
When a human-reviewed translation of that prose exists, it gets its own area file and that line comes out.