Wrong Original Targets with XLIFF 2.0

Description

Orginal targets are placed in the wrong segments when Ocelot reads a XLIFF 2.0 file that has a unit element containing more than one segment.

The bug is generated by the Change Tracking module in the unit, having a "revisions" element with the attribute appliesTo set to "target" and no "ref" attribute set. As more than a target exists for that unit, than a random target is picked.

Environment

None

Activity

Show:
Marta Borriello
November 30, 2016, 10:28 AM

Now the "revisions" element has the attribute "ref" pointing to the id of the segment containing the correct target.

Chase Tingley
November 30, 2016, 7:32 PM

Hi Marta,

Did you commit a fix for this? I don't see it in github.

Marta Borriello
December 2, 2016, 9:01 AM

Actually I haven't pushed it yet to the remote repository. I will add a comment as soon as the commit is done.

Marta Borriello
April 4, 2017, 10:46 AM

Fix committed to the dev branch

Fixed

Assignee

Marta Borriello

Reporter

Marta Borriello

Labels

None

Fix versions

Affects versions

Priority

Minor