Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


Tree [f18b7b] gimp-plugin-ng / po /

File Date Author Commit
.cvsignore 2005-01-05 dwilkins42 dwilkins42 [0799e4] Ignore compiled translations
ChangeLog 2008-01-15 brunopostle brunopostle [048a65] Add po/ChangeLog file required for 'dist' target
LINGUAS 2009-05-17 brunopostle brunopostle [f18b7b] Add missing LINGUAS file
Makefile.in.in 2009-05-15 brunopostle brunopostle [3688cf] Fix to build with automake 1.10 (Philippe Vanha...
POTFILES.in 2005-01-05 dwilkins42 dwilkins42 [24dce1] Initial revision
PanoPlugin.pot 2005-01-05 dwilkins42 dwilkins42 [f6b75b] Update translations
README.translators 2005-01-05 dwilkins42 dwilkins42 [0ae10e] Add readme for translations
de.po 2005-01-05 dwilkins42 dwilkins42 [f6b75b] Update translations
fr.po 2005-01-05 dwilkins42 dwilkins42 [f6b75b] Update translations
pl.po 2005-01-05 specu specu [ec4ad7] gimp-plugin-ng: partial Polish translation

Read Me

When translating menu paths, please do not translate the
name of the item factory (that is the one in brackets at the front),
e.g. <Image>/Script-Fu/Selection should _not_ be translated to
<Bild>/Skript-Fu/Kopieren, but to <Image>/Skript-Fu/Kopieren. If you
get this wrong, Gimp will warn you at startup about bad translations.
So do always test your translations and watch the console for output.
The version of The GIMP you are holding in your hand uses GTK+-2.0.
GTK+-2.0 requires that all strings are UTF-8 encoded. Therefore to make
internationalisation work, po files need to be UTF-8 encoded. If your
editor doesn't support UTF-8, you need to convert it to an encoding your
editor can handle and convert it back to UTF-8 before commiting your
changes back. The gnome-i18n module in GNOME CVS has some scripts that
help with this task, but it can also easily done using iconv.