Serious problems with missing translations!

[Timo Jyrinki]

> All Gnome packages are in GNOME, but a team does not use Rosetta as an
> official tool. The team frequently updates the upstream translations.
> These translations are not reflected in Rosetta.
> 
> At the same time other people translate using Rosetta. They are
> newbies, playing around, have no contact with the official team, do
> not adhere to standards. The official team does not even know of them.
> 
> What appears in Ubuntu will be the translations of the second group!
> Not quite what we want, eh?

I agree. Gnome translation teams are generally better organized and controlled
than the Rosetta teams currently. Translations from Gnome l10n project should
always take precedence.

I see this will continue to be the case until the following features are fulfilled:
- diffs to every older version of the strings, string-specific (old1: %s, old2:
%s, old3: %s... but so that when new upstream translation is uploaded, old:s get
cleaned and maybe made just suggestions if needed)
- diffs to upstream (whole PO-file)
- all strings of a package on one page -option (can do searches with the browser)
- Rosetta l10n team leader(s) can see all the changes of some team member
- Rosetta l10n team leader(s) have 7 days to review final translations while the
others can't do changes aymore

And even then, probably Gnome/KDE l10n teams' translations should probably be
imported as is, and then clearly mark that "now the translations are in, the
Rosetta team can improve / fill in missing". But before those five points are
fulfilled, the quality of Rosetta-made translations is in my opinion too hard to
follow/control.

-Timo