PO Editors

PO Editors

Every .po catalog in phpbbdocs-languages is plain text (gettext format), so a plain text editor works fine. These dedicated editors add PO-aware conveniences: fuzzy/untranslated filtering, side-by-side source/target view, and catching syntax errors before you commit.

• Poedit — the most common choice. Free tier covers everything needed here (side-by-side editing, translation memory, warns on fuzzy/untranslated entries before you save). Windows, macOS, Linux.
• Lokalize — KDE's translation editor. Linux-native, also has a translation-memory database and a glossary feature useful for keeping terminology consistent across a long catalog like events_list.po.
• Gtranslator — GNOME's equivalent to Lokalize. Similar feature set, GTK interface.
• OmegaT — a fuller CAT (computer-assisted translation) tool, not PO-specific. More setup than the three above, worth it mainly if you're translating multiple files at once and want cross-file translation memory.

All four are free. If you already use a paid translation platform and prefer it, nothing here requires switching: a .po file is a .po file regardless of what wrote it.

Whichever you use, the actual requirement is just a syntactically valid .po file when you're done. ./translations.sh check <lang> / devdocs-check <lang> (see Script Reference) validates that either way, tool-agnostic.

See Translator Workflow for what to actually do with one of these once it's open.