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

A separate autostatus pretranslated is missing for pretranslation

    • High
    • Hide
      Introduced new processing state (AutoStatus) "pretranslated".
      This state is used for segments pre-translated in translate5, but also for imported segments which provide such information. For example SDLXLIFF:
      if edit100%percentMatch is disabled, used full TM matches not edited in Trados manually are not editable. So edited 100% matches are editable in translate5 by the reviewer now. Not changed has the behaviour for auto-propagated segments and segments with a match-rate < 100%: they are still editable as usual.
      Show
      Introduced new processing state (AutoStatus) "pretranslated". This state is used for segments pre-translated in translate5, but also for imported segments which provide such information. For example SDLXLIFF: if edit100%percentMatch is disabled, used full TM matches not edited in Trados manually are not editable. So edited 100% matches are editable in translate5 by the reviewer now. Not changed has the behaviour for auto-propagated segments and segments with a match-rate < 100%: they are still editable as usual.
    • Hide
      Introduced new processing state (AutoStatus) "pretranslated".
      This state is used for segments pre-translated in translate5, but also for imported segments which provide such information. For example SDLXLIFF:
      if edit100%percentMatch is disabled, used full TM matches not edited in Trados manually are not editable. So edited 100% matches are editable in translate5 by the reviewer now. Not changed has the behaviour for auto-propagated segments and segments with a match-rate < 100%: they are still editable as usual.
      Show
      Introduced new processing state (AutoStatus) "pretranslated". This state is used for segments pre-translated in translate5, but also for imported segments which provide such information. For example SDLXLIFF: if edit100%percentMatch is disabled, used full TM matches not edited in Trados manually are not editable. So edited 100% matches are editable in translate5 by the reviewer now. Not changed has the behaviour for auto-propagated segments and segments with a match-rate < 100%: they are still editable as usual.

      problem

      1. The calculation of the segment auto status on pretranslation via language resources is not working correct
      2. For pretranslations there should be a new auto status "pretranslated" which should be used for such segments

      Segments that are pre-translated by MT or TM should not count into the progress of the task. They should not be considered as finished. CTRL+ENTER and the other workflow-step-related segment actions should not skip, but open them, if they are the next segment.

        1. translate5(14).png
          translate5(14).png
          177 kB
        2. translate5(15).png
          translate5(15).png
          151 kB
        3. translate5(16).png
          translate5(16).png
          155 kB

          [TRANSLATE-1643] A separate autostatus pretranslated is missing for pretranslation

          To talk over tlauria marcmittag

          Notes:

          1. what should happen with setUntuchedState with segments with autostatus pretranslated
          Thomas: it should be set to reviewed untouched

          • Do we need something similar to translators which do not confirm pretranslated segments

          2. What should happen when segment is commented (updateAfterCommented -> AutoStates class)

          Aleksandar Mitrev added a comment - To talk over tlauria marcmittag Notes: 1. what should happen with setUntuchedState with segments with autostatus pretranslated Thomas: it should be set to reviewed untouched Do we need something similar to translators which do not confirm pretranslated segments 2. What should happen when segment is commented (updateAfterCommented -> AutoStates class)

            tlauria Thomas Lauria
            tlauria Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: