Denis Roy schreef:
> Thanks for your feedback on this. I think we've come up with a
> reasonable approach:
> - syncup needs to run under its own ID. All of syncup's translations
> need to be marked as fuzzy. I've opened http://bugs.eclipse.org/255798
> to track that effort.
> - For Large contributions, we (the Babel team) will ask the contributors
> whether or not the translations they are donating were done by
> professional translators *and were tested/reviewed in context. *If the
> contributions are professionally authored, tested and reviewed (such as
> IBM's 3.2 lang pack donation), then they will be considered
> authoritative and they will overwrite whatever the current values are in
> the database, and none of the incoming translations will be marked as fuzzy.
> If the contribution is a professional effort but it has not been tested
> and reviewed in context (such as the Adobe contribution), option #3
> below will be invoked, and as Hendrik has suggested, the 'conflicts'
> will be flagged as fuzzy, allowing translators to revert and/or confirm
> the translation.
> *I have updated our import process docs with this new information:
> http://wiki.eclipse.org/Babel_/_Large_Contribution_Import_Pr ocess