*** empty log message ***
This commit is contained in:
@ -118,7 +118,6 @@ Thu Dec 30 15:21:29 GMT 1999 Adam D. Moss <adam@gimp.org>
|
|||||||
* plug-ins/common/animoptimize.c: PDB interface patch
|
* plug-ins/common/animoptimize.c: PDB interface patch
|
||||||
from Andreas Jaekel <jaekel@cablecats.de>
|
from Andreas Jaekel <jaekel@cablecats.de>
|
||||||
|
|
||||||
>>>>>>> 1.1987
|
|
||||||
Thu Dec 30 02:34:49 CET 1999 Marc Lehmann <pcg@goof.com>
|
Thu Dec 30 02:34:49 CET 1999 Marc Lehmann <pcg@goof.com>
|
||||||
|
|
||||||
* app/gradient.c: Applied patch by Daniel Egger:
|
* app/gradient.c: Applied patch by Daniel Egger:
|
||||||
|
41
README.i18n
41
README.i18n
@ -1,7 +1,7 @@
|
|||||||
This document exists to document the important things to care for
|
This document exists to document the important things to care for
|
||||||
because of locale support.
|
because of locale support.
|
||||||
Actually this one is maintained by me, that is Daniel Egger
|
Actually this one is maintained by me, that is Daniel Egger
|
||||||
(Daniel.Egger@t-online.de).
|
(Daniel.Egger@rz.fh-muenchen.de).
|
||||||
|
|
||||||
1. Why localisation?
|
1. Why localisation?
|
||||||
|
|
||||||
@ -10,7 +10,8 @@ Actually this one is maintained by me, that is Daniel Egger
|
|||||||
even those people sometimes like to use good and free software
|
even those people sometimes like to use good and free software
|
||||||
without using a dictionary to get the unknown words.
|
without using a dictionary to get the unknown words.
|
||||||
So why not simply localise the software to make it available to
|
So why not simply localise the software to make it available to
|
||||||
the mass which isn't wholly English native?
|
the mass which isn't wholly English native? Of course this also
|
||||||
|
eases the migration from PhotoX to GIMP. :))
|
||||||
|
|
||||||
2. How?
|
2. How?
|
||||||
|
|
||||||
@ -32,40 +33,40 @@ Actually this one is maintained by me, that is Daniel Egger
|
|||||||
libgimp directory which check whether gettext is available on the system
|
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.
|
which GIMP is compiled on and will deactivate language support if it's not.
|
||||||
You CAN use such a compiled GIMP even without the catalogs or on a system
|
You CAN use such a compiled GIMP even without the catalogs or on a system
|
||||||
which dosen't enable language support.
|
which dosen't have language support.
|
||||||
|
|
||||||
If the gettext system is there it will declare 3 functions which will be
|
If the gettext system is there it will declare 3 functions which will be
|
||||||
described below.
|
described below.
|
||||||
|
|
||||||
3.1 _() [more correctly: char * _( char * )]
|
3.1 _() [more correctly: char * _( char * )]
|
||||||
|
|
||||||
This one is a macro for the function gettext(). With it every text may be
|
This one is a macro for the function gettext(). You can wrap any text with
|
||||||
wrapped that is directly called directly in a function. If you use it the
|
it that is allowed to be a return value of a function. If you use it then
|
||||||
given string will be tried to get translated in the native language of the
|
libintl will try to translate it into the native language of the
|
||||||
user according to his/her environmental settings.
|
user according to his/her environmental settings.
|
||||||
The gettext() function will do a lookup in the hashed gimp.mo which contains
|
The gettext() function will do a lookup in the hashed catalog which contains
|
||||||
all the translated texts.
|
all the translated texts.
|
||||||
|
|
||||||
- If it is found a pointer to the string will be returned to the caller.
|
- 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.
|
- 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
|
This way it is ensured that there isn't any harm caused to the program
|
||||||
(i.e. The GIMP) if no catalog isn't installed.
|
(i.e. The GIMP) if no useful catalog is installed.
|
||||||
|
|
||||||
Please note that it is important to use _() directly (and not gettext())
|
Please note that it is important to use _() directly (and not gettext())
|
||||||
for simple messages because of reasons that will be mentioned below.
|
for simple messages because of reasons that will be mentioned below.
|
||||||
|
|
||||||
NOTE: I know some of the developer like short functions like _() but
|
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 a better source understanding I suggest to use it consistently only
|
||||||
for text (like _("That's text!") ) and not for variables (like _(text) BUT
|
for text (like _("That's text!")) and not for variables (like _(text) ) BUT
|
||||||
gettext(text) instead)
|
gettext(text) instead.
|
||||||
|
|
||||||
|
|
||||||
3.2 N_() [more correctly: void ( void ) ]
|
3.2 N_() [more correctly: void ( void ) ]
|
||||||
|
|
||||||
This one is a macro for the function gettext_noop(). As you can see and
|
This one is a macro for the function gettext_noop(). As you can see and
|
||||||
guess it doesn't really anything in the programm i.e. it is a dummy
|
guess it doesn't really do anything in the programm i.e. it is a dummy
|
||||||
function but nevertheless important. As it isn't possible to call functions
|
macro but nevertheless important. As it isn't possible to call functions
|
||||||
in a structure as seen here:
|
in a structure as seen here:
|
||||||
|
|
||||||
struct blurb
|
struct blurb
|
||||||
@ -74,12 +75,12 @@ Actually this one is maintained by me, that is Daniel Egger
|
|||||||
}
|
}
|
||||||
|
|
||||||
you have to do it in some other way. In GIMP such structures are often used
|
you have to do it in some other way. In GIMP such structures are often used
|
||||||
to create menues or similar things very simply. Here you have to use the
|
to create menus or similar things very simply. Here you have to use the
|
||||||
dummy to allow the generation of a template which will be described below.
|
dummy to allow the generation of the template catalog which will be described
|
||||||
This one doesn't do anything but it marks the text as important to the
|
below. This one doesn't do anything but it marks the text as important to
|
||||||
gettext extractor.
|
the xgettext extractor.
|
||||||
|
|
||||||
The text has to be translated "by hand" with the next function.
|
The text has to be translated manually with the next function.
|
||||||
|
|
||||||
3.3 gettext()
|
3.3 gettext()
|
||||||
|
|
||||||
@ -137,7 +138,7 @@ Actually this one is maintained by me, that is Daniel Egger
|
|||||||
add all strings that are in the template but not in the uncompiled catalog
|
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
|
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 fuzzy logic method for already translated strings for possible reduction
|
||||||
of programmers work: If a original string seems similar to a new one
|
of translators work: If a original string seems similar to a new one
|
||||||
and it already has a translation, it will be taken over to the new catalog
|
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.
|
together with a remark that this one may not necessarily fit.
|
||||||
|
|
||||||
@ -145,7 +146,7 @@ Actually this one is maintained by me, that is Daniel Egger
|
|||||||
|
|
||||||
I hope I mentioned everything that is worth it and hope that this document
|
I hope I mentioned everything that is worth it and hope that this document
|
||||||
will clarify some things. If it doesn't please write me a mail and tell me
|
will clarify some things. If it doesn't please write me a mail and tell me
|
||||||
what you want to know. This text may contain errors, so if you find one
|
what you want to know. This text of course contains errors, so if you find one
|
||||||
tell it to me, too....
|
tell it to me, too....
|
||||||
|
|
||||||
Happy Gimping. Yours,
|
Happy Gimping. Yours,
|
||||||
|
Reference in New Issue
Block a user