Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 4 Nov 2026. What's built · Install 0.2.0
jadpo
ReferenceLanguages and translations

Configuration

Languages and translations

The languages your app speaks, and how its text is translated and checked.

Locales

A locale is a language as a place writes it, such as British English (Locale.en_gb) or the French of France (Locale.fr_fr).

Translations as messages

Text your server writes for people, such as emails, generated pages and a failure's text for client apps, is translated in Jadpo itself.

Enums with wording

An enum has no label for people of its own (Enums).

Failures for client apps

A client app can show a failure to its user in the user's language.

Packages' text in an app

To show a package's or Jadpo's message in a locale, Jadpo looks first in your app's root wording for that locale, then in the owner's own.

Tooling for translations

The jadpo translations commands list what is missing, keep the record of what each translation was made from, and exchange wording with translation services.

Exchanging translations with a service

Most teams send their wording to a translation service, such as Crowdin, Lokalise or any that reads XLIFF or JSON.

Details

The exact rules, for when you hit an edge case.

What the compiler checks of translations

jadpo check checks every language file against the messages, enums, emails and failures it words.

Markdown for agents: /docs/languages-and-translations.md.Built from Jadpo main at 6cc3cb4.