critical internal Tag errors

internal tag errors must be split into "critical" and "non-critical" error. "Critical" errors are those who make it impossible to export a task. Tasks that can not be exported are a real problem in automated environments.

E.g. ConnectWorldserver automatically transfers a task back to Worldserver when its finished. Therefore the task needs to be exported. And if that is not possible the task stays in state "post-processing". In this state the task is not useful to the customer any more.
and this causes support-effort for MittagQI and the customer.

Only proper solution for this is to solve the "root of the problem" which is simply: it should not be possible to save a task with critical tag errors. The the persons who actually is working on a segment has to solve the error before saving.

Maybe it will be possible to have some "helping mechanisms" to solve the problems automatically. E.g if an opening Tag was deleted, but the corresponding closing Tag was NOT deleted, this helper can mark the closing Tag as deleted (by the current customer)