don’t forget to add new files with translatable strings to POTFILES.in/POTFILES.skip, otherwise those new strings will not be caught. quickly check http://l10n.gnome.org/module/$MODULENAME to get a list of those files (they are listed at the top of the “UI translations” section under “Notices” – if there are none, you’re a good maintainer(TM) and deserve a cookie.
GNOME’s translators are very creative with regard to working around bad strings. however, it seems that they are way too friendly by not filing bug reports against modules with hard-to-translate strings. why?
are you keen on trying to translate “Read” (“has been read”? or “something to read”?), “Profile” (“a profile”? or “to profile”?) or “%s at %s on behalf of %s” properly by try&error guessing, or do you love spending time on reading the source code?
you’ve got better things to spend your time on! there aren’t many bug reports on translation issues in gnome bugzilla, which surprised me. so please file bug reports against the affected modules and add the “L10N” keyword, and if a string definitely has to be rephrased then please also add the “string” keyword to your report. help the developer to understand your problem, by linking to a good explanation, e.g. if a comment would help to understand how to translate a string, add a link explaining how to use comments, if a sentence is splitted up, add a link to your bug report to the explanation why this is bad behaviour. it only takes you a minute and will help everybody to get a better localized desktop.
if you like your favourite desktop and want to give some of the love back, why not getting involved by helping your translation team?
just take a look at the webpage and write an email to your translation team leader that you are interested in getting involved (if you do not receive an answer to your email within two weeks, please complain to gnome-i18n mailing list and CC the team leader on your email, because this should not happen.).
we have a webpage that provides wonderful statistics about which modules are in need of an update – choose your language, click on “GNOME 2.20 (development)” and then click on the icon of a module. then take gtranslator, kbabel, poedit or your favourite text editor to make the translation perfect again, then let the team leader upload your file, that’s all. easy, eh? :-)
languages in need of more translators
for my guadec talk (page 15f.), i compared the translation stats of 2.14 to those of 2.18 to find out which languages probably need more manpower. beside of course those languages that have always been on a low level, the following languages with more than 50% ui translation have lost quite a lot:
nepali (-20%), albanian (-14%), indonesian (-12%), czech and croatian (-11%), romanian and nynorsk (-10%).
also, i wonder whether those translation teams that have 99% ui translation (and therefore obviously enough human ressources) but less than 3% documentation translation (arabic, dzonghka, macedonian, hungarian, catalan, finnish, lithuanian, danish, japanese, vietnamese) could perhaps also translate a few docs for 2.20? we all know that a fully translated ui is much more important than having translated docs, but perhaps, perhaps some people can spend an additional little amount of time on translating the doc of their favourite application (again: if new translators are interested – of course feel free to join and help, see above).
general disclaimer: if you do not like translating, but want to help making GNOME even better: there are also many other ways how you can get involved.
“and now for something completely different.” looks like some of the issues that i described in my guadec talk are on a good way now:
- willem is interested in providing better analysis tools for bugzilla, something that could make it easier to analyze/identify bottlenecks and the quality of our modules and services. looking forward to it.
- if i remember the last guadec evening correctly (we were all so damn busy with fixing the showstopper bug 455415), don told me that somebody talked to him about working on providing a better tracking of our documentation status. i don’t know if it’s the same thing as gil described here – vertimus, used by the frenchies, looks quite advanced, compared to the stuff used by the dutchies (i don’t remember the exact url, this one here is for the docs) or germans.
yes, one evening at the etap, we introduced the systems used by the translation teams to each other. that’s why guadec is so cool.
- i’d like to thank danilo for addressing our gtp bottleneck.
i’m a pretty happy camper currently.