164
164
po/gimp20.po -- the core
165
165
po-libgimp/gimp20-libgimp.pot -- the libgimp library
166
po-plugins/gimp20-std-plugins.pot -- most of the plug-ins
166
po-python/gimp20-python.pot -- the pygimp plug-ins
167
po-plugins/gimp20-std-plugins.pot -- the C plug-ins
167
168
po-script-fu/gimp20-script-fu.pot -- the script-fu scripts
168
tips/gimp-tips20.pot -- the startup tips
169
po-tips/gimp20-tips.pot -- the startup tips
170
171
If you are looking for the translations of gimp-perl, please note that
171
gimp-perl has been moved into it's own CVS module called gimp-perl.
173
When translating menu paths in Script-Fu, please do not translate the
174
name of the item factory (that is the one in brackets at the front),
175
e.g. <Image>/Script-Fu/Selection should _not_ be translated to
176
<Bild>/Skript-Fu/Kopieren, but to <Image>/Skript-Fu/Kopieren. If you
177
get this wrong, Gimp will warn you at startup about bad translations.
178
So do always test your translations and watch the console for output.
180
The version of The GIMP you are holding in your hand uses GTK+-2.0.
181
GTK+-2.0 requires that all strings are UTF-8 encoded. Therefore to make
182
internationalisation work, po files need to be UTF-8 encoded. If your
183
editor doesn't support UTF-8, you need to convert it to an encoding your
184
editor can handle and convert it back to UTF-8 before commiting your
185
changes back. The gnome-i18n module in CVS has some scripts that help
186
with this task, but it can also easily done using iconv.
172
gimp-perl has been moved into it's own Subversion module called
175
The version of GIMP you are holding in your hand uses GTK+-2.0.
176
GTK+-2.0 requires that all strings are UTF-8 encoded. Therefore to
177
make internationalisation work, po files need to be UTF-8 encoded. If
178
your editor doesn't support UTF-8, you need to convert it to an
179
encoding your editor can handle and convert it back to UTF-8 before
180
commiting your changes back. The gnome-i18n module in Subversion has
181
some scripts that help with this task, but it can also easily done
188
184
7. Adding additional textdomains
190
186
Third-party plug-ins (plug-ins that are not distributed with The
191
GIMP) can't have their messages in the gimp-std-plugins textdomain.
192
We have therefore provided a mechanism that allows plug-ins to install
193
their own message catalogs and tell The GIMP to bind to that
194
textdomain. This is necessary so that The GIMP can correctly translate
195
the menu paths the plug-in registers. Basically the plug-in has to call
196
gimp_plugin_domain_add() or gimp_domain_plugin_add_with_path() before
197
it registers any functions. Have a look at the script-fu plug-in to see
198
how this is done in detail.
187
GIMP) can't have their messages in the gimp-std-plugins textdomain.
188
We have therefore provided a mechanism that allows plug-ins to
189
install their own message catalogs and tell GIMP to bind to that
190
textdomain. This is necessary so that GIMP can correctly translate
191
the menu paths the plug-in registers. Basically the plug-in has to
192
call gimp_plugin_domain_add() or gimp_domain_plugin_add_with_path()
193
before it registers any functions. Have a look at the script-fu
194
plug-in to see how this is done in detail.
200
196
8. Tip of the Day messages