mo
What is a .mo file?
application/x-gettext-translation
A MO file (.mo, Machine Object) is the compiled binary form of a gettext PO catalog used at runtime by gettext libraries. It stores msgid/msgstr pairs in a compact hashed table for fast lookup.
How to use a .mo file
Use an example .mo file to test gettext runtime loaders, MO parsers, and PO↔MO conversion tooling.
Download example .mo files
- Gettext MO — FrenchCompiled gettext MO binary for French — pair with the matching PO for loader tests.
- Gettext MO — GermanCompiled gettext MO binary for German — pair with the matching PO for loader tests.
- Gettext MO — Portuguese (Brazil)Compiled gettext MO binary for Portuguese (Brazil) — pair with the matching PO for loader tests.
- Gettext MO — KoreanCompiled gettext MO binary for Korean — pair with the matching PO for loader tests.
- gettext MO with Plural-Forms — Polish (compiled)The compiled Polish MO twin. Plural entries are encoded the way msgfmt does it — the original is 'singular\\0plural' and the translation is the 3 forms joined by NUL — and the header entry carries the Plural-Forms expression, so ngettext resolves without the .po file present.
- gettext MO with Plural-Forms — Russian (compiled)The compiled Russian MO twin. Plural entries are encoded the way msgfmt does it — the original is 'singular\\0plural' and the translation is the 3 forms joined by NUL — and the header entry carries the Plural-Forms expression, so ngettext resolves without the .po file present.
- gettext MO with Plural-Forms — Arabic (compiled)The compiled Arabic MO twin. Plural entries are encoded the way msgfmt does it — the original is 'singular\\0plural' and the translation is the 6 forms joined by NUL — and the header entry carries the Plural-Forms expression, so ngettext resolves without the .po file present.
- gettext MO with Plural-Forms — Welsh (compiled)The compiled Welsh MO twin. Plural entries are encoded the way msgfmt does it — the original is 'singular\\0plural' and the translation is the 6 forms joined by NUL — and the header entry carries the Plural-Forms expression, so ngettext resolves without the .po file present.
and 4 more in the library.