[Mailman-i18n] Updating translations

Stefaniu Criste webmaster at dizain.ro
Mon Jul 30 21:27:37 CEST 2007

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

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 at python.org
> Unsubscribe:
> http://mail.python.org/mailman/options/mailman-i18n/webmaster%40dizain.ro

More information about the Mailman-i18n mailing list