Better lies about GNOME localisation

  • : Function ereg() is deprecated in /var/www/translate.org.za/blogs/friedel/includes/file.inc on line 895.
  • : Function ereg() is deprecated in /var/www/translate.org.za/blogs/friedel/includes/file.inc on line 895.
  • : Function ereg() is deprecated in /var/www/translate.org.za/blogs/friedel/includes/file.inc on line 895.

I had the pleasure of meeting Claude Paroz, the maintainer of Damned Lies (the system for localisation statistics and workflow at GNOME). We started thinking about how Damned Lies might be able to provide guidance for smaller teams on prioritisation, and statistics that might provide better help with problems people want to address.

From time to time, GNOME localisers discuss the localisation statistics, and people often mention the arbitrary method used for calculating "supported" status. Of course, there is a reason why Damned Lies has the name it has, and teams should probably not give too much attention to the numbers. However, Damned Lies also functions as a place where decisions are taken (which module should be translated next), and where people get their motivation (progress between releases).

People came up with more specific suggestions after the release of the GNOME i18n survey in October 2010, with lots of discussion in this thread started by Gil Forcada. People were discussing the idea of ignoring some possibly less important strings for translation for better statistics (lies), better prioritisation, and better motivation. GConf schema strings are always mentioned, as well as the developer tools, and there was also talk of error messages and things that are only printed on the console. Identifying error messages and console messages is not trivial, but it is mostly trivial to identify GConf schema strings. Gil also published the numbers to show what portion of the total work is taken up by GConf strings:

  • 3158 strings out of 45785 (6.8974%)
  • 35074 words out of 205155 (17.096%)

That is a humongous amount of work. Not translating GConf strings means that your language has almost no chance of being "supported". Extra reasons for leaving these out could be that they are not really aimed at the end-user as much as other strings, and that they tend to be more technical and therefore more demotivating. A lot of teams also give a lower prioritisation to the developer tools like Anjuta.

I wrote earlier about trimming a localisation task to get it to a manageable size. Not everyone can easily do this kind of thing, but with our work in Africa, this is probably what most languages should do before they move onto doing more. If we could provide this kind of help through Damned Lies, we could hopefully help teams to put their time into what is probably most important, and hopefully provide better motivation that might help us to retain more translators and build more successful teams. In the end, I hope that users will receive the main benefit, since GNOME can be available in more languages, and that partial translations are more likely to have translations where it matters to the average user.

Lots of the details still need to be worked out, but it feels as if this is within reach. Claude already has ideas of how he wants to approach the changes to Damned Lies (probably the biggest job), and I have some ideas about trimming modules to a smaller size. For a start, just ignoring GConf schema strings can already help a lot.

Comments

Thanks!

Thanks for bringing back the topic and also to try to tackle the matter.

From time to time I'm also thinking about it, but I still haven't done any look at the Damend-Lies source code.

Could you elaborate more about what are you (Claude and you) up to? I'm really interested on helping as much as my spare time allows me.

I'm glad that the survey ended being useful.

We should also take a look at how many languages have been supported from release to release.:
2.32: 52 languages
2.30: 50 languages
2.28: 52 languages
2.26: 48 languages
2.24: 45 languages
2.26: 45 languages

It's improving, right, but there's 169 languages right now on Damned-Lies, so 75% of them aren't considered supported.

Thanks for all your efforts!!
Cheers,

part of original damned-lies goals

This was part of original damned-lies goals, however I've lost time to work on it since then. It was even listed in the HACKING file as part of the TODO: http://git.gnome.org/browse/damned-lies/tree/HACKING?id=90ba810e49a14f89...

Some of the things are still relevant (like the .schemas translations that you mention), but others might not be anymore. I am very happy to see that amazing Claude is finally going to do something about this.

Reproducing here for the click-lazy:


Judging Translation Support Levels:
-----------------------------------
Not everything that can be counted counts; and not everything that
counts can be counted. //George Gallup

- Level 0:
not fulfilling even Level 1 requirements

- Level 1:
check percentage for every PO file EXCLUDING:
- irrelevant modules (gtk+/po-properties, gstreamer, xkeyboard-config, gnome-applets/po-locations ...)
- translations exclusively for .schemas.in files
- special checks for what we know we can exclude?

- Level 2 (fully usable UI translation: no gconf or non-visible things translated)
- xkeyboard-config
- iso_codes
- gnome-applets/po-locations (at least the relevant part: top-level
countries and entries for relevant country for a language)
...

- Level 3 (complete UI translation)
- .schemas.in translations as well
- gnome-applets/po-locations (full translation)
- gtk+/po-properties
- gstreamer
- scrollkeeper
...

- Level 4 (UI + docs)
- Level 2 + docs translation

- Level 5 (full UI+docs translation)
- Level 3 + docs translation

Level 0: unsupported
Level 1: partially supported
Level 2/3: supported
Level 4: excellent support
Level 5: "Gnome badge of honour" or "we owe you a beer" award :)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

19 + 0 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.