[zanata-bugs] [Bug 873489] New: XLIFF strategy should use source and target elements for safety

[bugzilla at redhat.com]

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

            Bug ID: 873489
        QA Contact: dchen at redhat.com
          Severity: unspecified
           Version: unspecified
          Priority: unspecified
                CC: zanata-bugs at redhat.com
          Assignee: runab at redhat.com
           Summary: XLIFF strategy should use source and target elements
                    for safety
        Regression: ---
      Story Points: ---
    Classification: Community
                OS: Unspecified
          Reporter: sflaniga at redhat.com
              Type: Bug
     Documentation: ---
          Hardware: Unspecified
        Mount Type: ---
            Status: NEW
         Component: Component-Maven
           Product: Zanata

Description of problem:

When pushing XLIFF content, it is possible for the translation files to have
older source strings than the source files, but with the same trans-unit ids. 
For instance:

source file:
...
<trans-unit id="greeting">
  <source>Hello World</source>
</trans-unit>
...

trans file:
...
<trans-unit id="greeting">
  <source>Hello</source>
  <target>Hallo</target>
</trans-unit>
...

NB: even though the ids match, "Hallo" is not a valid translation of the
current source "Hello World".


Version-Release number of selected component (if applicable):
2.0.0

How reproducible:
100%

Steps to Reproduce:
1. Push both files above
2. Pull the translation

Actual results:
greeting has the incorrect translation "Hallo"

Expected results:
greeting should be untranslated

Additional info:

We may need to change the way we generate resIds for XLIFF files, to be similar
to the Gettext approach, so that the server will reject the outdated
translation.  If so, we will need a migration path for existing content in the
database.

Alternatively the client may be able to load source and target files and
compare the source element.  We will need to weigh both approaches.

We have a similar problem for Properties files.

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