Red Hat Bugzilla – Bug 873930
Properties/XLIFF strategies should check source content when pushing
Last modified: 2013-12-11 23:00:41 EST
Description of problem:
When pushing translated content in Properties projects, we don't check whether the client's source files are up to date.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Push source v1:
2. Push source v2:
3. Revert source v2 to v1, and push trans v1:
"Hallo" is accepted as a translation of "Hello World". (It is actually a translation of source v1, "Hello".)
"Hallo Welt" is rejected by the server because the latest version of greeting is "Hello World", not "Hello".
See also bug 873500.
I think we can solve this by allowing the client to push a hash of the source content as an optional property of the TextFlowTarget DTO. If it is provided, the server can check this against the HTextFlow's contentHash, and decide whether to accept the translation or reject it.
*** This bug has been marked as a duplicate of bug 873489 ***