Sorry about resuming an old thread, but since most translations are not kept up to date, what about switching to the Translation Project instead?

There are experienced teams for the languages that Subversion is currently translated into and many more. The risk for orphaned localisations will be lower since the teams deal with continuity themselves. Users will enjoy higher consistency in terms of vocabulary and style across software packages.

The details can be read at http://translationproject.org, but in essence, it would work as follows:

1. As a release is getting near, the Subversion release manager sends the .pot file, or an URL to a source tarball containing the .pot file (that is up to date), to the project. 2. As each translation is finished, a robot will send the .po file to this list. 3. Someone, perhaps the release manager, commits the .po files as they arrive.

Reply via email to