Hi Andrea,
the development nearly stopped on the OOO330 code line. It does not make
sense to use this code line as there will be no further milestones. And
it is planed to integrate the l10n as well.
We should use the DEV300 now and as soon as the OOO340 code line opens
we go onto this.
Cheers,
Ivo
Andrea Pescetti wrote:
On 09/12/2010 Ivo Hinkelmann ha scritto:
I am happy to announce that soon the localization process will be
changed into a continuous process which will allow to provide l10n
turnarounds cycles at every milestone.
Nice, it's a very promising development!
Out of curiosity: I see it is now meant to provide updates on the DEV300
codeline; could a (much simplified) version of it be used to deliver
updates to language packs for the current (OOO330) codeline?
I would see it as a convenient option for post-release localization
fixes; the latest version of OOo, 3.2.1, has been out for more than six
months, and we wondered if there could be a way to update (meaning: fix)
some Italian strings in this timeframe through a specific language pack.
It seems that a subset of the new process could allow something like
this. The main issue I see is with English strings that get removed from
the DEV300 codeline: if they get removed from Pootle too, then this
would require extra care.
Regards,
Andrea Pescetti - Italian N-L Project Lead.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
