[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: KDE 4.2 / KDE 4.3 translations
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2009-06-24 15:31:18
Message-ID: 200906241731.20006.aacid () kde ! org
[Download RAW message or body]

A Dimecres, 24 de juny de 2009, Martin Schlander va escriure:
> Onsdag den 24. juni 2009 15:53:47 skrev Albert Astals Cid:
> > A Dimecres, 24 de juny de 2009, Martin Schlander va escriure:
> > > Onsdag den 24. juni 2009 15:19:37 skrev Albert Astals Cid:
> > > > A Dimecres, 24 de juny de 2009, Martin Schlander va escriure:
> > > > > Just confuses me a bit, cuz for 4.2 you guys fixed the scripts so
> > > > > translators weren't affected by the branching at all, and we
> > > > > continued translating in trunk, despite kde 4.2 having been
> > > > > branched.
> > > >
> > > > Not true, 4.2 was translated in the stable branch, if you were
> > > > translating trunk you were translating for 4.3 and not for 4.2.x
> > >
> > > http://lists.kde.org/?l=kde-i18n-doc&m=123117056213328&w=2
> >
> > It says KDE 4.2.0 there not the whole KDE 4.2.x live
>
> Yes. My concern was also just the timespan between branching and tagging of
> 4.3.0 - i.e. the next 4 weeks or so.
>
> > For KDE 4.2.x we had http://lists.kde.org/?l=kde-i18n-
> > doc&m=123303520320858&w=2
> >
> > This time we've just made the branching the translations happen at the
> > same time of the code since it makes more sense.
>
> Not from my perspective ;-)
>
> This means:
>
> a) we have to switch branch in the middle of a hectic translation round -
> which likely leads to some confusion, especially for "normal" translators,
> but also to some degree for coordinators I'll expect.
>
> b) I have to do some work to move translations done in Stable between now
> and release, to Trunk. Or I have to make Lokalize manage two branches at
> once, which is still a bit more work and an increase in complexity.
>
> So I'd prefer the way it was handled for the 4.2.0 release, which was
> extremely fluent and non-bumpy from a translator point of view. But
> obviously I have little or no clue how things look from your end - you
> should do what you think is best.

Yeah i agree this can cause some confusion to translators, but in my opinion 
it's much more confusing architecture wise to have trunk translations using 
stable code.

What do others think? Do you prefer delaying branching of translations after 
the release is done (confusing because trunk translation is for stable code) 
or do you prefer branching at the same time (brings a switch in a "heavy" work 
time)

Albert

[prev in list] [next in list] [prev in thread] [next in thread]