gtk+ non-update

[Clytie Siddall <clytie riverland net au>]

Hi everyone :)

I started catching up with my 2.16 updates today, and discovered one  
peculiar thing.

My gtk+ file (the "HEAD" branch, not gtk-2-8) was a couple of years  
old. In fact, it dated from before I started translating for Gnome.

There were over a hundred untranslated strings, not surprisingly, and  
merging back my gtk-2-8 file filled in most of these. I updated the  
rest.

I'm wondering, has the non-standard branching nomenclature of gtk+  
broken the update scripts in some way?

I'm always impressed by how well the Gnome scripts handle  
initializing any new strings, using our current strings. It's an  
unpleasant surprise when it doesn't happen.

I don't understand why some modules don't follow the standard HEAD  
and gnome-VERSION branches, and in this case it may even have caused  
dysfunction. Please, developers, when you branch, stick to the  
standard format. It helps us, since we don't have to try and remember  
all these odd branches, and thus it helps you, because we get our  
translations committed in the right place.

Thankyou. :)

from Clytie (vi-VN, Vietnamese free-software translation team / nhÃm  
Viát hÃa phán mám tá do)
http://groups-beta.google.com/group/vi-VN