problem

If a PM creates a task where source language and target language are equal (for example source de and target de) and this task should use terminology with termtagger, this leads to hanging termtagger instances. They use 100% CPU and do nothing anymore.

solution

prevent termtagger usage in that case and inform the user by putting a warning in the task log.

additional todo

• Currently it is unclear if that happens too with languages differing in the sublanguage. So source = en-gb and target en-us must be tested too!
• Search Jira for duplicates of this issue, we had that error some time ago and I thought that I created an issue about it, but I could not find it