From: Bjoern V. <bj...@cs...> - 2006-02-25 23:51:31
|
Hello! During translation I found some difficult to understand GTK+ i18n strings. This strings are in gtkcellview.c gtkcombobox.c gtkexpander.c This files are imported from the GTK+ libraries (>=3D2.4.0) for compatibility reasons (missing widgets in older GTK+ libraries). This three files cause around 30 translation strings. Some of them are hard to translate (like "Row span column") for people without detailed GTK+ knowledge. From=20this three files only two have working _() markers: gtkcellview.c gtkcombobox.c gtkexpander.c contains P_() markers and a NOOP function "#define P_(x) (x)". There are two other GTK+ imported files which do not have any i18n strings: gtkcelllayout.c gtkcellviewmenuitem.c 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. 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. 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? I personally prefer 2). Regards, Bj=F6rn |