Looking for the latest version? Download cinepaint-1.0-4.tar.gz (12.2 MB)
Home / OldFiles
Name Modified Size Downloads / Week Status
Parent folder
Totals: 44 Items   281.6 MB 57
MacCinepaint-0.24.dmg 2008-04-15 15.9 MB 11 weekly downloads
cinepaint-0.22-0_0.22-1.diff.gz 2007-06-12 769.5 kB 0
glasgow.0.1a.zip 2006-12-22 3.3 MB 0
glasgow.0.1.zip 2006-12-22 3.3 MB 0
MacCinePaint-0.21-2.nativ.dmg.gz 2006-11-01 21.0 MB 22 weekly downloads
cinepaint-0.21-0.tar.gz 2006-04-04 10.8 MB 0
MacCinePaint-0.20-3_rc3.dmg 2006-03-17 9.4 MB 0
MacCinePaint-0.20-1.dmg 2005-11-12 52.4 MB 11 weekly downloads
cinepaint-0.20-0.tar.gz 2005-10-31 7.6 MB 0
test.me-0.1.zip 2005-09-19 228.0 kB 3838 weekly downloads
cinepaint-0.19-1.tar.gz 2005-05-28 7.3 MB 0
cinepaint-0.18-3_cms2.tar.gz 2004-11-20 7.2 MB 0
MacCinePaint-0.18-2.dmg.gz 2004-03-29 32.5 MB 0
MacCinePaint-0.18-1-2src.tgz 2003-11-16 18.4 kB 0
MacCinePaint-0.18-1-2.dmg.gz 2003-11-16 498.6 kB 0
MacCinePaint-0.18-1-2src.tar.gz 2003-11-10 17.8 kB 0
ffd.color.cube.pdf 2003-09-05 110.6 kB 0
gimp.1.3.17.README.i18n.txt 2003-08-26 9.9 kB 11 weekly downloads
cmyk.separate-0.1.tar.gz 2003-08-26 273.8 kB 0
cmyktiff.tgz 2003-08-26 1.1 MB 0
MacCinePaint-0.18-1src.tar.gz 2003-08-09 13.5 kB 0
MacCinePaint-0.18-1.dmg.gz 2003-08-09 50.1 kB 0
Windows.CinePaint.0.18-1.exe 2003-08-04 4.6 MB 33 weekly downloads
cinepaint-0.18.tar.gz 2003-07-28 9.7 MB 0
MacCinePaint-FimGimp-0.16-4src.tar.gz 2003-06-25 13.3 kB 0
MacCinePaint-FimGimp-0.16-4.dmg.gz 2003-06-25 49.6 kB 11 weekly downloads
MacCinePaint-FimGimp-0.16src.tar.gz 2003-06-24 13.8 kB 0
MacCinePaint-FimGimp-0.16.dmg.gz 2003-06-24 50.0 kB 0
cinepaint-filmgimp-0.16.tar.gz 2003-06-21 7.0 MB 0
cinepaint-filmgimp-devel-0.16-1.i386.rpm 2003-06-21 40.6 kB 0
cinepaint-filmgimp-0.16-1.i386.rpm 2003-06-21 6.3 MB 0
cinepaint-0.17.src.win32.tar.gz 2003-06-11 16.8 MB 0
cinepaint-0.17.src.tar.gz 2003-06-11 8.4 MB 0
Windows.CinePaint.0.16-3.vcpp.src.exe 2003-05-12 8.8 MB 11 weekly downloads
cinepaint-0.16-3.src.tar.gz 2003-05-12 7.3 MB 0
Windows.CinePaint.0.16-3.exe 2003-05-12 4.3 MB 11 weekly downloads
cp.win32.libplugin.zip 2003-05-02 3.7 MB 0
cp.win32.gtk.zip 2003-05-02 2.9 MB 0
filmgimp-0.16-2.win32.tar.gz 2003-03-24 7.1 MB 11 weekly downloads
windows.CinePaint.0.16-2.exe 2003-03-24 4.2 MB 0
filmgimp-0.16-2.tar.gz 2003-03-24 7.1 MB 77 weekly downloads
filmgimp-0.16-2.win32.zip 2003-03-24 5.1 MB 0
mac.and.linux.downloads.html 2003-03-14 475 Bytes 0
install.CinePaint.0.16-1.exe 2003-03-12 4.3 MB 0
This document exists to document the important things to care for because of locale support. It is aimed at developers and translators. If you are a translator, you can skip the first sections, but you definitely want to read sections 5 - 9. Table of Contents 1. Why localisation? 2. How 3. Deep inside ... 4. Some magic ... 5. Tools and how to use them 6. Gimp is different 7. Adding additional textdomains 8. Tip of the Day messages 9. How to contribute 10. And more ? 1. Why localisation? Many persons from many countries start to get used to Linux. Unfortunately not everyone is able to understand English. But even those people sometimes like to use good and free software without using a dictionary to get the unknown words. So why not simply localise the software to make it available to the mass which isn't wholly English native? Of course this also eases the migration from PhotoX to GIMP. :)) 2. How? GNU provides a very nice package called gettext. This one offers the possibility to translate chosen messages from the native language of the program into that one of the users if a necessary catalog is provided. Gettext therefore provides some easy tools to create and maintain such catalogs and a few functions which can be called by the program to enable automatic translation at runtime. The program gets linked to the gettext library or glibc2 which already provides that functionality and everything is fine. 3. Deep inside... GIMP provides header files called gimpintl.h and stdplugins-intl.h in the libgimp directory which check whether gettext is available on the system which GIMP is compiled on and will deactivate language support if it's not. If the gettext system is there it will declare 3 functions which will be described below. 3.1 _() [more correctly: char * _( char * )] This one is a macro for the function gettext(). You can wrap any text with it that is allowed to be a return value of a function. If you use it then libintl will try to translate it into the native language of the user according to his/her environmental settings. The gettext() function will do a lookup in the hashed catalog which contains all the translated texts. - If it is found a pointer to the string will be returned to the caller. - If not, the caller will receive a pointer to the original string. This way it is ensured that there isn't any harm caused to the program (i.e. The GIMP) if no useful catalog is installed. Please note that it is important to use _() directly (and not gettext()) for simple messages because of reasons that will be mentioned below. NOTE: I know some of the developer like short functions like _() but for a better source understanding I suggest to use it consistently only for text (like _("That's text!")) and not for variables (like _(text)). Use gettext(text) instead. 3.2 N_() [more correctly: const char * ( const char * ) ] This one is a macro for the function gettext_noop(). As you can see and guess it doesn't really do anything in the programm i.e. it is a dummy macro but nevertheless important. As it isn't possible to call functions in a structure as seen here: struct blurb { _("This won't work\n"); } you have to do it in some other way. In GIMP such structures are often used to create menus or similar things very simply. Here you have to use the dummy to allow the generation of the template catalog which will be described below. This one doesn't do anything but it marks the text as important to the xgettext extractor. The text has to be translated manually with the next function. 3.3 gettext() This function is the same as that macro in 3.1. But there is one big difference: The _()'s and N_()'s are the only expressions which get parsed by the template generator. If you have strings that should be translated but are unfortunately in a structure you have to do that on your own which means that you have to parse the fields with the messages in a loop and translate the texts with this gettext() function. Please note that it may be necessary to free or allocate memory in this case! 4. Some magic... As you have seen we only did the programming part until now but this isn't all by far. To use catalogs we'll have to create them. Now there are 3 different files which are importart: gimp.pot: This one is the so called template. It contains the messages which are extracted from the sources and empty fields which have to get filled by the author. It is used to start a new catalog or to update the an already available one. The Makefile will automatically call the program gettext which will extract all messages that are wrapped by a _() or a N_() (but NOT gettext()) and concat them to this template. [language].po: This file has to be an edited gimp.pot and contains the original messages plus the translated ones. This file will be delivered together with GIMP and is the base for the final catalog. [language].mo: This file is a compiled version of [language.po] which will be automatically compiled by the Makefile system and installed in the locale directory of the system. It contains everything that the .po file contains except not translated messages, comments and other overhead. For maximum speed it is also hashed to allow gettext a faster search. 5. Tools and how to use them As mentioned the to be translated strings are extracted directly from the source and written to the template. I guess many of you will now ask if it is necessary to add new strings directly to the template or if there's a tool to achieve that. I think I can calm down those of you who fear lots of had work just to update the language files. There's a program called msgmerge which will add all strings that are in the template but not in the uncompiled catalog to it. Msgmerge does this job very nicely and also tries to use some kind of fuzzy logic method for already translated strings for possible reduction of translators work: If an original string seems similar to a new one and it already has a translation, it will be taken over to the new catalog together with a remark that this one may not necessarily fit. 6. Gimp is different Gimp is a complex application which has a bunch of scripts and plug-ins that all want to be internationalized. Therefore there is not one catalog but many. For a full translation of the GIMP's UI, you will have to add translations for the following catalogs: po/gimp14.po -- the core po-libgimp/gimp14-libgimp.pot -- the libgimp library po-plugins/gimp14-std-plugins.pot -- most of the plug-ins po-script-fu/gimp14-script-fu.pot -- the script-fu scripts tips/gimp-tips14.pot -- the startup tips If you are looking for the translations of gimp-perl, please note that gimp-perl has been moved into it's own CVS module called gimp-perl. 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>/Edit/Copy should _not_ be translated to <Bild>/Bearbeiten/Kopieren, but to <Image>/Bearbeiten/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. Unfortunately most editors don't support UTF-8, so to edit your po file, 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 CVS has some scripts that help with this task, but it can also easily done using iconv. 7. Adding additional textdomains Third-party plug-ins (plug-ins that are not distributed with The GIMP) can't have their messages in the gimp-std-plugins textdomain. We have therefore provided a mechanism that allows plug-ins to install their own message catalogs and tell The GIMP to bind to that textdomain. This is necessary so that The GIMP can correctly translate the menupaths the plug-in registers. Basically the plug-in has to call gimp_plugin_domain_add() or gimp_domain_plugin_add_with_path() before it registers any functions. Have a look at the script-fu plug-in to see how it is done in detail. 8. Tip of the Day messages In addition to message catalogs Gimp provides a file with tips that are displayed in a Tip of The Day window. This file is in XML format and can be found in the tips directory. The english tips messages are extracted from gimp-tips.xml.in so translators can use the usual tools to create a <lang>.po file that holds the translations. All translations are then merged into gimp-tips.xml with language identifiers taken from the po filename. GIMP needs to know what language it should select from gimp-tips.xml. Therefore, there's the special message "tips-locale:C" in the main message catalog that needs to be translated correctly. For a german translation of the tips this would look like this: #: app/gui/tips-parser.c:158 msgid "tips-locale:C" msgstr "tips-locale:de" 9. How to contribute Any help with translations is appreciated. If you want to help, please get in contact with the people from the GNOME Translation Project who coordinate all translation efforts in the GNOME CVS tree. They have a nice web-page at http://developer.gnome.org/projects/gtp/. 10. And more? We hope we mentioned everything that is worth it and hope that this document will clarify some things. If it doesn't please write us a mail. This text of course contains errors, so if you find one tell us... Happy Gimping. Daniel Egger Sven Neumann
Source: gimp.1.3.17.README.i18n.txt, updated 2003-08-26