Translate django.po, then check every line
makemessages writes locale/en/LC_MESSAGES/django.po with %(name)s variables and plural entries. Translate %(name)s or drop it, and the template raises an error or shows nothing. KAERIS fills each msgstr and leaves the variables as Django expects.
%(name)s stays exactly where it was
Each msgid gets its msgstr; the header gets the target's Language and plural rule.
msgid "Welcome back, %(name)s!"
msgstr ""
msgid "Save changes"
msgstr ""
msgid "Welcome back, %(name)s!" msgstr "Willkommen zurück, %(name)s!" msgid "Save changes" msgstr "Änderungen speichern"
What KAERIS does with it
Plural forms per language
ngettextentries get as manymsgstrforms as the target needs: three for Russian, one for Chinese.Variables checked without AI
After translation a plain counting check compares every variable and tag with the original. A line that lost one is marked and shown on top.
Each line translated back
A different model, Gemini 2.5 Flash-Lite, translates every line back into your language, and DeepSeek V3.2 on US hosts (DeepInfra, DigitalOcean, Google) judges whether the meaning changed. You read what each line now says.
Questions
What do I run afterwards?
Put the file into locale/<lang>/LC_MESSAGES/ and run compilemessages as usual.
Is msgctxt kept?
Yes. Entries with the same text and a different context stay separate.
Is it free?
Yes, without an account: 10,000 characters per file and up to 8 languages per run. A free API key raises the file limit to 50,000 characters. Lifetime is $79 once, on your own OpenRouter key; monthly plans start at $19. Pricing
Can I run it from the terminal or in CI?
Yes. pip install kaeris, then kaeris translate with your file and --langs de,ja. A GitHub Action opens a pull request when new keys land. Docs