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ü
Parents

  • I hope I 'm not throwing a cat among the pigeons, but I use the different statuses for a different purpose in a complex translation assignment for publication, arbitrarily assigning them the following meanings:

    I use "Translation rejected" to earmark segments in which material needs research before validation (quotations to be sourced, validation required by the client from sources held exclusively in manuscript form by the client);

    "Translation approved" denotes segments that have been previously translated in the series, and can be passed on unchanged;

    I mark as "Signed off" segments that have been updated from previously-translated segments in the same series;

    "Sign-off rejected" marks segments that are not to be translated: in this assignment, these are mainly instructions to the proofreader and page setter.

    I should state that I operate solo, in direct liaison with the end client, who does not work with CAT software.

  • 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.

  • 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.) 

Comment
  • 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.) 

Children