LocalePilot opens the Localizable.xcstrings files of your iOS and macOS apps, shows what is missing in each language, checks format specifiers, and writes the catalog back in Xcode's style, touching only what you changed.
new state or empty. LocalePilot never writes an empty value: clearing a translation removes the localization, like Xcode does.key › plural › one.needs_review…); an edited value becomes translated.Writing back an unchanged catalog produces a byte-identical file; an edit only changes its own lines. Your code review stays readable, and the export goes through the same review, disk merge and backup as every other format.
QA recognizes %@, %1$@, %d, %ld, %lld, %.2f, %u, %i and %s; %% is treated as text. A missing or extra specifier in a translation is flagged before export.
shouldTranslate: false and keys using substitutions (%#@count@) are preserved untouched but not shown: they stay managed in Xcode.one (Japanese, for example) may report a gap..strings files are supported too, in UTF-8.No, it complements it: Xcode extracts strings from your code, LocalePilot is where you check, translate and review them. Both read and write the same .xcstrings file.
No. A catalog written back without changes is byte-identical; an edit only changes its own lines, in Xcode's style.
Yes, plurals and device variations are editable. Substitutions (%#@count@) are preserved but still edited in Xcode.
LocalePilot is being finalized. Leave your email to hear about the launch and the price of the Pro plan.