Translate

Translate Localizable.strings and check every specifier

A %d where English has %lld builds without a warning and can print the wrong number for large values. Below, one command finds that and a missing key, another translates the file again.

The example project

A small iOS .strings project: the English source and a German file that fell behind. The commands below ran on exactly these files.

Sourceen.lproj/Localizable.strings
/* Greeting on the home screen */
"greeting" = "Hi, %@!";
"files_synced" = "%lld files synced";
"upload_progress" = "Uploading %1$@ of %2$@";
"sign_out" = "Sign out";
"storage_full" = "Your storage is full.";
German, beforede.lproj/Localizable.strings
/* Greeting on the home screen */
"greeting" = "Hallo, %@!";
"files_synced" = "%d Dateien synchronisiert";
"upload_progress" = "Lade %1$@ von %2$@ hoch";
"sign_out" = "Abmelden";

1. Find what is missing

kaeris check compares each translation with the source file. It runs offline with no key or account, and exits with code 1 when it finds a problem, so a CI job can stop on it.

Terminalexit code 1
$ npx kaeris check --source en.lproj/Localizable.strings --langs de
! Could not detect a known locale-file layout for 'en.lproj/Localizable.strings' (source_lang='en') — nesting output by language instead
✗ de: 1 missing key(s): storage_full
✗ de: 1 placeholder mismatch(es):
    files_synced: missing -, added ['%d']
✗ de: 2 translation fault(s):
    files_synced: lost placeholder %lld
    files_synced: invented placeholder %d (not in source)
✗ 1 missing key, 1 placeholder mismatch, 2 translation faults

2. Translate the file

--only-new covers JSON and ARB in this release. For .strings the CLI says so and translates the whole file again, which also replaces the broken lines. The command is in the Python package: pip install kaeris.

Terminalexit code 0
$ kaeris translate en.lproj/Localizable.strings --langs de --only-new
→ no key: free demo limits 10,000 chars per file, 8 languages per run, get a key: kaeris.dev/developer
! --only-new supports JSON/ARB only (zero-dependency CLI); translating the whole .strings file instead
→ Translating Localizable.strings → de
! Could not detect a known locale-file layout for 'en.lproj/Localizable.strings' (source_lang='en') — nesting output by language instead
✓ Wrote 1 file(s) to ./en.lproj/de
en.lproj/de/Localizable.strings
✓ Translation QA: no placeholder loss, no overflow risks
→ Run: openai/gpt-6-luna · Free · 1/1 languages · 5 strings · 4.6s
     75 charged

This release writes the file to en.lproj/de/ instead of de.lproj/, as the output shows. Until a fix ships, move it:

Terminalexit code 0
$ mv en.lproj/de/Localizable.strings de.lproj/Localizable.strings
German, afterde.lproj/Localizable.strings
/* de */
"greeting" = "Hallo, %@!";
"files_synced" = "%lld Dateien synchronisiert";
"upload_progress" = "%1$@ von %2$@ werden hochgeladen";
"sign_out" = "Abmelden";
"storage_full" = "Dein Speicher ist voll.";

3. Check again

Exit code 0: every key is there and every placeholder matches the source.

Terminalexit code 0
$ npx kaeris check --source en.lproj/Localizable.strings --langs de
! Could not detect a known locale-file layout for 'en.lproj/Localizable.strings' (source_lang='en') — nesting output by language instead
✓ de: complete & placeholder-safe
✓ all locales complete & placeholder-safe

Run on 2 November 2026 on the free tier, without a key: npx kaeris 0.2.42 for the check, kaeris 0.2.42 from PyPI for the translation. Output as printed, except that progress lines and the local folder path are left out.

What kaeris check catches in iOS .strings

What it costs

Questions

What about String Catalogs (.xcstrings)?

KAERIS translates them: .xcstrings. In 0.2.43 the check finds strings missing from a catalog, compares the specifiers inside plural variations and reports a plural without the forms a language needs.

Are my comments kept?

Not in a .strings file, 0.2.43 included: the translated file starts with /* de */ and the comments for translators are gone, as in the run above. The English file is not touched. A String Catalog keeps them: translate updates it in place and leaves comments, extraction states and shouldTranslate: false as they were.

Can it run in CI?

Yes. npx kaeris check exits with code 1 when it finds a problem. Recipes: GitHub Actions, GitLab CI, pre-commit.

Keep going

Check reference · CLI reference · Free check in the browser · Translate in the browser

Other stacks: react-i18next · next-intl · vue-i18n · Flutter · Android