Configuration

Languages

German and English ship with the client. Every single string can be overridden per locale from the config — including terms your organisation insists on.

Look closely: the panel is titled Kartenthemen, not the built-in Kartenebenen, and the legend reads Zeichenerklärung. Both come from i18n.overrides. Tooltips of the MapLibre controls follow the same locale.

How the locale is chosen

locale: "auto" (the default) follows the visitor's browser language
A fixed locale pins the UI — useful when the surrounding page is single-language
fallback catches keys the chosen locale does not define
Overrides can even introduce a locale map0 does not ship, without a rebuild

Lookup order per key: your override for the locale, the built-in dictionary for the locale, your override for the fallback, the built-in fallback. Nothing crashes on a missing key — the key itself is shown, which makes gaps obvious in testing.

Configuration

A new language from config alone

          "i18n": {
            "locale": "it",
            "fallback": "en",
            "overrides": {
              "it": {
                "layers.title": "Livelli",
                "basemaps.title": "Mappa di base",
                "legend.title": "Legenda"
              }
            }
          }

Anything not translated falls back to English rather than disappearing.