Helps you localize your app String Catalogs. Start enjoying the benefits of this Xcode 15 localization feature with ease.
- No need to learn XLIFF XML formats or invest in complex translator tools.
- Translate all your app texts and localized string resources in minutes, using the two best machine translation APIs: DeepL and Google.
- Continue to use your favorite manual localization workflow, either with text editor, spreadsheet or scripts to other APIs.
- Keep localizations consistent across your apps with your own glossary of localization rules. Especially for cases where machine/AI translators struggle, like buttons with a single word.
How does fast and easy localization work?
- You need to configure the app first, for machine translation (explained here), manual translation by populating the built-in rules database (explained here) or both.
- After configuration, follow these simple steps: 1) Export Localizations from Xcode, 2) select the folder that Xcode exported, 3) if the summarized results look ok, import the now localized content of this folder back into Xcode. Now the screens of your app show texts in the langauges you planned.
- A step by step walkthrough of this process, with detailed screenshots, can be found here.
- String catalog keys that already have a filled localized string are not translated. Selecting the same folder again will give different results, typically strings reported skipped because already localized.
- Configuration and Settings determine which of the three “translators” will be used and in which order. This is shown in the light grey status bar, above the ‘Select’ (and localize immediately) button.
- The app finds all XLIFF files in the Localizations folder exported from Xcode String Catalogs. All in one go: hundreds of keys with dozens of localizations in multiple catalogs.
• Strings with interpolations, pluralizations (single and multiple) and variants by device are no problem at all.
– Try it with this small test app: https://github.com/prosultsstudio/XLIFF-Localizer-Testcases.
• Manual workflows supported by .csv and json file export and import. No need to obtain (free) personal API keys from DeepL Translator or Google Cloud Translation.