Built for Phoenix first.
We built Dialecto's gettext support for Phoenix first, and it's the experience we've polished most. If you localize a Phoenix app, this is for you.
Native gettext
Dialecto is gettext-native — no export step, no format conversion, no "sync" that rewrites your files. Your gettext domains map straight onto Dialecto's domain-driven editing, and the validation matches what your app actually runs: %{} placeholder parity and plural-form checks that agree with Elixir'sGettext runtime, so a translation that passes here works there.
msgid "%{count} file"msgid_plural "%{count} files"msgstr[0] "%{count} fichier"msgstr[1] "%{count} fichiers"
- Placeholders match
- Plural forms match Gettext
Quickstart
- Connect your repo. Dialecto takes a surgical slice: your
.poand.potfiles, read by the GitHub App at the paths you confirm or sent by your own CI, plus the few source lines around each string if your CI sends them. Nothing else leaves. - Scan. Your catalog appears organized by domain, with every string in its context.
- Edit by domain. Move quickly through a domain, work in bulk when you need to, and review as you go.
- Ship a clean pull request. It goes into whichever branch you're working on, with one line of diff per change.
Elixir features
gettext domains
Phoenix apps split translations across gettext domains — default, errors, emails, whatever you've grown. Dialecto reads that structure and makes it the editing model: browse by domain, translate a domain at a time, and rename keys in batches when your app outgrows its early names.
Call-site context
When your pipeline sends the few source lines around each string, you see them right beside it, so translators know what a string is for and nobody translates blind.
Call-site rewrites
Renaming a msgid rewrites the gettext() call-sites in your source — computed by Dialecto, applied by a CI action in your repo, shipped in the same pull request. A rename is finally one operation, not a grep-and-pray.
Merge gate
The completeness check fails a pull request on strings it newly leaves untranslated — as a required check, if you want teeth. Configured in your repo's Dialecto settings, with a link that takes the author straight to the strings that need them.
Curated context
Machine-translation suggestions are grounded in your brand voice, your audience personas, your glossary, and the domain each string lives in — whether they come from a local model, from DeepL or Gemini if your organization's owner chooses one, or from your own coding agent over MCP. Dialecto is model-agnostic on purpose: we don't claim "best translation," we make sure the model sees exactly the right context and that a human signs off before anything merges.