Convert XLIFF2 to PO

Turn XLIFF2 files into PO. A gettext PO file with each entry's context, source text and plural source, translation or plural forms, notes, translator comments, source references, flags and fuzzy mark, obsolete entries as #~ lines, and a header with the language and its plural rule.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop XLIFF2 files on the dialor turn it to pick what to do

A gettext catalog from your XLIFF 2.0 file.Each unit becomes a PO entry with its text, translation and notes.

  1. What you get

    One PO file with a header that holds the language and its plural rule. Each entry carries its source text, its translation or plural forms, and its plural source when it has one.

    Notes, translator comments, source references and flags come across with each entry. The fuzzy mark is kept, and obsolete entries are written as #~ lines.

  2. How units are turned into text

    The segments of a unit are joined into one message. Inline codes keep their text. Placeholders such as <ph/> become their display text, so the message reads as plain text in the PO file.

    A numeric unit id is not taken as a context. It does not appear as the entry's context in the PO file.

XLIFF2 and PO.What each format is.

The formats

From · XLIFF2

XLIFF 2.0

XLIFF 2.0, the newer translation exchange format with units, segments and states.

Extensions
.xlf .xliff
MIME type
application/x-xliff2+xml
Kind
Text and data
To · PO

Gettext PO

Gettext translation catalogs and .pot templates, with each message's context, plural forms, notes and fuzzy mark.

Extensions
.po .pot
MIME type
text/x-gettext-translation
Kind
Text and data

In your code.The same XLIFF2 to PO conversion through the API, for your app or your agent.

terminal
$ cv convert report.xlf report.po
$ cv convert report.xlf report.po

Questions.What people ask about XLIFF2 to PO.

01OF 04

Yes. The fuzzy mark is kept on the entry, along with its other flags.

The segments of a unit are joined into one message in the PO file.

Yes. An entry keeps its plural source and its plural forms, and the header holds the language and its plural rule.

Placeholders such as <ph/> become their display text. Inline codes keep their text.

More conversions.Other ways in and out of XLIFF2 and PO.