Pavel Janík napisał(a):
work in the product. As Pavel already mentioned, there are plans to
make more regular L10N merges and builds available. That way a
translator would only have to verify the latest translation changes in
the final L10N CWS for a release.
No - he could verify his translations as soon as they are merged and he
can in fact skip the hurry generated by Sun translation schedule at the
end of the release cycle completely. This is part of the problem as well.
Well, what about QA? I was trying to begin implementing automatic (or
semi-automatic) QA on Polish build (and then on others), as I described
in the wiki. However, I didn't have ANY chance to verify the changes as
I worked using sources, and Vladimir didn't prepare a tarball. I have no
direct access to DB, so I couldn't say it the changes are integrated or
not - I was spell-checking the sdf files...
I was planning to propose that we implement a community-aided automatic
process of checking the translations but now I think the release process
isn't flexible enough. Yet I think early automatic checks are important
because manual checks are done at random. Nobody will read the whole
Help file, for example, to see if there are any typos. So
So my question is: how do we change that?
Best regards,
Marcin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
