Convert MO to TMX

Turn MO 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 MO files on the dialor turn it to pick what to do

A translation memory from a compiled catalog.Each finished entry becomes one TMX translation unit.

  1. What you get

    A TMX 1.4 file, one file in all. It holds one translation unit for each finished entry in the MO catalog, with the source segment and the target segment side by side.

    The context of an entry is stored as a property. Notes and comments are stored as notes on the same unit.

  2. What is left out

    Fuzzy entries and untranslated entries are not included, so only finished translations reach the memory. Obsolete entries are dropped too.

    Plural entries keep their first form. The other plural forms are not written to the TMX file.

MO and TMX.What each format is.

The formats

From · MO

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
To · TMX

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 MO to TMX conversion through the API, for your app or your agent.

terminal
$ cv convert report.mo report.tmx
$ cv convert report.mo report.tmx

Questions.What people ask about MO to TMX.

01OF 04

Yes. The context is written as a property on the translation unit.

Yes. Notes and comments are written as notes on the translation unit.

Fuzzy, untranslated and obsolete entries are left out. Only finished entries become translation units.

They keep their first form only. The other forms are not carried into the TMX file.

More conversions.Other ways in and out of MO and TMX.