• Medium
    • Provide for PMs the possibility to download the tasks content as spreadsheet containing all segments, with the pre-translated target and the target content after each workflow step.

      It should be possible to export the last edited version of a tasks segments within each workflow step.

      Export format would be XLSX, so the existing XLSX export can be adopted regarding XLSX creation and tag conversion etc.

      First column: Segment number

      Second column: Language Resource resource_id  used for pre-translation (editor_Services_Deepl_1, editor_Services_t5memory_1, etc.)

      Third column: Language Resource name (name given by the PM, when creating the language resource)

      Fourth column: Source

      Fifth column: pre-translated target

      Sixth column: target at end of first workflow step

      Seventh column: target at end of second workflow step

      etc.

       

      Inside of the segments internal tags would simply show up like this
      This <1>is a<2>test</2>, that <3/>serves</1> for demo.

      Download option should be integrated in the export task menu in the GUI.

          [TRANSLATE-2869] Export of editing history of a task

          Thomas Lauria added a comment - - edited

          All implemented apart of the engine field, since there is no common interface to get the engine from the used language resource. As discussed with marcmittag we remove the engine column from the excel - readding is easy but first a generec getEngine must be available on language resource level.

          Thomas Lauria added a comment - - edited All implemented apart of the engine field, since there is no common interface to get the engine from the used language resource. As discussed with marcmittag we remove the engine column from the excel - readding is easy but first a generec getEngine must be available on language resource level.

            tlauria Thomas Lauria
            marcmittag Marc Mittag [Administrator]
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: