Release v0.22.0
Your catalogs become native mobile resources. verbaly export learns two new formats: android-xml writes drop-in res/values-*/strings.xml folders and ios-strings writes *.lproj/Localizable.strings, so a web app and its mobile companion can share one set of translations. The same release makes catalog reads safer: a corrupt catalog file now stops the CLI with a clear error instead of being silently treated as empty. No breaking changes.
Highlights
- Export your translations for mobile apps.
verbaly export --format android-xmlwrites Android resource folders you can drop intores/, and--format ios-stringswrites.lprojfolders for Xcode. One catalog, web and mobile. - Sensible defaults for the platforms. Your source language becomes the platform default (
values/strings.xml,en.lproj), and untranslated keys are left out so the app falls back to the default language instead of showing empty text. - Safer catalog files. A catalog with broken JSON now stops the command and names the file, instead of being read as empty (which could have ended in lost translations on the next extract). A Windows BOM at the start of the file is simply tolerated.
For the full details of this release, see the repository changelog.