Comments on Stephane's log: Multiple branches and translations

You need to fix up your page at http://l10n.gnome....

2009-11-07T16:22:30.507+01:00

You need to fix up your page at
http://l10n.gnome.org/module/f-spot/

It's messy; you contact gnome-i18n for this.

Heh, if you were using Launchpad, translators coul...

2009-11-06T19:06:27.632+01:00

Heh, if you were using Launchpad, translators could work only on a single version (usually stable), and translations would propagate to all versions where they are for exactly the same English string.

It happens real-time, so there's no opportunity for duplicate work other than work that happens externally, but that's not a solvable problem :)

FWIW, this feature was designed precisely to solve observed problem in GNOME. I hope we will be able to make GNOME (and f-spot) benefit from this feature.

Hi Stéphane, You should announce your stable branc...

2009-11-06T16:32:45.925+01:00

Hi Stéphane,
You should announce your stable branch to gnome-i18n and ask translator
to commit on it (the branch will be tracked prioritarily by
l10n.gnome.org). And when you're working in master again, just tell
gnome-i18n about the change. Coordinators generally know the process of
merging from a branch to trunk.

À+

Claude

I am the coordinator of the Bulgarian Gnome transl...

2009-11-06T15:35:43.860+01:00

I am the coordinator of the Bulgarian Gnome translation project. On receiving a new translation I always commit on stable and master in GNOME git. Plus we have an internal svn where we keep copies of all the translations — (stable and master).
With the sometimes huge diffrerence between the branches, I am not aware of any automatic means of solving this.
Kind regards:
al_shopov