On Mon, May 7, 2012 at 4:08 PM, Cédric Krier <[email protected]> wrote: > Hi, > > I would like to report some issues I faced during the last release: > > - format of the po file > Some have pushed files not generated by the tryton export which means > it was not wrapped correctly. > This is wrong, we must generate files always the same way to minimize > the changeset diff. This is important when you search in the history. > (exception of the client which uses Babel). > > - fuzzy > There was some translations commited with fuzzy attribute. > This is wrong and useless. It just shows that the translation process > is not complete so it is better to not push work in progress. > > - multiple commit on the same file > During the translation window, translators must commit only once the > translation of a module. We don't need to have WIP in the repository. > The repository is not a tool to send WIP files. Again we must have a > clean history and try to reduce the number of changeset on a file. > > - commit during the release > When the date of the release is reached, no commit should be made > (except the one of the release manager). Otherwise it is too complex > work for the release manager. And again the history is not clear. > For now, nothing prevent it, we just trust everyone to respect it. > > - 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). > > - new comers > I got this time a lot of requests for new language. I think it is too > difficult to manage new language during the release window. So new > language should be added during the development window as a start > point and new comers will be refused during the release window > (because we spent too much time on this topic than testing the > release). > > - 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. > > If anyone has suggestion to improve the process, comments are welcome.
I created a long while ago the Transifex[1] project for Tryton and GNU Health. It's a very nice portal and I believe it's the best way to handle it, especially when the number of modules and languages increases. It allows parallel translations and peer reviews. Today is the tool that we're using for GNU Health and I'm quite happy with it. My 2 cents. 1 .- https://www.transifex.net/projects/p/GNU_Health/ > > Thanks, > -- > 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/ -- [email protected] mailing list
