Le 02/10/2014 09:32, Michele Calgaro a écrit :
Once a team
has a team leader the team leader can control the team members leaving the developer with
simply
uploading the pot files and downloading the translated po files in a timely manner (once
a week /month or so) and
merging them into the source packages as they would do anyway.
Ah ah! I was
replying to this comment when I suddenly realized that my original thinking was at fault.
The translated .po files do not need to be *patched* to GIT, they can just be *copied*
over the older copies when new versions are submitted. This does not require any
"manual patching work" and can be achieved quite quickly even by few
developers.
In this view, daily updates would work fine.
Given the development rate, I still think that daily updates (or even weekly) would be
overkill, since most of the time only the date of generation would change and nothing
else. Probably by-weekly or monthly is a good choice.
Cheers
Michele
I've already had a problem using translation patches today.
I used kbabel yesterday to update missing/fuzzy translations in french
tde-i18n.
Then I created a big patch file that I intended to submit today.
But today, the tde-i18n package has been updated in GIT, and my patch no
longer applies correctly.
I've seen 2 main causes:
- The header of ".po" file contains a "build date" that can change at
every update
- a single new "msgid/msgstr" in a large list can cause a big chunk of
patch file to fail
So I agree, we should not proceed using patches for translation files.
Then, how can we do ?
Do we open a bug report to collect all ".po" files ?
Still, I wonder, if I update the .po files that I've downloaded today,
then I submit them tommorrow...
if the git tde-i18n is automatically updated during that time, will
pushing my file to Git cause a loss of the automatic updates ?
Also, since the automatic .po files update is in place, there are MANY
fuzzy translations for the new strings.
This can cause lots of misunderstanding for people using tde-i18n !
Having bad translations is even worse than no translation at all, IMO.
Now if every language has got lots of fuzzy translations as french
language did, we need to fix this ASAP.
It is important that non-developper can help us !
François