https://github.com/botforge-pro/ios-i18n-sync
iOS localization sync tool for .strings files
https://github.com/botforge-pro/ios-i18n-sync
cli i18n ios localization python swift xcode yaml
Last synced: 25 days ago
JSON representation
iOS localization sync tool for .strings files
- Host: GitHub
- URL: https://github.com/botforge-pro/ios-i18n-sync
- Owner: botforge-pro
- License: mit
- Created: 2025-08-24T00:32:35.000Z (7 months ago)
- Default Branch: main
- Last Pushed: 2026-02-23T11:30:51.000Z (27 days ago)
- Last Synced: 2026-02-23T19:51:37.425Z (27 days ago)
- Topics: cli, i18n, ios, localization, python, swift, xcode, yaml
- Language: Python
- Size: 85.9 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://www.python.org)
# iOS i18n Sync
Manage iOS localization files (`.strings`) through a single YAML file. No more editing dozens of separate files for each language. Automatically handles both `Localizable.strings` and `InfoPlist.strings`.
## Why?
- 📝 **Single source of truth** - All translations in one YAML file
- 🔍 **Easy to review** - See all languages for each key side by side
- ✅ **Find missing translations** - Instantly see which keys are missing in which languages
- 🚀 **Simple workflow** - Extract, edit, apply
- 🎯 **Smart key routing** - Automatically puts `NS*` and `CF*` keys into InfoPlist.strings
- 🔢 **Plurals support** - Parses `.stringsdict` and generates Android ``
- 🌐 **Per-app language** - Auto-generates `locales_config.xml` for Android
## Installation
```bash
pip install git+https://github.com/botforge-pro/ios-i18n-sync.git
```
## Usage
### iOS
From your iOS project root:
```bash
# Extract all .strings files (both Localizable and InfoPlist) to translations.yaml
i18n-sync extract --resources Resources
# Edit translations.yaml with your favorite editor
# Then apply changes back:
i18n-sync apply --resources Resources
```
### Android
Generate Android `strings.xml` files from the same YAML:
```bash
# Generate strings.xml for all languages
i18n-sync apply-android --input translations.yaml --res app/src/main/res
```
This creates the proper Android resource structure:
```
res/
├── values/strings.xml # Default (English)
├── values-ru/strings.xml # Russian
├── values-zh-rCN/strings.xml # Chinese Simplified
├── values-pt-rBR/strings.xml # Portuguese Brazil
├── xml/locales_config.xml # Per-app language support
└── ...
```
Language codes are automatically converted from iOS to Android format (e.g., `zh-Hans` → `zh-rCN`, `pt-BR` → `pt-rBR`).
### Plurals
iOS `.stringsdict` files are automatically parsed and converted to Android ``:
```yaml
# In translations.yaml
Plurals:
items_count:
en:
one: "%d item"
other: "%d items"
ru:
one: "%d элемент"
few: "%d элемента"
many: "%d элементов"
other: "%d элементов"
```
Generates Android:
```xml
%1$d item
%1$d items
```
### Per-App Language Support
The tool automatically generates `locales_config.xml` for Android 13+ per-app language settings:
```xml
```
Reference it in your `AndroidManifest.xml`:
```xml
```
The tool automatically:
- Extracts from both `Localizable.strings` and `InfoPlist.strings`
- Organizes translations into sections in YAML
- Preserves the structure when applying back
Default paths:
- Resources: `Resources/` directory
- YAML file: `translations.yaml`
## YAML Format
The YAML file is organized into sections corresponding to different .strings files:
```yaml
Localizable:
cancel:
en: "Cancel"
ru: "Отмена"
de: "Abbrechen"
es: "Cancelar"
save:
en: "Save"
ru: "Сохранить"
de: "Speichern"
es: "Guardar"
InfoPlist:
CFBundleDisplayName:
en: "My App"
ru: "Мое приложение"
de: "Meine App"
es: "Mi aplicación"
NSCameraUsageDescription:
en: "This app needs camera access"
ru: "Приложению нужен доступ к камере"
de: "Diese App benötigt Kamerazugriff"
es: "Esta aplicación necesita acceso a la cámara"
```
## Features
- Handles multiple .strings files (`Localizable.strings`, `InfoPlist.strings`)
- Parses `.stringsdict` for pluralization rules
- Generates Android `strings.xml` with proper `` elements
- Auto-generates `locales_config.xml` for Android per-app language
- Converts iOS format specifiers to Android (`%@` → `%s`, positional args)
- Organized YAML structure with sections
- Preserves file headers (comments at the top of .strings files)
- Sorts keys alphabetically within sections
- Reports missing translations during extract
- Handles Unicode correctly
## Why no `check` command?
The `extract` command already serves as a check - it reports the status of all translations when extracting to YAML. You'll see output like:
- `All keys present in all languages ✓` - Everything is consistent
- Missing keys are reported per language if found
There's no need for a separate `check` command since `extract` is non-destructive to your .strings files and provides all the validation information you need.