General idea

The idea is, that a translator is able to download a zip package, that includes everything he needs to translate a job outside of translate5 and afterwards update the task with it.

Download of translator package

Location should be an additional entry in the export menu of the task.

Menu entry text should be:

EN: Export translator package

DE: Übersetzerpaket herunterladen

Analogous to the Excel export the task should be locked for editing, if it is exported as a translator package.

The translator package should contain:

• One subfolder: "xliff". It contains the same folder structure and the same files,  as it would be usually the case in a normal translate5 export. Except that only the xlf or xliff files are contained. In the case that the task contains some or only other bilingual file formats than xlf/xliff (so sdlxliff or Transit or bilingual CSV), the export will immediately abort and show a pop-up with a warning message and an "ok" button.
  Message:
  EN: Task contains bilingual file formats, that are currently not supported for a translator package (e. g. sdlxliff, Transit, bilingual CSV). Package creation aborted.
  DE: Aufgabe enthält zweisprachige Dateiformate, die derzeit für ein Übersetzerpaket nicht unterstützt werden (z. B. sdlxliff, Transit, zweisprachige CSV). Die Paketerstellung wurde abgebrochen.
• One subfolder "tmx". It contains one tmx file for every TM language resource, that is assigned to the task
• One subfolder "tbx". It contains one tbx file for every TermCollection, that is assigned to the task.
• One subfolder "reference". It contains the same folder structure, as it might have been in the reference folder of a usual import zip with all reference files of the task
• Visual: in case the task contains visual pdf's, place them in the reference folder withing 'visual' sub folder

The export should open in a new browser tab and analogous to Pavels Excel TBX-export the export should show a progress for the creation of the translator package and start the download, once it is created. Or alternatively start the download immidiately, even though the different components must first be created on the disk and the zip must first be packed and make the browser wait for the download to finish. Yet probably this is not a good approach as for a large task with large memories and TermCollections this could take a while. It makes sense for the TMX and TBX and xliff exports to run in separate workers.

Re-import

Analogous to the Excel re-import there should be a menu entry "Re-import translator package". DE: Übersetzerpaket re-importieren

The expected file structure in the imported zip should be the same, as in the export zip file.

Evaluated will be only the bilingual files in the xliff folder. The file matching will be made via folder structure and file name.

If a file is missing or there is an additional file in the xliff folder, that is not contained in the task, the date will be collected during the import process and logged in the event log with a warning.

Changes to current tab "Update files"

The tab should be renamed to:

EN: Manage files

DE: Dateien verwalten

3 sub-tabs should be introduced:

1. EN: Source files DE: Ausgangsdateien
   => This tab should only be present, if there are source files converted with Okapi to xlf
2. EN: Bilingual files DE: Bilinguale Dateien
3. EN: Reference files DE: Referenzdateien

Each tab will contain a grid to manage the files  For "source files" and "reference files" this will be implemented with https://jira.translate5.net/browse/TRANSLATE-2298. Currently these tabs will stay empty with the message "will be implemented with a following release".

In the "Bilingual files tab there should be 2 buttons above the grid

• EN: Export translator package DE: Übersetzerpaket herunterladen

• EN: Re-import translator package DE: Übersetzerpaket re-importieren

Below the buttons the info message will be shown:

EN: Target segment contents changed outside translate5 are visible as tracked change marks in the segment after re-import. Change marks in segments from before the re-import are lost. Changed source segments are also updated. Newly added segments (e. g. from a segment split) will be ignored. Currently the following bilingual files can be updated: xliff, xlf

DE: Außerhalb von translate5 geänderte Ziel-Segmentinhalte sind nach dem Re-Import als Änderungsmarkierungen im Segment zu sehen. Änderungsmarkierungen in Segmenten von bevor dem Re-Import gehen verloren.  Geänderte Quellsegmente werden ebenfalls aktualisiert. Neu hinzugefügte Segmente (z. B. durch einen Segment-Split) werden ignoriert. Derzeit können die folgenden bilingualen Dateien aktualisiert werden: xliff, xlf

Below this message is a grid that list all bilingual files in the folder structure of the import (as the current update files grid).