Introduce "Forbidden target terms" QA check

Current behavior:
The "Forbidden terms" QA check returns a warning if a forbidden term is inserted in target, even when the equivalent source term is not present.

Requested behavior:
Add a QA check option like "Forbidden target term" that displays a warning when a forbidden term is present in target and the equivalent term is present in source.

Use case:
Sometimes terms are not forbidden for any use case, but only if used as a translation variant for a specific source term. Therefore, if the source term is not present, the term may be accepted. 



1 comment

  • As far as I understand, this can be done with a custom QA check (the one that is based on a regular expression).


Please sign in to leave a comment.