A new functionality should be introduced, that allows updating an existing task

Details of the import

Pre-conditions regarding file formats

This feature should work with xliff 1.2 files, if xliff 1.2 had been the bilingual file format on creation of the task.

If it is only little additional more effort (or none) the same should be possible for other bilingual file formats.

Yet every task should only be updateable with the bilingual file format, it was created with.

For not native importable file formats (Okapi is used) the update is currently not possible. This may change after implementing splitting and merging (TRANSLATE-1387).

TODO tlauria : Fix that empty source with filled target may be imported (without MRKs, plain source plain target).

TODO aleksandar  What does language resources do with empty source content? Did Axel fix only for OpenTM2 or for all language resources?

How updating of segments works

The import runs as usual, yet no new task is created, but the old one is updated.

The target of the trans-unit will update the target of the segment in translate5 and the source will update the source of the segment.

Even if the target in translate5 is filled, yet in the xliff it is empty, the target in translate5 will be updated with the empty string.

When updating

• matching of segments is done by trans-unit ID and mid if the trans-unit is segmented
  • If no segment can be found, that matches the ID, an error is logged to the task log
• only those segments are updated, where the source differs OR where the target in the xliff is NOT empty and differs
• A special handling for Adobe Captative is needed (only source tag, export as <de> stuff...)
  • If the source of a trans-unit is empty in the xliff the target is still updated
    • if it differs to the previous content
• if segments are updated, the same happens, as if the acting project manager would edit the source or the target in the interface (concerning segment history, last editor, etc.). This should be analogous to the Excel reimport.
• The process status is set to "not translated", if the target in the xliff is empty. Else it is set to "pm edited".
• Trackchanges is only done in the target (not supported for source editing so far). The same serverside  TrackChanges algorithm as for the Excel reimport is used.

Integration in the GUI

• Create a new task property tab which lists the file tree. The implementation of that new tab must be booked on TRANSLATE-2298.
• Each listed file must be selectable
• if a file is selected, the "file replace button" above the treegrid must be enabled. If disabled, a tooltip should explain why (missing file selection).
• clicking on the file replace button should provide a small upload window (similar to the excel re-import).
  • the dialogue allows to select a file (same file type as the selected file)
  • contains a checkbox which decide if the new source and/or target content of an updated segment should be saved into the already attached TMs (if any)

• • the checkbox should not be checked by default (see below) and have the label
    • EN: Save all segments to TM
    • DE: Alle Segmente ins TM speichern
  • The checkbox label contains an info icon with a tooltip with the message
    • EN: Saving all segments of the task in associated writable TMs after updating the task.
    • DE: Speichern aller Segmente der Aufgabe in die zugehörigen beschreibbaren TMs nach Aktualisierung der Aufgabe
  • the default of the checkbox is off. Yet the default value can be configured on instance level and overwritten on client-level

Idea of technical realisation

• new task controller action or new file controller putAction?
• the above action triggers an ordinary import (similar excel re-import, similar pivot file import) of the uploaded single file just with a different, new segment processor (similar to the excel re-import) which updates then the segment
• the exchanged file should also get as additional file into the task archive.zip