Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-735

Import match-rate-type history

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • None
    • None
    • None

      if there are more than one entry for the match-rate type in sdlxliff, translate5 currently imports the latest

      This means, for an adjusted TM-Match, it displays "interactive" instead of interactive TM-Match.

      We should combine the different types in translate5 as well like this:

      • tm + interactive → "Editierter TM-Match (importiert)* <br><br><br>*Im ursprünglichen Übersetzungswerkzeug außerhalb von translate5 aus einem TM übernommen und dann editiert"
      • mt + interactive → "Editierter MT-Match (importiert)* <br><br><br>*Im ursprünglichen Übersetzungswerkzeug außerhalb von translate5 aus Machine Translation übernommen und dann editiert"
      • source →†’ Source Text initial übernommen
      • source + interactive→ Quelle übernommen & editiert (importiert)* <br><br><br> *Im ursprünglichen Übersetzungswerkzeug außerhalb von translate5 Quelle vom Benutzer übernommen und dann editiert
      • auto-propagated + interactive → Editierte Wiederholung (importiert)* <br><br><br>*Im ursprünglichen Übersetzungswerkzeug außerhalb von translate5 vom Benutzer angepasstes Segment, das automatisch als Wiederholung übernommen und dann editiert wurde (Autopropagation)
      • auto-aligned + interactive → Editiertes Alignment (importiert)*<br><br><br>*Im ursprünglichen Übersetzungswerkzeug außerhalb von translate5 durch ein Alignment erstellte Übersetzung, die dann editiert wurde

        1. translate5 1.png
          translate5 1.png
          25 kB
        2. translate5 2.png
          translate5 2.png
          37 kB

          [TRANSLATE-735] Import match-rate-type history

          Thomas Lauria added a comment -

          Probably solved with TRANSLATE-1643:

          The current implementation there does not read out a full history of TM, just imports the last one.

          1. When the segment was not edited outside it is now with processing state "pretranslated" and the match type contains the Type TM and the name of the last origin.
          2. When the segment was edited outside it looks like this:

           

           

           

          Thomas Lauria added a comment - Probably solved with TRANSLATE-1643 : The current implementation there does not read out a full history of TM, just imports the last one. When the segment was not edited outside it is now with processing state "pretranslated" and the match type contains the Type TM and the name of the last origin. When the segment was edited outside it looks like this:      

          Thomas Lauria added a comment -

          Current Work putted in branches, check diff branch <> master, since work was not complete.
          Created feature branch feature/TRANSLATE-735-import-match-rate-type-history in all submodules.

          Thomas Lauria added a comment - Current Work putted in branches, check diff branch <> master, since work was not complete. Created feature branch feature/ TRANSLATE-735 -import-match-rate-type-history in all submodules.

          Thomas Lauria added a comment - - edited

          The match-rate-typ history seems to be in an sdl:prev-origin tag, contained in the sdl:seg tag.

          Thomas Lauria added a comment - - edited The match-rate-typ history seems to be in an sdl:prev-origin tag, contained in the sdl:seg tag.

          Thomas Lauria added a comment -

          Also implement along this issue the replacement of (translate5) to the real used TMMT System, the tmmtid is already given in the request. See Marcs comment in TRANSLATE-684.

          Thomas Lauria added a comment - Also implement along this issue the replacement of (translate5) to the real used TMMT System, the tmmtid is already given in the request. See Marcs comment in TRANSLATE-684 .

          Thomas Lauria added a comment -

          In the source code I found the following remark:
          //REMINDER: this would be possible if we would know if the user edited the segment after using the TM
          //$matchrateType->add($matchrateType::TYPE_INTERACTIVE);

          To enable it, we have to track in JS - after taking over the match - the match content. On saving we have then to compare the tracked content and the content to be saved. When it differs then it is [TM/MT]-interactive. We can deliver this information in the matchrate field itself instead of the current placeholder.

          Thomas Lauria added a comment - In the source code I found the following remark: //REMINDER: this would be possible if we would know if the user edited the segment after using the TM //$matchrateType->add($matchrateType::TYPE_INTERACTIVE); To enable it, we have to track in JS - after taking over the match - the match content. On saving we have then to compare the tracked content and the content to be saved. When it differs then it is [TM/MT] -interactive. We can deliver this information in the matchrate field itself instead of the current placeholder.

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

              Created:
              Updated: