The example above is invalid with the current XLIFF specification because <sc id="1" ...> in seg1 is not isolated="yes" although it does not have the corresponding <ec> element in seg2. The specification should be updated to clarify the constraint:
This constraint always applies to <source> values in a <unit>.
For values, this constraint is effective when all <segment>s in a <unit> have <target> elements.
Example Use Case
N/A
Compatibility Impacts
This specification update should have very small or no impacts to existing XLIFF applications.
Authors
Yoshito Umaoka
Area of Changes
Detailed Description
In XLIFF 2.1 specification 4.2.3.4 sc, there is a constraint statement below:
The attribute isolated MUST be set to yes if and only if the element corresponding to this start marker is not in the same , and set to no otherwise.
This constraint makes perfect sense for
<source>
part . However, in translation process, not all<target>
values might not be ready at a point.The example above is invalid with the current XLIFF specification because
<sc id="1" ...>
inseg1
is notisolated="yes"
although it does not have the corresponding<ec>
element inseg2
. The specification should be updated to clarify the constraint:<source>
values in a<unit>
.<segment>
s in a<unit>
have<target>
elements.Example Use Case
N/A
Compatibility Impacts
This specification update should have very small or no impacts to existing XLIFF applications.