Convert MO to XLIFF2
Turn MO 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 MO files on the dialor turn it to pick what to do
A translation catalog in XLIFF 2.0.Each MO entry becomes a unit, and its state travels with it.
What you get
One XLIFF 2.0 file with one unit per entry in the MO catalog. The context of an entry becomes the name of its unit.
A plural entry becomes a group of units, so the plural forms stay together.
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 flag is still visible in the XLIFF file.
Notes, translator comments and source references are kept as notes on the unit.
What it leaves behind
Obsolete entries are dropped. They do not appear in the XLIFF file.
MO and XLIFF2.What each format is.
The formats
Gettext MO
Compiled gettext catalogs that programs load at run time, made from PO files by msgfmt.
- Extensions
- .mo .gmo
- MIME type
- application
/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 MO to XLIFF2 conversion through the API, for your app or your agent.
$ cv convert report.mo report.xlf$ cv convert report.mo report.xlfQuestions.What people ask about MO to XLIFF2.
Yes. A fuzzy translation is marked initial with the substate gettext:fuzzy.
A plural entry becomes a group of units in the XLIFF file.
The context becomes the name of the unit.
No. Obsolete entries are dropped.