file formats are available via the Files ↓ Customize download menu: • gettext PO • XLIFF with gettext extensions • XLIFF 1.1 • TermBase eXchange • Translation Memory eXchange • gettext MO (only available formats store two languages in single file—source and translation (typical examples are GNU gettext, XLIFF or Apple iOS strings). On the other side, monolingual formats identify the string by ID, and each yes yes yes yes9 needs edit- ing Mono- lingual gettext mono yes yes yes yes yes9 needs edit- ing XLIFF both yes yes yes yes yes10 needs editing, approved Java prop- erties both no yes no no no mi18n

file formats are available via the Files ↓ Customize download menu: • gettext PO • XLIFF with gettext extensions • XLIFF 1.1 • TermBase eXchange • Translation Memory eXchange • gettext MO (only available formats store two languages in single file—source and translation (typical examples are GNU gettext, XLIFF or Apple iOS strings). On the other side, monolingual formats identify the string by ID, and each yes yes yes yes9 needs edit- ing Mono- lingual gettext mono yes yes yes yes yes9 needs edit- ing XLIFF both yes yes yes yes yes10 needs editing, approved Java prop- erties both no yes no no no mi18n

file formats are available via the Files ↓ Customize download menu: • gettext PO • XLIFF with gettext extensions • XLIFF 1.1 • TermBase eXchange • Translation Memory eXchange • gettext MO (only available formats store two languages in single file—source and translation (typical examples are GNU gettext, XLIFF or Apple iOS strings). On the other side, monolingual formats identify the string by ID, and each yes yes yes yes9 needs edit- ing Mono- lingual gettext mono yes yes yes yes yes9 needs edit- ing XLIFF both yes yes yes yes yes10 needs editing, approved Java prop- erties both no yes no no no mi18n

file formats are available via the Files ↓ Customize download menu: • gettext PO • XLIFF with gettext extensions • XLIFF 1.1 • TermBase eXchange • Translation Memory eXchange • gettext MO (only available formats store two languages in single file—source and translation (typical examples are GNU gettext, XLIFF or Apple iOS strings). On the other side, monolingual formats identify the string by ID, and each yes yes yes yes9 needs edit- ing Mono- lingual gettext mono yes yes yes yes yes9 needs edit- ing XLIFF both yes yes yes yes yes10 needs editing, approved Java prop- erties both no yes no no no mi18n

XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF2 JavaScript JSON i18next files3 34 Chapter 1. User docs The Weblate Manual, Release 4.0.3 Following formats store two languages in single file—source and translation (typical examples are GNU gettext, XLIFF or Apple iOS strings). On the other side, monolingual formats identify the string by ID, and each yes yes yes yes yes9 needs editing Monolingual gettext mono yes yes yes yes yes9 needs editing XLIFF both yes yes yes yes yes10 needs editing, ap- proved Java properties both no yes no no no Joomla

XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF2 JavaScript JSON i18next files3 34 Chapter 1. User docs The Weblate Manual, Release 4.0.2 Following formats store two languages in single file—source and translation (typical examples are GNU gettext, XLIFF or Apple iOS strings). On the other side, monolingual formats identify the string by ID, and each yes yes yes yes yes9 needs editing Monolingual gettext mono yes yes yes yes yes9 needs editing XLIFF both yes yes yes yes yes10 needs editing, ap- proved Java properties both no yes no no no Joomla

XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF2 JavaScript JSON i18next files3 34 Chapter 1. User docs The Weblate Manual, Release 4.0 Following formats store two languages in single file—source and translation (typical examples are GNU gettext, XLIFF or Apple iOS strings). On the other side, monolingual formats identify the string by ID, and each yes yes yes yes yes9 needs editing Monolingual gettext mono yes yes yes yes yes9 needs editing XLIFF both yes yes yes yes yes10 needs editing, ap- proved Java properties both no yes no no no Joomla

XML resource files Perl GNU gettext Ruby Ruby YAML files Web extensions WebExtension JSON Java XLIFF2 JavaScript JSON i18next files3 34 Chapter 1. User docs The Weblate Manual, Release 4.0.1 Following formats store two languages in single file—source and translation (typical examples are GNU gettext, XLIFF or Apple iOS strings). On the other side, monolingual formats identify the string by ID, and each yes yes yes yes yes9 needs editing Monolingual gettext mono yes yes yes yes yes9 needs editing XLIFF both yes yes yes yes yes10 needs editing, ap- proved Java properties both no yes no no no Joomla

available via the Files ↓ Customize download menu: • gettext PO (po) • XLIFF with gettext extensions (xliff) • XLIFF 1.1 (xliff11) • TermBase eXchange (tbx) • Translation Memory eXchange (tmx) • gettext 4.18 1.10.36 XLIFF XML-based format created to standardize translation files, but in the end it is one of many standards, in this area. XML Localization Interchange File Format (XLIFF) is usually used Weblate supports XLIFF in several variants: XLIFF translation file Simple XLIFF file where content of the elements is stored as plain text (all XML elements being escaped). XLIFF with placeables support

available via the Files ↓ Customize download menu: • gettext PO (po) • XLIFF with gettext extensions (xliff) • XLIFF 1.1 (xliff11) • TermBase eXchange (tbx) • Translation Memory eXchange (tmx) • gettext 18.2 1.10.36 XLIFF XML-based format created to standardize translation files, but in the end it is one of many standards, in this area. XML Localization Interchange File Format (XLIFF) is usually used Weblate supports XLIFF in several variants: XLIFF translation file Simple XLIFF file where content of the elements is stored as plain text (all XML elements being escaped). XLIFF with placeables support