OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Inline IDs in <source>/<target> in mtc and ctr modules

So to summarize the problem:

The issue occurs when we have something like the following unit, which is very common: a candidate that has the same inline codes as the source it is based on.

<unit id='u1'>
  <mtc:match id="mtc1" type="mt" ref="#m1">
   <source><pc id='1'>text</pc></source>
   <target><pc id='1'>texte</pc></target>
 <segment id="m1">
  <source><pc id='1'>text</pc></source>

The ID values in the <match> element are not allowed according a strict reading of the current specification, because they are duplicates of the IDs in the main <source> and are not in a <target> sibling of that <source> (See http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html#id)

But if it's not allowed, then it's impossible to carry exact matches in XLIFF2.

The same issue will occur for the Change Tracking handling of inline codes.

This is a rather bad situation.
I don't see how we can resolve it without changing the text of the specification. Any idea on how we can resolve this?


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]