Hi Santiago,
Santiago Bosio wrote:
Martin Hollmichel escribió:
Hi Santiago,
I think it's an good plan to verify localization (and terminology)
as a early as possible.Are there any technical hurdles to import
incremental localization updates from pootle and do frequent builds.
Can this also easily be done for more languages than Spanish ? What
would be your preferred platform for doing this ?
Martin
Hi Martin:
Perhaps somebody from the l10n project can give better technical
background about the workflow on translation and why the process
doesn't admit changes after the localisation CWS has been integrated.
This is something we are aiming to change. See all my posts in the past
requesting feedback and support for a better and easier workflow.
We have been working with Pootle, open language tools, and gsicheck
and, personally, I consider that string translation changes are of the
safest changes that can be introduced (provided that they are checked
and sanitized) without breaking builds or causing problems. And even
when we considered some translation errors as show-stoppers, their
corrections weren't accepted in RC stage, and were delayed to next
bugfix release.
That was after the RC3, so it's very late in the release process. May be
a warning during the RC1 would have left more time.
As I said, we have been doing our own builds, patching the
translations with the latest snapshot from Pootle, converted to OOo
SDF format using po2oo, and gsichecking the resulting file. All of it
can be done automatically, but I see two problems to solve for the "as
early as possible" scenario:
1. Pootle updates are done only after UI and string freeze. Then these
new or modified strings are available for a few weeks to be
translated, before localisation CWS integration, and after that,
usually a two week period to introduce changes before first RC.
Ideally, new or modified strings should be inmediately available on
Pootle to alleviate the translation burden when too many strings were
introduced/modified. Also, I think translation updates must be
accepted in-between RC's when NL project leaders ask to do so, and
next RC built with the last snapshot from Pootle.
This is an ideal world we would be pleased to reach I imagine, but see
the archive of this list, this is not currently possible.
2. Weekly devel builds should be done with the complete set of
language packs, and not only a few of them as it is done currently (I
think they are FR, DE, IT, JA, pt-BR, etc.) as it will give us the
opportunity to check our advance (provided that we have early the
strings to translate on Pootle as I said before).
As Andre explained, this is not for localization purpose, this gives no
advantages over the localization process but may raise i18n issues
earlier if they happen, for the QA process in general.
Regardless of that, on our community we have a specific problem with
our translation: it has a poor overall quality, and this review
process I described on my previous e-mail must be carried out outside
the current translations on Pootle, because if we did otherwise, we
can get as a result a more confusing translation on the next upcoming
releases. So, we still need a local box to do our own builds to test
the revision process until it gets to an acceptable degree of quality
to merge the changes back to Pootle.
Why didn't you react when we had the build including localization to
test in November and before the RC3? An alert here could have help to
review the workflow or dedicate a specific effort to your language.
I don't think that funding one community will help to enhance our process.
I think each NL project had hard time to follow the process because of a
lot of strings, a shorter period to translate them, errors in the files
and a module that was integrated and should not be translated.
Of course we should be able to build our own cws when we feel that we
need to check the work done. But this may be coordinated also to save
resources and let the rest of the group be aware of the progress. We
need to work as a team here with the developer team and the release team.
Kind regards
Sophie
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
