Our translations are all on launchpad, and that has made it harder to keep everything in sync between svn and launchpad. However lp has made improvements and this is now easier.
To give an idea of what happens: launchpad watches our svn repo (currently 'trunk' and '0.x' branch) for changes to the POT template and individual language PO templates. when it find updates, it updates the strings in the lp translations service. in order for this to happen though, we need to generate a new POT template when we add new strings. So, I've now setup a weekly cron to generate the new POT automatically, which lp will then see when it syncs with our svn. I have also told lp to export tanslations (PO and MO templates) to a bzr branch (https://code.launchpad.net/~mattread/habari/locales). it has not exported to it as of now. But when it does I will setup a script to sync the bzr branch to our "habari-extras/locales" svn repo. We could then package them as we do with plugins/themes. But the question remains, which translations do we include in releases. I would like to have someone from each translation team volunteer to become "team leader". Then when we announce a release they can rally the troops and get the translation ready for inclusion. I don't really know what the exact process would be, but having someone to say "this is as ready as it's going to get" is better than just blindly including "the most complete ones". thoughts? -- Matt Read http://mattread.info http://mattread.com -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
