RE: [xliff-inline] Editing operations and spliting segment

[Yves Savourel <ysavourel@enlaso.com>]

Hi Fredrik, all,

It seems we are dealing with two classes of issues here:

a) The uniqueness of IDs for inline codes at the unit level.

b) Changing the order of the target segments.

I believe we have the uniqueness of IDs at the unit level since the start (The fact that the different scopes of the id attribute is not described yet in the spec says how much work is still needed). 

We are already working at the unit level: Inline codes or annotations can span several segments, original data are defined at the unit level, added codes have id unique within the unit, etc.

One way to look at it is that <unit> is a single <segment> initially, so any splitting has to result in unique ids at the unit level afterward since they were unique in the original segment.

As for changing the order of target segments, I agree: it brings some problems, especially with codes re-ordering and difference between codes in source and target when matching. But I think those issues exist anyway when you start applying matches. Your target matches may have different codes than the source already.

Those challenges exist in 1.2 as well where segments can be re-ordered, and id uniqueness is at the trans-unit level since the segments are defined by <mrk> elements. They are not something 2.0 is introducing.

In addition, the alternative (id unique within each segment) brings its own set of issues as well. For example you may have to re-ID some inline codes when joining segments and that would cause problem with merging for the codes without the original data.

Cheers,
-yves