Hi Sophie,
sophie schrieb:
Make those cws build by buildbots and merge those small cws in a final
one called localizationxx?
Ivo is working on a semi-automated process to build l10n CWSs, so that
such CWSs might be created more often than at the time. Btw., for this
goal it is not necessary to put data into Pootle from CWSs that are not
yet nominated.
Thanks to Ivo :) I've read your second mail about Integrated instead of
Nominated, why isn't it necessary, the cws won't content further changes?
What I meant is that for the semi-automatic process of creating l10n
CWSs, which Ivo is working on, it is sufficient to work with the
integrated strings just as we do now.
The picture is that news string (more or less) continuously get into the
code with every integrated CWS. At the same time the strings from the
integrated CWSs get imported into Pootle, get translated and
automatically get exported onto an ftp server, where the process can
grab them and put them onto an l10n CWS. These l10n CWSs get created and
integrated more often than now, so that we have less strings per l10n
CWS, get earlier feedback for the translation teams about the results of
their work and also have less strings to translate with the final l10n
CWS for a new major/minor release.
For what I described above it is not necessary to work with CWS that are
not already integrated i.e. nominated, approved by QA etc. It would be
possible but IMHO it would either not help much (in case of nominated
CWSs, where the time advantage before integration might not be worth the
effort) or might even pose some risks (in case of e.g. not yet approved
CWSs, where the strings might change later in the process and we might
trigger translations that would need to be corrected later).
I hope this clarifies what I meant to say :-).
Regards,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: dev-h...@l10n.openoffice.org
