With runtimeOptions.termTagger.markTransFoundLegacy = 0 this error messages should NOT appear anymore.
We discovered two cases in which this error happened again:

• First case: one term occurs in source more times that in target. Then markTransFound marks the difference in Source red. The method throwing above error can not handle this behavior, so it handles this as error.
  → The logging method should be also to be able to count terms in source and target.

• Second Case: if in source and target there are two synonyms out of the same termentry (which is indeed a valid scenario) then one of the synonyms in source is marked red, which is wrong. This should also be corrected.