Re: Moduleset Reorganization -- Take two

[Gil Forcada <gforcada gnome org>]

Hi!

El dg 10 de 10 de 2010 a les 01:41 +0200, en/na Petr Kovar va escriure:
> Hi!
> 
> Michael Terry <mike mterry name>, Fri, 8 Oct 2010 10:30:14 -0400:
> 
> > On 8 October 2010 03:13, Johannes Schmid <jhs jsschmid de> wrote:
> > >> The best solution IMHO would be to import PO files for all
> > >> applications, and integrate them into Damned Lies. Else, we're taking
> > >> the risk of losing consistency, and « moduleset » won't mean anything
> > >> in the end.
> > >
> > > I am afraid that the problem is not to import PO files in damned-lies
> > > but to commit them from damned-lies to the repositories. And we have to
> > > find a solution for this while keeping the current permissions that are
> > > specific to git.gnome.org.
> > 
> > From a Launchpad perspective, a translation branch can be imported
> > from git into a bzr branch in Launchpad.  This would involve zero
> > change from an LP maintainer perspective (currently, there is a bzr
> > branch in LP for translations that gets written to by translators
> > through the web interface; maintainers merge that branch before a
> > release).
> > 
> > So the trick then would be having Damned Lies import pot/po files from
> > a bzr trunk.  Then GNOME translators can edit them in git like they
> > like.  Then LP can import that translation branch with changes.
> > 
> > Eh?
> 
> I think that would be very acceptable to GNOME translators, while keeping
> the main development at a location of developer's preference.
> 
> (CC'ing gnome-i18n as this is definitely of interest to the members of that
> group as well.)
> 
> Best,
> Petr Kovar
> _______________________________________________
> gnome-i18n mailing list
> gnome-i18n gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-i18n


Being a module on the applications moduleset should be a coin with its
two sides: being famous as an application in a GNOME official set but
some requirements as explained in the propuse sent by Vincent.

As Emmanuele already said on the thread discussing Clutter
translations[1] one way to go could be creating not-official
repositories on GNOME infrastructure synchronized wit the official one
where the GNOME i18n can send their translations and the module
developers should only have to pull from.

With translations the VCS used is not that important since the last
translation is the important so the developer could just grab the po
folder and put on their VCS.

That way translators can keep their focus on translating and not going
through different systems to send the translations, but also since
everything would be in one place more nice things could be created
(automatic fuzzies for strings already translated on other modules,
glossaries, translation memories, an API to query translation status and
update them...).

If we deliver a rock solid GNOME 3.0 but with all kind of
mistranslations everywhere no one would use it.

Cheers,

[1] http://mail.gnome.org/archives/gnome-i18n/2010-October/msg00016.html

-- 
gil forcada

[ca] guifi.net - una xarxa lliure que no para de créixer
[en] guifi.net - a non-stopping free network
bloc: http://gil.badall.net
planet: http://planet.guifi.net