Convert PO to XLIFF2
Turn PO files into XLIFF2. An XLIFF 2.0 file with one unit per entry, the context as the unit's name, a plural entry as a group of units, and each segment's state as initial, translated or final, where a fuzzy translation is initial with the substate gettext:fuzzy, with notes, translator comments and source references as notes.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop PO files on the dialor turn it to pick what to do
PO catalogs as XLIFF 2.0 files.Each entry becomes a unit, with its context, notes and state carried over.
What you get
One XLIFF 2.0 file with one unit per entry. The context of an entry becomes the unit's name.
A plural entry becomes a group of units.
States and notes
Each segment gets a state of initial, translated or final. A fuzzy translation is marked initial with the substate gettext:fuzzy, so the fuzzy mark is not lost.
Notes, translator comments and source references are written as notes.
What it leaves behind
Obsolete entries are dropped. They do not appear in the XLIFF 2.0 file.
PO and XLIFF2.What each format is.
The formats
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
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
In your code.The same PO to XLIFF2 conversion through the API, for your app or your agent.
$ cv convert report.po report.xlf$ cv convert report.po report.xlfQuestions.What people ask about PO to XLIFF2.
Yes. A fuzzy translation is written as initial with the substate gettext:fuzzy.
It becomes the name of the unit.
A plural entry becomes a group of units.
No. Obsolete entries are dropped.