-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Clytie Siddall wrote:
Mark, I didn't mean in my personal copy of Mailman. I mean in the repo. Shouldn't at least the POT file be automatically updated in each branch?
This has to be some kind of compromise. Considering the 3.0 branch (formerly the trunk), there have certainly been changes and there will be more, some of which will remove prior additions. This also happens to a lesser extent on the more stable branches. We don't want to keep making a moving target for translators, so in the past, we have set a point around a first beta release where i18n strings should be frozen for that release, and that's when we update the POT file and announce that the release is ready for translation. I am a little unclear myself on exactly how and when this is done as I have never done it although I have observed the results. Certainly we can discuss doing this more frequently. In the recent past, I have avoided making changes to the i18n strings in the 2.1 branch, because I thought the trunk would form the basis of a 2.2 release in the near future. Now that 2.2 has branched from 2.1 and not the trunk (3.0), and it looks like the near term release will be 2.1.10, I will be backporting some of my trunk changes to 2.2 and some even to 2.1. In any case, my opinion is that updating the POT any time i18n strings are added or changed is too frequent, but perhaps the current schedule (whatever it is) is not frequent enough. Of course, you can always update the POT in your working copy (or local branch in bzr) any time you want to work on changes. - -- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGrgygVVuXXpU7hpMRAj3NAKDdCEmHXbqQM8mNUiQyj3M+g4p/YACg6AgK HV1byZoAgsc47K12j/Wf21Q= =9anj -----END PGP SIGNATURE-----