So we should do a clean-up and come up with a good system to avoid this in the future.
Some work and thinking has been done in bug MDL-15252, but this has to be discussed in this forum and decisions have to be made eventually.
1 requires 2 i.e. we cannot perform the clean-up properly without branching, but branching language packs has it risks too:
1) translators must LEARN to use and commit them properly
Branching involves having a Moodle 1.9, a Moodle 2.0, Moodle 2.1 and perform each translation in the corresponding one and committing the translation to the corresponding branch.
We could make a clean start for Moodle 2.0 on a new download page, like we did for 1.6, but then the problem starts building up if we don't do branching.
Another track is to install on a Moodle.org box all maintained Moodle versions, give translators an admin account on it with the translating capability set. A demo course can be stored (and may be restored every X time) to have something to play with. The box updates daily
A robot can daily move the translated files in the correct CVS branch.
-no need to do anything with CVS for translators - branching is automatically
-no need to install anything for translators: translating is done on the Moodle servers
-no need to change anything on the translation interface
This is problematic AFAIK for
-moodle.com: yet another set of installations to maintain
-translators who like playing with CVS
-translators who like translating directly on the files.
Maybe those last two groups can have a CVS account to do their thing on the files, but I would keep that as an exception.
Sorry for this long post - with this length it hardly looks like a summary
Please give your ideas and comments!