2.3.4 Useful Hints For Editing PO Files

This section contains additional explanations, some in the form of advices and recommendations; not all of them are strictly related to PO files editing.

• When you install a new translation of an article (that is different from a server template or the homepage), all you need to do is to add your PO file in the appropriate /po sub-directory and add a link to it in the translations list of the original article.html. Use only HTML entities for any non-ASCII characters and follow the established scheme. If language names in your native language are not capitalized (unlike for example in English or German), you should not capitalize the name of your language.

  In the next build, your article.lang.html will be built and the link to it will propagate to all translations, provided that they are under GNUN's control.

• If you don't feel comfortable editing gnun.mk, do not worry. Someone from the GNUN maintainers will notice and will amend TEMPLATE_LINGUAS or HOME_LINGUAS for you, as appropriate.
• Dealing with obsolete strings. Elements which are removed from the original articles appear in the PO files as “obsolete” strings—the translation is not lost, but they are marked in a special way at the end of the PO file. You don't have to update a PO file if it contains obsolete strings—do this only if it has “fuzzy” or “untranslated”, and of course when you want to improve the existing translated ones. Sometimes these obsolete strings are useful, and they can save time. For example, if you anticipate that the deleted text may reappear some time in the future, you can preserve the string and hopefully it would be marked as “fuzzy” when this happens. Failing that, you can still copy it and yank it at the appropriate place.
• You can add comments to every message in a PO file—for example if you want to remember that you have to do something, or to remind you why this particular message is translated in a special way. These comments do not appear in the generated HTML source.
• Sometimes, especially when the original message contains many links, it is easier to copy it to msgstr and edit the latter by translating the English text. In PO mode, this is done by C-j. This is useful also for large chunks of text in <pre> elements, which normally you would want to preserve verbatim.
• To reduce the load on the webmasters RT queue, please replace webmasters@gnu.org in the standard footer with web-translators@gnu.org.
• If you translate “Free Software Foundation, Inc.” in your native language in the copyright notice, then please prepend the English name to the <address>; otherwise it looks awkward in most languages. Example:

            # type: Content of: <div><address>
            msgid "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA"
            msgstr ""
            "Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, "
            "Boston, MA 02110-1301, USA"
  

• There is absolutely no reason to use HTML entities in translations as a replacement for common non-ASCII characters. They are harder to write and serve no purpose.
• Wrapping of msgstr using M-q in Emacs (or other means) is considered harmful. It is best to leave GNUN (or more precisely, Po4a) to do the wrapping—that way all generated HTML translations will have predictable results. This will help tremendously for the conversion to other formats, like Texinfo. Also, note that not all elements are wrapped by default, so deliberately wrapping the text inside the msgstr could lead to an invalid page or a page that is valid, but is rendered incorrectly by the web browser.