EN English IT Italiano DE Deutsch ES Español FR Français PT Português (BR) RO Română HU Magyar PL Polski RU Русский TR Türkçe JA 日本語 ZH 简体中文 ZH 繁體中文 UR اردو

One catalogue, fifteen files

Every string lives in a single catalogue from which all fifteen language files are generated. Keeping fifteen files aligned by hand means finding out about a missing key only when the interface shows the key itself instead of the text.

The generator refuses to build when:

  • a language is missing a key
  • a format placeholder does not match the base language, a lost %@ breaks formatting in that language alone, which is exactly the sort of bug that reaches release

Sentences, not fragments

Messages are whole sentences with a single placeholder. Building "Starting" plus "of" plus a name works in English and falls apart nearly everywhere else: German puts the verb at the end, Turkish uses suffixes. So the app stores "Starting %@…" as one string, and the translator rearranges it freely.

Urdu reads the other way

macOS mirrors interfaces built with Auto Layout on its own, and the window is built that way. The rows that draw themselves, service rows, project rows, buttons, flip explicitly instead, so indicators, ports and labels all land on the correct side rather than staying stubbornly left to right.

Where translations came from

Wording is shared with the dashboard wherever an equivalent already existed, so the same idea is not called two different things in the two products. The guides that came with the servers remain in English, and the interface says so with a badge rather than pretending they were translated.

In your language, from the first launch

It follows the system setting; nothing to configure.

v9.26.17Updated November 2026Free · app and dashboard GPL