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.
Now the "revisions" element has the attribute "ref" pointing to the id of the segment containing the correct target.
Did you commit a fix for this? I don't see it in github.
Actually I haven't pushed it yet to the remote repository. I will add a comment as soon as the commit is done.
Fix committed to the dev branch