Formats, merge & MO build

Supported formats

  • .po — open and save (full gettext: msgctxt, msgid_plural, refs #:, flags #,, comments #., obsolete #~ ignored).
  • .pot — opens as a template (all strings untranslated).
  • .mo — compiled from the editor (see below).

Catalog merge

When the game updated and produced a new .pot/.po: open the old translated file → «Update catalog» → pick the new file. The app matches entries (context+source+plural), shows a preview (preserved/added/removed) and, after confirmation, carries translations over. Changed sources get an empty translation — translate them again (AI pre-translation covers them from your pack).

MO compilation

Ctrl+M (or File → Compile MO) builds a binary .mo from the current file. Untranslated strings are not included. The format is fully gettext-compatible (msgid/msgctxt/plural, a correct header with Plural-Forms from the file header). Put the .mo into the game/app localization structure.

Encodings

Files are read and written in UTF-8. Escapes (\\n, \\t, \\", \\\\) are decoded on read and restored on write — lossless round-trip.