Source and target segment id not match in XLIFF merging
Issue #281
resolved
Original [issue 281](https://code.google.com/p/okapi/issues/detail?id=281) created by @ysavourel on 2012-10-03T16:10:04.000Z:
When merging back an XLIFF document into an original XLIFF document the source and target segment id do not match. This cause a bad source segment id to be in the merged file. See http://tech.groups.yahoo.com/group/okapitools/message/3290
The root cause is probably that the segment id is not ported properly into the extracted resource when filtering the original XLIFF document.
Comments (2)
-
Account Deleted -
Account Deleted - changed status to resolved
Comment [2.](https://code.google.com/p/okapi/issues/detail?id=281#c2) originally posted by @ysavourel on 2012-10-03T16:57:19.000Z:
This issue was closed by revision 86956cc3ca3c.
- Log in to comment
Comment [1.](https://code.google.com/p/okapi/issues/detail?id=281#c1) originally posted by @ysavourel on 2012-10-03T16:47:13.000Z:
The problem was actually in the merger where we are un-segmenting then re-segmenting the container to allow the transfer of the inline codes. The source re-segmentation was not done in some case, so the ID was the one of the joinAll() result.
This should be fixed now. It'll be in the next snapshot