Skip to main content
Apple XLIFF (.xliff)
Fedya Levkin avatar
Written by Fedya Levkin
Updated over a week ago

To learn more about XLIFF files in general and how to work with them in Lokalise, please check out our detailed blog post.

To learn about generic XLIFF format and support in Lokalise, please check the corresponding article.

The process of generating, importing and exporting XLIFF is outlined in XCLOC documentation.

Apple XLIFF is the format generated by Xcode.

Starting with Xcode 10 it is stored in the Localized Contents directory of Xcode Localization Catalog (XCLOC) which is generated instead of XLIFF files.

Apple XLIFF is based on standard 1.2 XLIFF specifications and includes support for plural translations (starting with Xcode 9) and variable width translations (starting with Xcode 10).

When generating an XLIFF file, Xcode aggregates translations for all .strings and .stringsdict files as well as localizable resources that use .strings file type for localization (.storyboard, .xib and Info.plist files).

Special notes and limitations

  • Plural translations are supported by Lokalise.

  • Variable width translations are not supported by Lokalise.

  • While the XLIFF is an industry standard, for iOS projects we recommend using .strings and .stringsdict files directly. XLIFF has its benefits (like the ability to generate keys for new elements in .storyboard files) but comes with a drawback that limits Lokalise as a translation management platform.

  • When importing an XLIFF to Xcode every key must have the same base (source) language value in the Xcode project and in the XLIFF document. In the case of mismatch, updates to these keys are ignored. It means that it's not possible to use Lokalise to update base (source) language values.

  • Translation for non-base (non-source) languages will be ignored if value for base (source) language was also changed.

Did this answer your question?