[zanata-bugs] [Bug 873930] New: Properties/XLIFF strategies should check source content when pushing

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=873930

            Bug ID: 873930
        QA Contact: dchen at redhat.com
          Severity: unspecified
           Version: unspecified
          Priority: unspecified
                CC: zanata-bugs at redhat.com
          Assignee: runab at redhat.com
           Summary: Properties/XLIFF strategies should check source
                    content when pushing
        Regression: ---
      Story Points: ---
    Classification: Community
                OS: Unspecified
          Reporter: sflaniga at redhat.com
              Type: Bug
     Documentation: ---
          Hardware: Unspecified
        Mount Type: ---
            Status: NEW
         Component: Component-Logic
           Product: Zanata

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):
2.0.2

How reproducible:


Steps to Reproduce:
1. Push source v1:
greeting=Hello

2. Push source v2:
greeting=Hello World

3. Revert source v2 to v1, and push trans v1:
greeting=Hallo

Actual results:
"Hallo" is accepted as a translation of "Hello World".  (It is actually a
translation of source v1, "Hello".)

Expected results:
"Hallo Welt" is rejected by the server because the latest version of greeting
is "Hello World", not "Hello".


Additional info:

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.