The sooner the translator do their job, the sooner the .po file will be ready, testable and thus the sooner the people will get the opportunity to correct and fix the translations.Don't care. Do that somewhere else than in the main repository. Again, pushing for testing is *wrong* and it is not what we do for everything else so why doing it for that?
Of course this process should happen somewhere else then the main repository. Wasn't it the reason you proposed transiflex?
>Nobody translates a book when the writer is writing it! In the peculiar process we're using, it would not happen this way since there is the codereview process which ensure that a full bunch of strings get in the main tree all together at once.There are never codereview for translations. And according to the codereview rate, I'm pretty sure it will be useless to try to do it.
I was not speaking about codereviews for translations (in fact in my previous email I even said that it was probably not something suited for the translators). I meant that new English phrases land/change by batch in the main tree. So the development is not incremental but rather progress by steps. And thus the book metaphor is not suited. -- 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
