Under Community Review

Show translation version history in online editor

This is another feature we have lost transitioning from WorldServer to Trados Enterprise.

In the browser workbench of WorldServer we are able to see the version history of a translated segment and easily roll back the translation if needed. This also assist us in seeing when a quality issue may have been introduced. The TE online editor does not enable us to pinpoint where quality issues were introduced.

This also enables individuals further along the workflow to see what changes were made by editors or reviewers.

Screenshot of SDL WorldServer Browser Workbench showing a translation task with three segments. Segment 2 has Chinese characters with a change highlighted.

Russell Banton
Parents

  • Hi Russell,

    If you enabled Tracked Changes, you would see the changes that were made by editors and reviewers, you can even force Tracked changes for certain tasks, so it can't be disabled. Have you had a chance to explore this?

    While we don't have a full history of each version displayed, we have Word-like Tracked Changes functionality currently. In future we are looking at also exposing this kind of information, but in the meantime Tracked Changes may do the trick.

    Thanks,
    Luis

Comment

  • Hi Russell,

    If you enabled Tracked Changes, you would see the changes that were made by editors and reviewers, you can even force Tracked changes for certain tasks, so it can't be disabled. Have you had a chance to explore this?

    While we don't have a full history of each version displayed, we have Word-like Tracked Changes functionality currently. In future we are looking at also exposing this kind of information, but in the meantime Tracked Changes may do the trick.

    Thanks,
    Luis

Children
  • in reply to Luis Lopes

    Hi Luis,

    Track changes does not do a great job recreating the experience we have in WorldServer. It is a bit chaotic how all the separate changes show in the track changes window for a single segment as well. We'd also lose the version history once the changes are accepted at any point in the translation process so we would not be able to pinpoint where quality issues are introduced. Version history would be a great feature to have, especially without needing to force individuals to work in a track changes mode.

    Best,

    Russell

  • in reply to Russell Banton

    Hi Russell,

    I agree with the comments you shared. I personally think that Track changes can be useful from a linguist's perspective, but it cannot replace the effectiveness of having the segment history when talking about the quality perspective (used more by PMs, LEs, QA). Similarly to your organization, we frequently reviewed segment history in TMS to investigate quality issues and it's a feature that's sorely missed in TE.

    I would say an option that's a bit more helpful in our shared use case is to use the File Version History under Files because those files actually seem to save what was submitted at each workflow step.

    That said, the user then needs to analyze the files using a text comparison tool and that's not necessarily simple for everyone to do so having the actual segment history within the online editor is my ideal design as well.