4 Oct
2014
4 Oct
'14
5:35 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
Le 02/10/2014 09:32, Michele Calgaro a écrit :
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
I can shut the automated update back down for now until a solution can be
formalized if that would help. The automated update does not change the
dates unless something else has changed, however as you can see what
usually changes are the source line numbers and nothing else.
I suspect strongly that the translation team is going to have to use the
msgmerge utility when submitting new translations instead of the standard
GIT tools. I'm starting to wonder if instead of allowing direct GIT
access to the i18n tree we may need to have a service acting as middleman,
accepting modified .po files and merging them into the tree.
This is a happy problem; TDE development is happening at a much faster
rate and therefore we need to figure out how to let that continue while
the translation team works. :-)
Finally, should we have a separate i18n mailing list? I can set one up
real fast if desired.
Tim
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iFYEARELAAYFAlQwL9gACgkQLaxZSoRZrGGHzwDgrzo4OgfboCYQSj0CSa17mhr0
vhYvruhk1khx4wDggCPOYxPP1Ri95radA+LGO4bqHkGJGw79LpnGFQ==
=CiIg
-----END PGP SIGNATURE-----