Everything Dialecto does, in the order you'll meet it.
Dialecto works on the translation files in your repository, helps you and your model get them right, and sends every change back as a pull request your team reviews. Four things set it apart, and you'll meet each of them again on the way through.
Four things that set Dialecto apart
Translation files only
Dialecto reads the translation files at the paths you confirm, and never your source, configuration or secrets. In Security mode, your own pipeline sends those files, and Dialecto holds no access to your repository.
Shown in station 2, ScanCurated context
Bring the model you trust, local or hosted, or your own coding agent over MCP. Dialecto gives it the domain, where the string appears, your brand voice, your audiences and your glossary, and nothing it drafts reaches your repository until a person merges the pull request.
Shown in station 3, DraftBatch key renames
Rename one key or a whole family of them, such as every
Shown in station 4, Editbasket.*key tocart.*, in every language at once, and it arrives as one reviewed pull request. This is what makes organizing by domain practical, rather than a nice idea.Call-site rewrites
When a key is renamed or the English text of a gettext string changes, every place your code uses it is rewritten in the same pull request. Dialecto works out each change, a public action in your repository applies it, and anything it can't rewrite safely is listed for you, never guessed.
Shown in station 6, Ship
Integrate
The string hereen.jsonin the repository, untouched
Installation
Install the GitHub App, or let your own workflow send the files in Security mode. In-place editing is an add-on that runs only while you develop, and it leaves nothing in your production build. Your translations stay ordinary JSON and gettext files, so if you ever leave, you take everything with you and there's nothing to migrate.
Scan
The string hereYour basket is emptyfound at a confirmed path
Repository access
Dialecto reads the translation files under the paths you confirm, and that is all it opens. With the GitHub App, it also looks at file names, never their contents, against a published list of catalog patterns, so it can tell you about translation files you haven't added yet. Your configuration, secrets and tests stay in your repository. Code snippets come only from your own pipeline, when you choose to send them.
With the GitHub App, our own code holds that limit, because GitHub's permission covers the whole repository. In Security mode, Dialecto holds no access to your repository at all. Your workflow sends the files it names, opens Dialecto's pull requests with your repository's own token, and runs the translation check.
- What comes back is only ever a pull request, and it waits for your team. Dialecto never merges anything.
- Everything that runs next to your code, the add-ons and the rewrite action, is public on GitHub under the MIT licence, so you can read every line.
- Dialecto runs in the EU, and a local model and self-hosting are there for when you want every piece in your own hands.
Promise 1: Translation files only
Draft
The string hereVotre panier est videdrafted, waiting for review
Machine translation
Ask your model for a draft on any string, or let it fill new strings on every scan. Either way it works from the domain, your brand voice, the audience you're writing for, your glossary and your translation memory. Filled drafts wait for a person's review unless you decide otherwise, and nothing reaches your repository until someone merges the pull request.
Context and personasPromise 2: Curated context
Edit
The string hereYour cart is emptyrenamed to cart.empty
Ways to edit
The editor is built for translating: move through a domain, see where each string is used, and work in bulk when bulk is what's needed. While you develop, you can also open your running Phoenix or Astro app, click any text, and edit it in a sidebar beside the page, plurals and all. Your coding agent can do the same over MCP.
In-context editing
Batch key renames
Rename a key or a whole family, every basket.* key to cart.*, in every language at once. It arrives as one reviewed pull request, with your code's call sites rewritten in it.
Promise 3: Batch key renames
Key family rename
The editor, on another projectpriv/acme/shop, a Phoenix app in gettext
Editor demo
Demo This is a demonstration. Nothing you type is saved or sent anywhere.
Choose a string to translate. “Apply a coupon” and the item count are waiting for French.
This is a still of the editor. With JavaScript on, you can edit these strings here.
acme/shop checkout French gettext
- 5Scanned
- 2Untranslated
- 0Edited
- 0Submitted
- 0In review
- 0Approved
No changes stagedEdits you make collect here, ready to ship as one PR.
The diff for checkout.po
Each string you saved changes only its own lines. The comments and neighbours around them stay as they were.
Pull request
Localize checkout (fr)
1 file changed +1 −1priv/gettext/fr/LC_MESSAGES/checkout.po
Dialecto/translationsPassing
This card is drawn for the demo. No pull request was opened and nothing was sent.
Validate
The string herecart.emptychecked, passing
Validation
Every change is checked as you save it: placeholders, plural forms, glossary terms and stale bases, with a note under the string when something's off. Then a person reviews it, and the merge gate fails any pull request that would leave new strings untranslated. The advisory quality check scores what a pull request adds; whether it ever blocks is your call.
The merge gateEditor and pull request checks
Ship
The string herePull request #312shipped, with cart.astro:12 rewritten
Changes as pull requests
Everything you approve leaves as one pull request with one signed commit: one line of diff per change, with comments and order untouched, and every place your code uses a renamed key rewritten in the same pull request. Dialecto works out each rewrite, a public action in your repository applies it, and anything it can't rewrite safely is listed for you to check.
Call-site rewrite docsPromise 4: Call-site rewrites
The rename's pull request
Comparison
A word about the neighbours. Translation “platforms” own your strings and regenerate your files. The AI-native command-line tools regenerate them too, only faster. We ran their actual published file loaders over valid gettext files, with no translation involved, and keptthe receipts.
| Dimension | Translation “platforms” | AI-native CLIs tested | Dialecto |
|---|---|---|---|
| Repository access | Your strings, uploaded into their store | Your repo, with write access | Only your translation files, and source lines only if your pipeline sends them |
| Translation storage | Their database | Your repo, regenerated on every run | Your repo, untouched except for the changes you made |
| Diff size | A regenerated file | A rewritten file, even when nothing was translated | One line of diff per change, with comments and order kept |
| Translation structure | Flat lists, sometimes tagged | Whatever the file had | By domain, as the way you work |
| Validation | Varies | Autofill races ahead | The merge gate, validation checks and a human review |
| Call-site rewrites | Your code is outside their reach | No | Yes, the call sites follow in the same pull request |
Each neighbour has a full comparison: Dialecto vs Tolgee,Dialecto vs Lingo.dev,Dialecto vs Weblateand Dialecto vs Crowdin.
See it on your strings.
Create your account, connect a repository, and your first change arrives as a pull request your team reviews.