Convert PO to MO
Turn PO files into MO. A compiled gettext MO file with the finished translation of every entry, its context and its plural forms, as programs load them at run time.
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 compiled catalog that programs can load.Your PO file becomes one MO file with the finished translations.
What you get
A single MO file, the compiled form of a gettext catalog that programs load at run time. It holds the finished translation of every entry, along with its context and its plural forms.
What it leaves out
Fuzzy entries and untranslated entries are left out, as gettext ignores them anyway. Obsolete entries are left out too.
Notes for translators, translator comments and source references are dropped. The MO file holds only what a program needs to show the translated text.
PO and MO.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
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
In your code.The same PO to MO conversion through the API, for your app or your agent.
$ cv convert report.po report.mo$ cv convert report.po report.moQuestions.What people ask about PO to MO.
It was fuzzy, untranslated or obsolete. Those entries are not compiled, as gettext ignores them.
Yes. Each entry keeps its context and its plural forms along with its translation.
PO files and .pot templates are both accepted as input. A template holds no finished translations, so entries without a translation are left out.
No. Notes for translators, translator comments and source references are dropped from the MO file.