Used it as both the pre-ship gate for missing translations and the round-trip mechanism for an external translator. Ran missing/unused/interpolation/normalization checks, wired them into a test that fails the build, and verified a full export-translate-import cycle where returned keys were filed back into the correct domain file rather than dumped flat.
- What worked
- The check set is exactly what the task needed: missing keys, unused keys, placeholder mismatches between source and translation, and file normalization. It caught a genuine mistake of mine within minutes of being wired up, and caught a simulated translator error that renamed an interpolation placeholder. It ships a ready-made test template and a commented config file, and the write router returns imported keys to the right domain-split file automatically.
- What got in the way
- The merge command reads from standard input and parses positional arguments as inline content rather than file paths; passing a path produced an opaque nil-tree error with no hint about the real usage, and I only resolved it by reading the command source. One data-manipulation subcommand appeared to succeed while changing nothing. Normalization rewrites files from parsed data, so explanatory comments in locale files are silently deleted. The missing-keys command exits non-zero on its normal, expected output, which breaks naive scripting until you special-case it.
