Planned for Future Release

Add configurability to enable if "automatically confirm unconfirmed segments" check box shows in Online Editor

From a quality and admin perspective we want to be able to control if this checkbox is shown to individuals working in the Online Editor. Typically, we do not want this shown as there have been quality issues in the past where a linguist forgets to go back and change an unconfirmed segment in a project before completing the project. If the segment is auto confirmed, this bad translation is now in the TM. There are also other reason why a segment may be left unconfirmed, but adding this check box creates the risk that the TM will become polluted.

Screenshot of the 'Complete Translation' dialog in Trados Enterprise. Highlighted checkbox reads 'Automatically confirm unconfirmed segments before completing.' Options include 'Complete task' and 'Cancel.'

Russell Banton

  • Has anyone tried this feature when completing the Linguistic Review step?

    I noticed that this feature seemed to work for submitting Translation, but Linguistic Review did not confirm any of my "unconfirmed" segments. To my knowledge, if I edit a segment in LR and it goes to Translation Rejected, that's still technically an "unconfirmed" segment. Am I mistaken?

    I inquired with Support about this and they told me this was intended behaviour.

    "During the Translation phase, segments with statuses Draft or Untranslated are converted to Translated. During the Linguistic Review phase, any segment that is not manually set to Translation Approved or Translation Rejected will automatically become Translation Approved. During the Client Review/Sign-Off stage, any segment that is not manually set to Sign-Off Approved or Sign-Off Rejected will automatically become Sign-Off Approved. This is the intended behavior. The Translation Rejected status is used to indicate to the next person in the workflow (usually the original translator) that a segment has been modified, allowing them to easily identify where their original translation was incorrect. This is an essential feedback mechanism to help linguists learn and improve. If segments with changes were automatically marked as Translation Approved, the original translator would have no way of knowing which parts were modified."

    If the above is truly the case, I am wondering if this feature should be more appropriately named as "Automatically confirm Draft or Not Translated segments before completing" because the current name is misleading.

  • in reply to Russell Banton

    Hey Russell, I confirmed that the entries were indeed saving to TM, we just had some other engine issue which was skipping the step in the workflow. Thanks for confirming!

  • Thank you all for the feedback. We'll look to introduce an option to disable this at a project template level.

  • I agree, it is too tempting for some of our laymen reviewers to simply use this function without really checking the translation. This is going to cause quality issues, please adjust this.

  • Unless the autoconfirmed segments get a special TU status field that allow to exclude them from re-leveraging if needed it definitively should be controllable if this is allowed as it lowers the barrier to just automatically confirm without looking too far.