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.
> > - translation outside the release window
> > This is just WIP commits because the strings are not freezed so it
> > is not needed to run after them.
> > If some translators find they don't have enough time (3-4 weeks)
> > during the release window, they can start (or maintain) outside the
> > main repository an up to date translation as far as it doesn't
> > trouble the history of the main repository.
> > Also we can try to setup a transifex instance on tryton.org if it is
> > needed (need to be patched to remove GNU headers).
> >
> > - improvement during the translation process
> > Some translators try to improve some strings in their translation
> > process. This is bad because it just improves the software for their
> > language and not for everyone, it is the english that should first
> > be improved. So this should be done during the development process.
>
> IMO those two points are linked. From my experience, I see most of the
> errors/inconsistencies during the translation window. As it is too late
> to fix the original strings, I don't do it, then I forget it and the
> strings gets never fixed. This scenario has repeated for each release
> without exception.
>
> 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. So fell free to make a review when you want and solve all
those issues.
--
Cédric Krier
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: [email protected]
Website: http://www.b2ck.com/
pgpCln74GeGjs.pgp
Description: PGP signature
