Translations
Translation status, language settings, and how to contribute
Choosing a language
Zipline uses your browser's preferred language by default. You can change it using the language button in the dashboard header or on the login and public pages. Your choice is saved in your browser.
If a language or translation is unavailable, Zipline falls back to English. API errors and custom text set by an administrator are not translated.
Contributing
Zipline uses Weblate for translation contributions. You can help translate missing text or improve existing translations directly in your browser:
- Open Zipline's Weblate.
- Sign in with your GitHub account.
- Choose your language and start translating.
Keep placeholders such as {{name}} and tags such as <anchor>...</anchor> unchanged. You can move them within the sentence and translate the text between tags.
Working with translation files
For development or local changes, translation files are in src/lib/i18n/locales, organized by language and section of the interface:
src/lib/i18n/locales/en/auth.json
src/lib/i18n/locales/fr/auth.jsonFor example, auth.json contains login and registration text, while common.json contains shared labels.
Editing a translation
Edit the file in your language's directory, using the matching English file in locales/en/ as a reference. Keep the same JSON keys and structure, and translate the values. Missing keys can be added as you translate them; partial translations are supported.
Keep placeholders such as {{name}} and tags such as <anchor>...</anchor> unchanged. You can move them within the sentence and translate the text between tags.
Do not leave empty values. Omit untranslated keys so Zipline can use the English text instead.
Plurals
Plural keys use suffixes such as _one, _few, _many, and _other. Include every form your language requires; the forms may differ from English.
Use the English _other entry as a reference for additional forms. {{count}} inserts the number into the sentence.
Adding a language
To add a language:
- Create
src/lib/i18n/locales/<code>/with translated JSON files, using the English filenames and structure. - In
src/lib/i18n/languages.ts, add the language code and its native name toLANGUAGE_NAMES.LANGUAGESis derived from this map. - If the Day.js locale differs from the language code, add a mapping to
DAYJS_OVERRIDESin the same file. - Import the corresponding Day.js locale in
src/lib/i18n/index.ts.
Language detection currently uses base codes such as fr or pt. Separate regional variants would also need changes to the detection logic.
Testing changes locally
Follow the development setup, then run:
pnpm test
pnpm validateThe tests check keys, placeholders, tags, empty values, and plural forms. Select your language in Zipline and check the affected pages for text that gets cut off or wraps awkwardly.
If you edit translation files directly, open a pull request against trunk with a short description of the language and changes. You can also report a translation issue with the affected page and suggested wording.