Languages
Path: /admin-settings → Languages tab
SUPERUSERs manage the TelWeb language catalogue from this page. Delphi v0.9.14 ships English and German bundles by default and can serve additional languages when operators add entries and translation overrides.
What a language controls
Each language entry controls whether the locale is available in TelWeb and which override bundle, if any, should replace or supplement the shipped translation files.
| Field | Description |
|---|---|
| Locale | BCP 47-style locale code, for example en or de. |
| Name | Display name shown in the UI. |
| Enabled | Whether users can select the language. |
| Message overrides | Optional JSON object for deployment-specific labels or corrections. |
TelWeb resolves the initial locale from the user's preference, then the browser Accept-Language header, then English as the fallback. Users can store their preferred language on their profile.
Translation overrides
Use overrides for deployment wording, not for secrets or customer data. Overrides are cached through Redis and ETags so users pick up changes quickly without a full service redeploy.
Malformed override JSON can make a locale unusable. Validate the object and keep keys aligned with the shipped English bundle.
Operational notes
- Run database migrations before enabling v0.9.14 so the
Languagetable, seed row, andUser.languagereference exist. - Keep at least one enabled fallback language. English is seeded by default.
- If users report stale labels after an override, save the language again to bump the cache revision, then have the user refresh TelWeb.
See also
- Platform settings — platform-wide defaults and resilience settings.
- Access logs — audit authentication and role-management events.