Is there a method to apply penalty on confirmed segments at Translation step?

Hello,

I am using Trados Studio 2022.

I've looked in the pages relating to specifying TM penalties (RWS Documentation) but I don't quite see what I am looking for. The closest thing I see is "multiple translations penalty" but that is not suitable for the scenario that I am hoping is possible.

Is there a way to assign a penalty to a translated segment that is performed by a translator but is not through QA? For example, if a translator has populated a translation and confirmed the segment, that would make that translation available to everyone via GroupShare, but the segment has not been approved through QA.

For example, is it possible to achieve a set-up that meets these elements?

- Translations confirmed at Translator stage has a penalty applied to segments (e.g. -1%) so that it is clear to the Reviewer what has not been 100% vetted/previously approved.

- Translations confirmed at Reviewer (Translation QA) stage has no penalty. 

For example, on a very large project where multiple translators are involved, it would be ideal to have translations that have been researched available to the team to save time but not showing as 100% to ensure users are clear it requires closer attention since it is not through the QA process.

If I'm looking in the wrong place, please let me know as well. I looked specifically at pages related to project setup penalties and through the forums (in vain!).

Thank you

Irene

emoji
Parents
  •  

    Well, when a segment is confirmed, it will be a 100% or a Context Match next time, depending on the situation. I see no possibility to change this when working with one TM.

    But why not use TWO TMs? One would be for the translators, where no QA has been performed yet. This TM could have a penalty of 1% for anyone else in team. The second TM would be read-only for all in team and consist only of revised content. Or you simply work with project translation memories. These are generated per project and will not be reused in the next project, so your QA team could easily separate revised from not revised content.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

    emoji
Reply
  •  

    Well, when a segment is confirmed, it will be a 100% or a Context Match next time, depending on the situation. I see no possibility to change this when working with one TM.

    But why not use TWO TMs? One would be for the translators, where no QA has been performed yet. This TM could have a penalty of 1% for anyone else in team. The second TM would be read-only for all in team and consist only of revised content. Or you simply work with project translation memories. These are generated per project and will not be reused in the next project, so your QA team could easily separate revised from not revised content.

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

    emoji
Children