On 24/03/13 12:53 +0100, Mathias Behrle wrote: > There are several issues: > > 1) Translation seems to be for you a task completely separated from > development. It is not. Translation also has to grow with the development > and use of an application. It is not just a thing to be done at the end.
I strongly disagree. As it was defined since day 1, it is up to any translator leader to organize the work. The only constraint is that it should not be merged in the main branch before the repositories freeze. I know that the Spanish translators has already started before the freeze but they don't push it yet. > 2) The load of string fixing is thus completely up to the translators. They > are > according to your guidelines the only ones to see the translation until the > end of the string fixing period. Completly wrong: http://hg.tryton.org/modules/project_plan/rev/16470dfa3939 And if you talk about typo in your translations, up to you to build a team to review your work. > I proposed before long time and I am doing it again to have a complete > review > of strings in Tryton with the help of a native speaker *at the beginning* > of > a release cycle, not at the end. You can propose. Tryton is a community project, people have their own objective. So if you want to review strings, do it, submit review/patches. And don't say it is impossible, Albert did this great job for all the error messages: http://codereview.tryton.org/371002 > 3) If there is a real bug in translation (sorry, it can happen like any other > bug in the code) the translator must not only have the approval to push the > fix, but he merely is in charge to fix those bugs. I realy don't understand what you are saying. Everyone is in charge of fixing bugs, the bugtracker is opened to anyone but indeed not so much people get involved. > 4) You are counting with the presence of translators in the "allowed" > pushing period, which is way to optimistic. Release dates are fixed since the begining and thus the translation window. When accepting the charge of translating, the translator knew about it so he can schedule the job for years in advance. But if for some reason he can not, of course he is free to delegate, resign etc. We just consider people are responsible to take action on time. > > And don't forget that countries and currencies are already up to date. > > BTW: How should translators or anyone else check the accuracy of those > translations, if they are not pushed? It is nice to rely on iso-codes, but > better would be the chance to be able to contribute and correct them just > in case of bugs in this package. If you care about such translations, fix it with upstream, just like Pilou did: https://bugs.tryton.org/msg11403 https://alioth.debian.org/tracker/index.php?func=detail&aid=313749 -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: cedric.kr...@b2ck.com Website: http://www.b2ck.com/
pgp11qN5AaB9Z.pgp
Description: PGP signature
