Re: Imminent release of 2.6.0

Points 3 through 5 are obvious enough, but how do I
A) check if a .po is correct?
B) determine if it is for STABLE or TRUNK?

Once that's solved, I'll do the translation stuff from now on.

Marc

On Fri, 2008-03-14 at 18:59 +0100, J.M. Maurer wrote:
> On Fri, 2008-03-14 at 18:52 +0100, Marc "Foddex" Oude Kotte wrote:
> > Is this is a mere matter of copying a single file in a translation
> > directory somewhere, and committing it? If that's the case, I'd be happy
> > to become the 'translation maintainer' for Abiword as it seems uwog is
> > occupied enough with other Abiword-related matters.
>
> The general procedure is (for existing translations, new ones require
> code changes):
>
> - Check that the .po is correct
> - Determine if it is for STABLE or TRUNK
> - Copy the .po file to $srcdir/po
> - run ./ui-backport nl_NL (or whatever the lang code is)
> - Commit the po file and the generated .strings file
>
> Cheers,
> Marc
>
>
> > Marc
> >
> >
> >
> > On Fri, 2008-03-14 at 17:27 +0100, J.M. Maurer wrote:
> > > > The thing is, while these PO files are waiting in the queue, other
> > > > people might notice that the translations in SVN are incomplete,
> > > > grab the latest PO file, and do the same work again -- all for
> > > > nothing. This may not have happened yet, but... it is painful when
> > > > it does. So for the past weeks you have had six, seven translators
> > > > hopping on their chairs, muttering at their screens: "Come on!
> > > > Come on! Put it in!"
> > > >
> > > > In short: submitted PO files should, in my opinion, be merged to SVN
> > > > as soon as possible after their arrival.
> > >
> > > I totally agree. I'd appreciate if some "translation maintainer" would
> > > show up to handle the task in the future, so we can guarantee timely
> > > commits.
> > >
> > > Marc
> > >
> >
>
Received on Fri Mar 14 19:03:46 2008