> I already see the answer from Cédric ("But you should check when we > do the codereview") : It doesn't work, it's already too difficult > to read all the reviews and think about the code. Moreover when > reading code bit by bit it's impossible to find inconsistencies > across files/modules. > > So IMO we should have two round of translation, a first one to do > most of the translations, spot the problems and talk about it > together. And a second one after the code freeze to finalize the > work.Your first round has nothing to do with translation but it is just plain development.IMO it is not, but I'm knit-picking.
It's another kind of contribution, but I don't see why those contributions should be done in a very specific time span. Moreover if the term is not precisely defined in the translation from the start it might be a sign that something has not been considered earlier.
So fell free to make a review when you want and solve all those issues.This is what I want to avoid. "when you want" means it will never be done.
I think translators should care enough about their work so that "when you want" means once or twice a month ;). But I understand that for non tech savvy users uploading a codereview is already a huge difficulty (even our GSOC students have difficulties with that and they are doing a MS in CS). Cédric proposed transiflex, I think that it should be tested. -- Nicolas Évrard B2CK SPRL rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 E-mail/Jabber: [email protected] Website: http://www.b2ck.com/
signature.asc
Description: Digital signature
