Most translations can be made by creating and modifying .po files. However, there are still exceptions to this rule. This page is meant to summarize such situations in GNOME packages.


  • Default welcome mail


    In the evolution/mail/default/$LANG directory (where $LANG is your two-letter language code),

    • copy and translate the default/mail/C/Inbox file,
    • copy default/mail/C/, replacing only C by $LANG
    • add the path to this Makefile in, under the "dnl Makefiles" list

    • add $LANG to default/

  • Quick Reference PDF file


    In the evolution/help/quickref/$LANG directory (where $LANG is your two-letter language code),

    • copy the english .tex file from evolution/help/quickref/C/quickref.tex
    • edit that .tex file and translate it according to the terms that are used in your translated evolution - in order to not confuse the user, make sure that you do not use different terms for the same functionalities. Use the same expressions as in evolution's translated menus, also for the term "quick reference card".
    • when finished, create a pdf file - see the comments at the beginning of the tex file for a howto:
      • {{{latex quickref.tex

dvips -t letter -f -Pcmz < quickref.dvi >| ps2pdf -sPAPERSIZE=letter}}}

  • copy evolution/help/quickref/C/, replacing only C by $LANG
  • add $LANG to SUBDIRS in evolution/help/quickref/
  • add help/quickref/$LANG/Makefile to evolution/

In the $LANG dir, commit only the, quickref.pdf and quickref.tex (no other transitional files).


Pangrams shown in font viewers/editors may use the pango_language_get_sample_string() API to get a pangram. Pangrams are stored in the Pango source tree, in /pango/pango-language-sample-table.h. Enter a bug in the pango product of GNOME bugzilla to add/modify the pangram for your language.


Glom's files can contain translations for the various table names, fields, relationships, choices, layout groups, reports, etc. This lets multiple people use the same database UI in different languages. These translations are exported to .po files so translators can use their familiar tools.

These are imported back into the .glom files every now and then.

Feel free to add new .po files, based on the .pot file in the directory.

GIMP Installer for the Microsoft Windows Platform

The installer is created with Innosetup, which uses its own translation files. The English version is the master, and located at - grab this file and translate it if you want to contribute a translation for a language that is not yet covered (see for the current translations).

Note that these files contain the GIMP-specific strings only. Innosetup itself comes with some translations for its common strings already (see, their master file is The encoding is language-dependent. It should match the encoding for the Inno Setup language file. There's LanguageCodePage near the top of each file, that's the Windows codepage used.


TranslationProject/TranslationsOutsideStatus (last edited 2016-05-05 16:17:50 by YuriKonotopov)