Internationalization

Kener internationalization has two parts:

1. Localization (translated UI text)
2. Timezone handling (how date/time values are displayed)

Use this page to configure both from the admin UI and keep translations complete.

Quick setup

1. Open Manage → Internationalization.
2. In Languages:
   • select available locales,
   • pick a default locale,
   • click Save Languages.
3. In Timezone Settings:
   • enable or disable Allow users to switch timezones,
   • click Save Timezone.

Localization

How it works

• Locale files are JSON files in src/lib/locales/.
• Each locale file stores translations under mappings.
• Admin settings store:
  • selected locales,
  • default locale.

Only selected locales are exposed to users in the language selector.

Add or update translations

1. Edit the locale file(s) in src/lib/locales/.
2. Add missing keys under mappings.
3. Run translation checks.

Example locale shape:

{
    "name": "English",
    "mappings": {
        "Status": "Status",
        "All Systems Operational": "All Systems Operational"
    }
}

Validate localization

Run these from project root:

node scripts/check-translations.js
node scripts/sort-translations.js

• check-translations reports missing/unused keys.
• sort-translations normalizes key order in locale files.

Timezone handling

How it works

• Kener stores timestamps in UTC (Unix seconds).
• On the client, Kener detects browser timezone automatically.
• If timezone switching is enabled, users can change timezone manually from the public page controls.

Admin toggle

In Manage → Internationalization, the timezone switch controls whether manual timezone selection is shown to users:

• ON: users can switch timezones.
• OFF: users see auto-detected timezone behavior only.

Server timezone variable

Server-side timezone behavior is also affected by TZ.

For setup details, see: /docs/v4/setup/environment-variables#timezone

Stored settings reference

Kener saves internationalization settings in site data with keys like:

Verification checklist

• Language selector shows only selected locales.
• Default language is used for first-time visits.
• translation-report.json has no unexpected missing keys.
• Time values render correctly for your locale/timezone.
• Timezone selector visibility matches your tzToggle setting.

Troubleshooting

• Missing translation keys in report

  • Add keys to all required locale files under mappings.
  • Re-run node scripts/check-translations.js.

• Language not appearing in selector

  • Make sure it is selected in Manage → Internationalization.
  • Save language settings.

• Timezone selector not visible

  • Enable Allow users to switch timezones and save.

• Unexpected server-side time behavior

  • Verify TZ is set as documented in /docs/v4/setup/environment-variables#timezone.