HI everyone :) I'm trying to catch up with my translations (after not being able to contribute for some months), but I can't seem to find any translations needing updating in Mailman. Even the POT file in the Mailman 3.0 branch has a last-modified date of 2006-04-28. The vi.po files in each branch are complete, and haven't been changed since I last submitted them. Surely there are new strings or changed strings needing updating. But how do I find them? Thankyou for any help you can offer with this. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Clytie Siddall wrote:
Surely there are new strings or changed strings needing updating. But how do I find them?
After running configure, cd to the messages directory and run
make potclean
make potfile
This will remove the existing marked.files, docstring.files and
mailman.pot files and rebuild them.
Note that this is done in the distribution/configure/make directory, not
in the install directory.
- --
Mark Sapiro
On 29/07/2007, at 2:45 PM, Mark Sapiro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Clytie Siddall wrote:
Surely there are new strings or changed strings needing updating. But how do I find them?
After running configure, cd to the messages directory and run
make potclean make potfile
This will remove the existing marked.files, docstring.files and mailman.pot files and rebuild them.
Note that this is done in the distribution/configure/make directory, not in the install directory.
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? mailman.pot in the /messages dir of the Mailman 3.0 branch shows a latest revision number of 6349 and a last-changed date of 2006-04-28. It has no new or changed strings compared with my Trunk translation of last year. I can't believe there have been no changes since then. :o from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
-----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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 30, 2007, at 12:06 PM, Mark Sapiro wrote:
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.
One idea is to try to switched to timed updates for the translations. For example, we could say that on the 1st of every month (i.e. Mailman Day <wink>), we'll update the pot files and push the changes to the official branches. Then translators will have what they need to update their translations. We can then say that on something like the 21st of each month, translators should send us their updates, or make sure their branches are updated for us to merge.
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.
Excellent Mark, thanks.
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.
- -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRq4eOnEjvBPtnXfVAQJJ9wP6At4zRtEddCdTIfWAGARpQdyRnZkCB6NX mNmZ+T78wtCKOetQs3o7Zeklv7Am4dHCnhihM52JP76mbrykm7as3CARkkP7ck4T dRPPAyjyod9cGLfGFL2Q2/maft9vSt3A3yDxYUPBvk0bt4fj/oT9vhrAdJoPRd+x FlmKihtNuJk= =AZIp -----END PGP SIGNATURE-----
I am trying to update Romanian translation but seems I have no permission to commit into ..../LC_MESSAGES/ro folder. - I do have my sourceforge ssh keys updated - I have tried this using KDESVN - my SF username is webdizainro Any help would be appreciated. Stefaniu Criste Romania On Monday 30 July 2007 20:22:02 Barry Warsaw wrote:
On Jul 30, 2007, at 12:06 PM, Mark Sapiro wrote:
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.
One idea is to try to switched to timed updates for the translations. For example, we could say that on the 1st of every month (i.e. Mailman Day <wink>), we'll update the pot files and push the changes to the official branches. Then translators will have what they need to update their translations. We can then say that on something like the 21st of each month, translators should send us their updates, or make sure their branches are updated for us to merge.
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.
Excellent Mark, thanks.
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.
-Barry
_______________________________________________ Mailman-i18n mailing list Posts: Mailman-i18n@python.org Unsubscribe: http://mail.python.org/mailman/options/mailman-i18n/webmaster%40dizain.ro
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stefaniu Criste wrote:
I am trying to update Romanian translation but seems I have no permission to commit into ..../LC_MESSAGES/ro folder.
The Mailman SVN repository on sourceforge is now read only (see
http://sourceforge.net/docs/E09#notice if you are having trouble
reading too).
Current development uses Bazaar branches hosted on Launchpad.
See http://wiki.list.org/display/DEV/MailmanOnLaunchpad and
http://wiki.list.org/display/DEV/MailmanBranches for more information.
Also see Barry's post at
http://mail.python.org/pipermail/mailman-i18n/2007-July/001497.html
and Clytie's reply in that thread.
- --
Mark Sapiro
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 28, 2007, at 2:49 AM, Clytie Siddall wrote:
Even the POT file in the Mailman 3.0 branch has a last-modified date of 2006-04-28. The vi.po files in each branch are complete, and haven't been changed since I last submitted them.
Hi Clytie, At this point, no one should waste time trying to translate the 3.0 branch. A lot has changed and a lot /will/ change yet. For example, I'm currently working on changing the entire address registration and confirmation stuff. Strings and templates that used to talk about confirming a list subscription now talk about confirming an email address registration. The 2.1 pot file should definitely be up-to-date. If not, we need to regenerate it. The 2.2 pot file should be pretty much up-to-date, although it may change as we start to see the fruits of the new web u/ i. I still think it's a little early to start translating 2.2, but we should make sure the 2.1 branch has updated pot files, and we should concentrate on getting the translations up-to-date for 2.1.10. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRq4dUXEjvBPtnXfVAQJvtwP8DxfTCZN0bCpBKGV7yJLsL1Poa9Vk99f9 MsFq7pYsJtgxFRwmkwJG0aeHLNoCddD2dmwwJcC9+AHeQzd8pWh+p/g/+tCzqYy6 KNqF5s6I5bTCDJuuuOzaLLYwGkonMauGy4bfcNT3P02ciSLzb6rYRpQ3pkkUB0sl n0mzYokq7CA= =4LW2 -----END PGP SIGNATURE-----
On 31/07/2007, at 2:48 AM, Barry Warsaw wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jul 28, 2007, at 2:49 AM, Clytie Siddall wrote:
Even the POT file in the Mailman 3.0 branch has a last-modified date of 2006-04-28. The vi.po files in each branch are complete, and haven't been changed since I last submitted them.
Hi Clytie,
At this point, no one should waste time trying to translate the 3.0 branch. A lot has changed and a lot /will/ change yet. For example, I'm currently working on changing the entire address registration and confirmation stuff. Strings and templates that used to talk about confirming a list subscription now talk about confirming an email address registration.
The 2.1 pot file should definitely be up-to-date. If not, we need to regenerate it. The 2.2 pot file should be pretty much up-to- date, although it may change as we start to see the fruits of the new web u/i. I still think it's a little early to start translating 2.2, but we should make sure the 2.1 branch has updated pot files, and we should concentrate on getting the translations up- to-date for 2.1.10.
OK, as long as my translations are up-to-date, that's my main concern. :) from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do) http://groups-beta.google.com/group/vi-VN
participants (4)
-
Barry Warsaw -
Clytie Siddall -
Mark Sapiro -
Stefaniu Criste