On 08/12/2006, at 2:08 AM, Ain Vagula wrote:
I think it is good idea to start at least with languages, having high percent of translated strings and approved quality. Maybe it is reasonable to raise count of languages eg. to 20 or 30. I have no idea how to automate determining which languages will be "in", other translation projects have a central statistics page (kde, gnome, suse). It makes a bit competitive feeling too, every time I start SUSE translation, I look at stats and think, that this time I leave 2 or 3 languages behind my back ;)
I agree, Ain. :)Status pages are extremely useful. They give you a one-glance idea where you are, and keep you motivated.
I hate to see my files under 100%. It really bugs me. :DWe're using Pootle, so we have full, one-glance stats on our translation, but it would also be good to have a table on the OOo website or wiki, showing overall stats for the language projects' translations, and then a page per project. This information is useful in many ways: to stimulate effort, to keep track of progress, to see which languages are actively maintained, even for users to see how thoroughly OOo is translated into their language. ;)
The KDE status pages are the best example of their kind. http://l10n.kde.org/stats.php and the code is GPL.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
PGP.sig
Description: This is a digitally signed message part
