Under Community Review

Default behaviour in translation status - can it be changed?

Hello,

When finishing translation in Trados Studio, the default behavior is that the project status changes to "In review", the progress bar of the translation is reset to 0. We would like to know if we can change this default behaviour and avoid that Studio automatically switches the projects to "In review" status.

Thanks in advance.

KR

Özge

Özge Ünlü
  • in reply to Gwen Gondry

    What I do when the software throws the work into revision phase is to start from scratch with "Open for translation", which resets the segments as for translation, not review. I don't know how practical this is on the scale you hint at.

    Incidentally, I see you work for the OECD. Does the Organisation use Trados Studio? I'm a former OECD staff translator in the early 1980s. Interesting to liaise. I have just downloaded the:

    document and I shall forward the link to two learned societies:

    - the Responsible AI network of the RSA, of which I am a fellow, and

    - the Société Française des Traducteurs Forum.

    I hope we can get this problem ironed out - while I continue to militate for a 64-bit version of Trados Studio.

    With best wishes,

    Adam Warren.

  • in reply to Gwen Gondry

     

    Ok, adding an extra status is fine, now I get it. But this is not a change of current behaviour, but a deep modification of it. So I would suggest, you post another suggestion with your description, asking for such a status. This makes really much more sense than changing the current behaviour without such a status.

  • in reply to Jerzy Czopik

    We're simply asking for flexibility, not a change that would apply to everyone. I hope my latest comment below makes things clearer. (By the way, I've been using TRADOS tools in various capacities since 1998 and am well-versed in their intricacies. My role involves optimizing user experience within a large team to ensure streamlined workflows.) 

  • in reply to Adam Warren

    This is a familiar scenario for us. We use statuses to differentiate between segments that may not be re-touched without going through a specific approval process, segments that are deemed correct but could be changed for improvement or consistency reasons, etc. We also use the translation rejected status for segments that are in the file but should not be translated. This is in fact the root of the issue.

    However, this setup creates an issue: when translators complete their work, the progress bar moves to revision instead of translation and drops to zero. This happens because Studio interprets "translation rejected" segments as the start of a revision cycle.

    We need a way to exclude non-translatable segments without: 1/ Leaving them blank (because then the progress bar will never reach 100%) 2/ Using a status that incorrectly signals a revision cycle

    A rejection status dedicated to the translation cycle—one that neither updates the TM nor triggers a switch to revision—would solve this problem. It would also ensure that the progress bar reaches 100% once the translation is done and stays there.

  • in reply to Adam Warren

     

    This is a very valid way of working. You use the statuses for your own purposes, even if these haven't been designed to work that way. But this only supports what I say: the current design is fine and can be used as needed.