[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: kde 3.1
- To: doc at arabeyes dot org
- Subject: Re: kde 3.1
- From: Isam Bayazidi <bayazidi at arabeyes dot org>
- Date: Tue, 26 Nov 2002 18:28:18 +0200
- User-agent: KMail/1.5
Salam
What exactly Hicham you think we need the branch for ? the current PO files
that we have are for the KDE 3.1 .. the KDE 3.2 will not appear in the KDE
CVS tree for the next 3-4 months .. if not even more ..
The branch we will stay with now is the KDE 3.1 .. and the KDE 3.1.x .. the
3.1.x are bugfixes .. it does not contain new features .. maybe some very few
changes in PO files .. nothing that would cause us to go even more backward
in translation ..
The main fallout happened when we moved from the KDE 3.0.x tree to KDE 3.1
tree .. that move was made in July if I can recall .. in that move hundereds
of new strings arrived, and alot of changes .. at the same time of this bicg
change in the PO files we had the lowest number of translators ever ..
Anyway .. discussion is open ..
Yours
Isam Bayazidi
On Tuesday 26 November 2002 16:25, Mohammed Elzubeir wrote:
> On Tue, Nov 26, 2002 at 04:05:05PM +0200, Isam Bayazidi wrote:
> > On Tuesday 26 November 2002 12:01, Hicham Amaouti wrote:
> > > Hi Isam,
> > > with the KDE release of 3.1, can you please create a branch on cvs so
> > > we can continue the translation of files and not bother with new ones?
> >
> > Salam Hicham ..
> > Well the translation files that we are working on now are the KDE 3.1
> > files.. and we will stay with this branch until at lest next April .. As
> > KDE 3.2 is planned for next June/July ..
> > No need to branch now as not all translators knows how to work with
> > branches in CVS. So what we will do ( as we did with KDE 3.0.x and KDE
> > 3.1 translation) is to stay with one branch until the KDE-i18n
> > coordinators says it is a good time to make a move .. no need to go
> > through the mess or branches ..
> >
> > This is my opinion.. and for sure it is open for discussion ..
>
> Salam,
>
> While I used to agree to the minimum options when it comes to the
> translation, I think we have a big enough base to be able to branch on the
> cvs. I do recommend that we have branches, but specifically request for
> translators to work on one branch or the other (the branches are there, but
> the option on what to work on is only up to the coordinator).
>
> I don't think adding an extra argument to the cvs command will kill anyone
> ;)
>
> later