Re: Preparing to release F-Spot 0.7.0

[Petr Kovar <pmkovar gnome org>]

Ruben Vermeersch <ruben savanne be>, Fri, 11 Jun 2010 21:11:48 +0200:

> On Fri, 2010-06-11 at 21:01 +0200, Petr Kovar wrote:
> > Hi!
> > 
> > Ruben Vermeersch <ruben savanne be>, Tue, 08 Jun 2010 11:20:31 +0200:
> > 
> > > On Tue, 2010-06-08 at 11:17 +0200, Ruben Vermeersch wrote:
> > > > Hi all,
> > > > 
> > > > I'm preparing to release F-Spot 0.7.0 in a week or so, when we get
> > > > most bugs ironed out. there are a few (but not much) string changes
> > > > since 0.6.2. Now is the time to update translations for 0.7.0, if
> > > > you would like to get them in!
> > > 
> > > 
> > > Oh and I forgot to mention the most important fact: Harold
> > > Schreckengost converted all our user help to Mallard and massively
> > > actualized it. There were only a few string overlapping so I'm afraid
> > > translations will need to be redone (sorry for that, blame shaunm!).
> > > 
> > > Status can be found here: http://l10n.gnome.org/module/f-spot/
> > 
> > Thanks for mentioning it. I see that the localized help content is still
> > stored within the docs directory:
> > 
> > http://git.gnome.org/browse/f-spot/tree/docs
> > 
> > I'm not sure about its usefulness though, since I guess most
> > translators/committers will forget and/or won't be able to locate it
> > there. Therefore I guess that it'd be better to either move all the
> > contents to the new help directory, or remove it altogether.
> 
> I left it there because it might be useful to translators trying to port
> over the translations from the old to the new documentation. But if you
> guys think it is ok to remove it, I'll gladly do it.

I can surely only appreciate your intention, but as I wrote, this way it
doesn't seem to very useful since l10n.gnome.org/module/f-spot (now without
any visible user guide translations) is what most translators work with
anyway, my guess is that the majority of them won't clone the f-spot
repository just to locate and make use of the old user guide localization.
For them, it's too developer-centric way.

But then again, maybe the respective committers/coordinators should provide
the content move for each team...

Regards,
Petr Kovar