[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Translations: String freezes, CVS converging, Packaging

On Wed, 2007-03-07 at 08:58 -0800, Karsten Wade wrote:
> On Wed, 2007-03-07 at 11:06 -0500, Jeremy Katz wrote:
> > > To do this we need to try not to add new strings after the freeze and let the
> > > L10n folks know if they need to do so. Also, maintainers should repackage before
> > > each release (and after the translation freeze) without a bug needing to be
> > > opened.
> > 
> > Yep
> Can we look into automating this in some fashion?  Not for F7, but for
> releases following?  Or is that not necessary?

The problem is that you have to do a release bump (which is different
for every package) as well as a run through the buildsystem.  Doing
these automatically is difficult at best.  Plus, it can be a good excuse
to go through the open bugs and hit any simple stupid low hanging

> > > ## CVS convergence
> > > 
> > > Right now translations are done on `i18n.redhat.com`. This requires contributors
> > > to have one account on the Fedora Account System (FAS) and a different
> > > one for translations. With the merge of Core and Extras, now is a good
> > > point to get rid of this distinction.
> > > 
> > > The plan is to move all PO files on Fedora infrastructure under a new
> > > CVS group (cvsl10n) [3]. An email will be sent to all translators to create a
> > > FAS account if they don't have one and join the cvs group. Members of the L10n
> > > team and ambassadors will help with this process.
> > > 
> > >   [3]: http://fedoraproject.org/wiki/L10N/Projects/CVSInfrastructure
> > 
> > Does this also include moving the actual source that's hosted on
> > elvis/i18n?  If not, then I have very strong concerns...  separating the
> > source code from the translations has a lot of downsides as it requires
> > a manual sync between the two.  And these never work well :(
> Sorry for my ignorance, but which source?  The PO files?  Or something
> more?

More.  All of the source for anaconda, pirut and all[1] of the apps
being translated here are on elvis.redhat.com also.  In the exact same
source repository.  
  cvs -d:pserver:anonymous elvis redhat com:/usr/local/CVS co anaconda

Look in the po dir.  Then, check out the translate directory.  Hey, all
the po files of all the modules on elvis in all the languages.  This is
purely done through a (ugly as sin) CVSROOT/modules file.

> The goal here is to stop using elvis.rh.c for the Fedora Translation
> project.  If Red Hat's l10n team needs elvis for their work, then they
> need to work out how to sync back from cvs.fedoraproject.org.

If we stop using elvis for Fedora Translations, then how are we
intending to actually provide the translations to the sources on elvis?

> To state it more clearly, we are trying to move the PO files to the
> source code (in cvs.fedoraproject.org).  Your comment makes it sound
> like the PO is already with the source?

It *IS* for the majority of stuff on elvis


[1] With the exception of some things like up2date and a few other weird

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]