+Ryan who's been writing the Pootle FS code.
I'm a +1 for repository is King. On the Pootle side our old VCS code did
the same. The logic for us is that VCS interaction doesn't need to know
that tools hang off of the content. But we convert to suggestions so there
is no data loss. The user simply resolves the suggestion which should in
most cases simply be factoring the VCS change into the suggestion. The
translators will always be the best at resolving things (even though they
might mess up and revert the VCS change) as they can read the language, but
we use the VCS translation until that is resolved by the localisers.
We expect such conflicts to be small especially in a case where the two are
synchronised regularly. To be clear its only a conflict if both sides
change so even in a major technical edit, as long as it happens quickly
after a sync I wouldn't expect major issues.
Our other potentail area of conflict is the arrival of new files on both
sides. Our current approach is to decide who ha authority, VCS in most
cases, though we can set it for Pootle to win. I'm not 100% sure what we
do when they've both arrived and there are translations present in each of
these new files.
--
Dwayne
*Translate*
+27 12 460 1095 (work)