Le Mon, 7 May 2012 23:01:59 +0200, Cédric Krier <[email protected]> a écrit :
> On 07/05/12 22:16 +0200, Bertrand Chenal wrote: > > Le Mon, 7 May 2012 21:08:45 +0200, > > Cédric Krier <[email protected]> a écrit : > > > > > Hi, > > > > > > I would like to report some issues I faced during the last > > > release: > > > > > > - format of the po file > > [...] > > > - fuzzy > > [...] > > > - multiple commit on the same file > > [...] > > > > All of this is solved by simply putting a Tryton server online, > > every translation team can/must use it to translate strings. When > > the release must be done, we just have to run the script that dumps > > all the *po files. > > That will not work. We need responsible that takes care. Take care of what? How is it less careful than the current way of doing stuff? And moreover, if Tryton cannot handle this kind of stuff I don't see how it can be useful for any other application. > > 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. > 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. -- Bertrand Chenal B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Email: [email protected] Website: http://www.b2ck.com/ -- [email protected] mailing list
