SDLXLIFF

For SDLXLIFF currently all translated 100%-Matches are locked, when the PM selects on import time "lock 100% matches". This is wrong according to what makes sense regarding workflow needs.

If a translator edited an 100%-Match, it should still be editable for the reviewer in translate5, even if the PM wants non-edited 100% matches be locked.

Therefore the import option must be changed from 

"lock 100% matches"

to

"lock non-edited 100% matches".

And the import behaviour must be changed accordingly. Implementation details see below.

XLIFF 1.2

For SDLXLIFF the source of a translation is recorded in the attribute "state-qualifier" of the target tag. 

If the PM selects "lock non-edited 100% matches" translate5 should therefore lock all segments, where the "state-qualifier" is set to one of the following values:

• exact-match
• id-match
• leveraged-glossary
• leveraged-inherited
• leveraged-repository
• leveraged-tm

Documentation

The above behaviour needs to be reflected in translate5 confluence.

Implementation details for SDLXLIFF

SDLXLIFF does not care for xliff standards, but implements its own logic in its own namespace for the above behaviour.

Therefore the xliff 1.2  standards described above can not be used.

For SDLXLIFF in addition to the current behaviour translate5 must take the "origin"-attribute of the sdl:seg tag of the current segment into account to decide, if the segment should be locked for the "lock non-edited 100% matches" switch. If its value is "interactive" the segment should NOT be locked, in other cases it should. This check is in addition to the current logic for checking, if a 100% match should be locked - this logic stays as it is.