=D0=88=D1=83=D1=87=D0=B5 =D1=83 0:51, Bjoern Voigt =D0=BD=D0=B0=D0=BF=D0=B8=
=D1=81=D0=B0:
> Now my questions?
>
> 1) Do we really need to translate the i18n strings in the imported GTK+
> files?
>
> I think no, because
> - the strings are never (or nearly never, may be on errors) visible
> to the user
> - only users with an old GTK+ setup (<=3D2.6.0) will use this imported
> files
>
> 2) If we decide that it's not useful to translate the i18n strings in
> the imported files, it's easy to disable the strings. The file
> gtkexpander.c for instance has it disabled.
"Property descriptions" can freely be disabled, IMHO. They are not
useful, and are only visible in a prospective "GObject class browser",
and I am not sure that such a thing exists. They will not be seen by
users. This is the main reason we split this in Gnome (so translators
know that they don't need to translate this for full Gnome support).
All strings marked with P_ are such "property descriptions". Other
strings are actually useful.
> 3) If we decide that it's useful to translate the i18n strings I
> suggest to use the original GTK+ translations.
>
> I used the following command for this:
>
> msgmerge -U XX.po gaim.pot -C <PATH-TO>/gtk+-2.8.X/po-properties/XX.po
>
> Unfortunately it's necessary to clear old translations and fuzzy
> marks from the GTK+ imported entries in XX.po. Own translations in
> XX.po (also fuzzy translations) will not be changed with the
> translations from GTK+ source.
I suggest you leave that to translators themselves, even if you keep
the strings. Providing a tip like this should be enough.
> 4) It's also possible to use multiple translation files for each
> language (e.g. one for Gaim and one for the imported GTK+ files for
> each language). Does someone know, how much work does this action
> cause?
That's a bit complicated, even if intltool supports it somewhat, it
may get ugly (you'll probably have to do some Makefile hacking anyway).
Cheers,
Danilo
|
