Convert PO to TMX
Turn PO files into TMX. A TMX 1.4 translation memory with one translation unit per finished entry, holding the source and target segments, the context as a property and the notes and comments 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
A translation memory from your PO catalog.Each finished entry becomes one TMX translation unit. Fuzzy and untranslated entries are left out.
What you get
One TMX 1.4 file. Every finished entry in the catalog becomes one translation unit with its source and target segments.
The message context is kept as a property of the unit. The notes and comments on an entry are kept as notes on the unit.
What is left out
Fuzzy entries and untranslated entries do not appear in the TMX file, so the memory holds only translations that are finished.
Plural entries keep their first form. The other plural forms are not copied. Source references and obsolete entries are dropped.
PO and TMX.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
TMX Translation Memory
Translation Memory eXchange files of aligned source and target segments.
- Extensions
- .tmx
- MIME type
- application
/x -tmx +xml - Kind
- Text and data
In your code.The same PO to TMX conversion through the API, for your app or your agent.
$ cv convert report.po report.tmx$ cv convert report.po report.tmxQuestions.What people ask about PO to TMX.
No. Fuzzy and untranslated entries are left out. Only finished entries become translation units.
Each plural entry keeps its first form. The other forms are not in the TMX file.
Yes. The context is kept as a property of the translation unit, and the notes and comments are kept as notes.
No. Source references are dropped, and so are obsolete entries.