319064a11b
Every map translated its own chrome but left the basemap's country, city and street names in the style default (English on Mapbox, Latin + native on OpenFreeMap) in all eleven locales. A reader in Arabic saw an Arabic legend over an English map. library/maps/localize-labels.js uses each engine's supported mechanism: - Mapbox: map.setLanguage(lang). It also localizes the Standard style's IMPORTED basemap, which a layer rewrite cannot reach. - MapLibre: basemap symbol layers point at ['coalesce', name:<lang>, name:latin, name]. English restores each layer's original expression, re-captured on every style load so a theme switch never restores the previous style's labels. Only layers whose text-field reads an OSM name field are touched. A plugin's own label layers (zone titles, group names) are never rewritten. useMapInstance applies it on every style.load and when the reader's language changes (ProfileLoader's 'lang', else profile-config locale, else ?lang / <html lang>). The Prayer Walk Planner drops its private copy for the shared one. Measured on the Prayer Progress map, ar/zh/ru/hi: - Mapbox getLanguage() == locale in all four. - MapLibre: 13/14 symbol layers localized, and the plugin's own label layer untouched. Read in the Arabic screenshots: القاهرة, الإسكندرية, السويس, الأردن on both engines. check:gallery-embed (+ :maplibre) and check:prayer-walk-planner pass. The shared change reaches all 11 bundles that compile initializeMap, and all are rebuilt here. check:shared-reached marker basemap-labels-localized: 10/10 consumers. |
||
|---|---|---|
| .. | ||
| api | ||
| colors | ||
| components | ||
| composables | ||
| constants | ||
| data | ||
| i18n | ||
| layouts | ||
| maps | ||
| packet | ||
| scripts | ||
| stores | ||
| styles | ||
| utils | ||
| index.js | ||
| ProfileLoader.vue | ||
| README.md | ||
library/ (@map) — the shared map template
The other half of the architecture (see ../plugin-designs/README.md):
every map in plugin-designs/<your-map>/ composes the reusable, parameterized pieces that live here.
Fix something here and every map benefits on the next build; break something here and every map
breaks — read components/WARNING.md before touching shared pieces.
| Folder | What lives there |
|---|---|
ProfileLoader.vue |
The root of every bundle: parses profile-config, loads the profile, provides the stores + config |
components/ |
Shared UI — map, legends, controls, popup (PeopleGroupDetail), tables, charts, hints (README) |
composables/ |
Shared logic — map engine (useMapInstance), provider switch, shadow-DOM styles, theming |
stores/ |
Per-instance Pinia stores (ui / map / data) — provided by ProfileLoader, injected by children |
api/ |
Data-source registry (sources.json) + fetch layer — the JAMstack runtime wiring |
colors/ |
Color sets maps opt into via profile-config.colorSet |
i18n/ |
The shared string catalogs (all maps speak the same languages) |
data/ |
Small shared datasets baked at build time (big served data lives in ../data/) |
constants/ |
Shared constants |
scripts/ |
Maintainer pipelines (posters, research) — not part of any bundle |
The rule of thumb (same as WARNING.md): custom code in your app-profile, reusable code here — and things only move from the first to the second once they've earned it.