---

4.9 Editing PO Files

We anticipate that some gnu.org translators will find this format odd or inconvenient, if they never happened to work with PO files before⁶. Don’t worry, you will soon get accustomed to it. It is the established format for translations in the Free World, and if you have any problems, other translators will help you.

The most efficient way to edit a PO file is using a specialized PO editor, because each of them represents and treats gettext messages in a consistent and predictable way. It is possible to edit a PO file with an ordinary plain text editor, but extra effort would be necessary to make the result valid.

Note that recent versions of some PO editors (both offline and web-based) offer access to various translation services that do machine translation for their users. Using a machine translation service is a clear example of SaaSS (see Who does That Server Really Serve?), so please don’t use such editors unless they only submit requests to your (or GNU project’s) own servers.

Here is a list of widely used PO editors we can recommend:

• PO mode. We recommend using GNU Emacs in PO mode, because Emacs is the program that is suitable for performing any task when it comes to maintaining the GNU Project’s website. Provided that you have GNU gettext installed, any .po file you visit should automatically switch to PO mode. You can enable/disable it with M-x po-mode RET. On some GNU/Linux distros such as gNewSense, PO mode is available in a separate package, gettext-el. See Emacs’s PO File Editor in GNU gettext tools.
• Gtranslator—the GNOME PO editor. See http://projects.gnome.org/gtranslator/.
• Lokalize—the KDE 4 editor. See http://userbase.kde.org/Lokalize.
• KBabel—the KDE 3 editor. No longer supported, but might be available on some old systems.
• Poedit—another popular editor that is based on the wxWidgets graphical toolkit. See http://www.poedit.net.
• po.vim—ftplugin for the Vim editor. The best option for people who use Vim as their editor. See http://www.vim.org/scripts/script.php?script_id=2530.