Under Community Review

Update Different Translation Memories at Different Workflow Steps

It would be useful to be able to update different translation memories at different workflow steps. For example, we would like to update a "Working" TM during "Translation" step, and a "Reviewed" TM during review step, so that we keep content that was translated but not reviewed in separate TMs. 

Andrea Jimenez
Parents

  •    I'm not sure many in industry would agree with this decision. It's essentially suggesting that it makes more sense to change customer behaviour than to introduce a feature that would be expected / is common. Essentially, if one has a pool of new translators and experienced ones, this means the expected work in Trados will differ from a team that has only experienced translators.

    Would an option to introduce a different shortcut that stores translation on project-level only, instead of into a TM, possibly be acceptable, knowing that this would probably mean less dev work?

Comment

  •    I'm not sure many in industry would agree with this decision. It's essentially suggesting that it makes more sense to change customer behaviour than to introduce a feature that would be expected / is common. Essentially, if one has a pool of new translators and experienced ones, this means the expected work in Trados will differ from a team that has only experienced translators.

    Would an option to introduce a different shortcut that stores translation on project-level only, instead of into a TM, possibly be acceptable, knowing that this would probably mean less dev work?

Children
  • in reply to Goran Markus

    Hi, I agree - depending on the skill of people, they may even confirm all MT matches without even looking - having the flexibility to override the TM Update settings in certain workflow steps would be great to have, ensuring that e.g. non native reviewers when involved in review would update a different TM. Either that or customizable TU statis  values that can get configured per worklow step...