Problem

In some cases it is necessary to omit a content protection tag, because the language requires it.

In such cases translate5 also needs to remove the tag from the source, when the segment is saved to the TM, because

• when re-using the segment we match also segments with other numbers of the same type
• if the tag is not present in the target, we are not able to recreate the correct number on task export

Now the problem: If a tag of a protection type was removed, where more than 1 of that type exist in the segment, translate5 does not know, which tag is the one, that should be removed in the source.

Also so far it is not possible for a user to remove tags (if the removal of normal tags is disallowed, what it is by default), because content protection tags are in the same category as normal tags.

Solution

Handling of missing content protection  tags

A new AutoQA tag error category "Content protection errors" is introduced. With 1 error types:

• Missing content protection tag

Of course they can also be set to false positive.

If a segment is tried to be saved with a missing content protection tag, a pop-up appears, that 

• Has the title: "Content protection tag errors" / "Content protection Tag-Fehler"
• If there are missing tags
  • Has a table with a list of all missing in the first column
  • In the second column (column header "Confirm" / "Bestätigen) a checkbox
  • If there are more than on tag of that content protection rule type beneath the tag the source sentence is displayed and tags of that rule type are highlighted. In that case above the table the sentence is displayed: "Where source segment is displayed please select the tag to remove".
  • A click on the tag also automatically checks the confirmation checkbox for that tag
  • I the footer of the pop-up there are 1 button:
    • Cancel / Abbrechen
  • If all tag removals are  confirmed,
    • the pop-up is automatically closed and the segment is saved.
    • The selected tags are removed from the source, when saved to the TM. In the source of the segment table the content protection tag stays.

Handling of additional content protection tags

Additional content protection tags are still dis-allowed and can not be present in the segment, when it is saved.

If a user tries that, a pop-up appears analogous to the current pop-up for normal tag errors. But without any possibility to ignore the additional tags and save anyway.