I built a small browser-local checker for a failure mode I kept seeing in game
localization handoffs: a file can look complete in a spreadsheet but still
break at runtime when a placeholder changes or disappears.
StringSentry reads existing Godot translation CSV and gettext PO/POT files
locally in the browser. It checks for:
- missing or empty translations;
- duplicate keys;
- placeholder mismatches such as %d becoming %s or {name} disappearing;
- whitespace or line-break issues; and
- strings likely to overflow a UI field.
It does not translate content, automatically edit files, or guarantee a build
is free of all localization issues. It is a structural pre-build check.
I included a deliberately broken Godot CSV and PO sample, plus the expected
report, here:
There is also a free 50-key demo for checking your own files locally (no
account and no file upload):
I would especially value feedback from anyone shipping multiple locales in
Godot: which structural issue costs you the most time before a build?