A Dilluns, 7 de maig de 2012 22:16:15, Bertrand Chenal va escriure:
> > - 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.
Another problem is the fact that translations cannot be updated after release.
I understand the reason (no database update within minor releases) but I think
it's something it would be nice to solve in a way or another in the future.
--
Albert Cervera i Areny
http://www.NaN-tic.com
Tel: +34 93 553 18 03
http://twitter.com/albertnan
http://www.nan-tic.com/blog
--
[email protected] mailing list
