Problem
Reimported translator packages may have tag-faults (swapped opening/closing internal tags) and may do show incorrect QA.
The diffing strategy and handling of "target at import time" field also is wrong, as a translation task will not be diffed against the edited target but the (empty) target at import time leading to a "everything new" diff

Solution

• Add AutoQA after reimport
• Prevent overwriting the "Target at import time" in all cases
• Always diff against the edited target, not the target at import time
• new target is written to the "target edit" onls
• Changed sources are processed only, if source editing is active. In this case a changed source is written to the "source edit"

Other TODOs
Add warning, that MQM-tags wil be lost when a translator package reimport is applied

Frontend-Tests

• use nextcloud/Developer/test-data/basic import/3-segments-en-de.tbx, nextcloud/Developer/test-data/basic import/3-segments-en-de.zip to test
• import a task (with editable sources), assign termcollection & pretranslate the task (TrackChanges should be enabled)
• download translator package
• unpack it, change segments & source-segments (Hint: <seg-source>)
• pack it (same structure as import) reimport translator package
• check, if terminology is still applied & trackchanges properly set
• check editable sources