No validation between codes with same id in source and target

[YvesS]

When one code in target has the same id as one code in source, they must be "corresponding" codes. But we do not validate this because "corresponding" has no associated constraints in the specification.

As a result something like <pc id='1' canCopy='no'> in source with <pc id='1' canCopy='no'> in target is seen as valid. But it is wrong in the spirit of the specification.

Note that not all codes must be the same, for example dataRef could have different values, but would need to point to <data> elements with identical content. And even that is possibly not quite true, as mixed representation is allowed, and one code in source could use dataRef while the corresponding code in target could not have dataRef.

Initial thread is here: https://lists.oasis-open.org/archives/xliff/201506/msg00028.html

[YvesS]

Added check for source/target corresponding codes (see issue #2). This does not check for data, dataDir, dir, value and ref as all may change for the target.

→ <<cset 464ff85ba5d0>>

[YvesS]

subType is another value we do not check as it may be changed in the target if the data is changed.

[YvesS]

This is resolved. The fix will be in the new master branch as well as in the new dev branch. A new 1.0.1 version will be release with this fix and a couple of others.

[YvesS]

Re-opening this issue. We are probably checking more than we should. See https://lists.oasis-open.org/archives/xliff/201506/msg00038.html

[YvesS]

Changed the verification for code correspondence to only the tag-type. See https://lists.oasis-open.org/archives/xliff/201506/msg00038.html for details. This resolves issue #2.

→ <<cset 1474242ecf1a>>