• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 4226 views
  • Users 0 members are here
Options
Related

Issue with the "Complete Sign-off" button in Trados 2015

Christine Lee

Hi,

My team has JUST noticed that there was a change in what happens when clicking the "Complete Sign-off" button (or "Yes" in the message that appears when closing the editor) in Open for Validation mode, between Trados 2014 and Trados 2015. 

According to the SDL product help site, here is the description of that button in Trados 2014 : "Click this to approve all the translation in the document and set their status to Signed Off. This will also change any Translation Rejected or Sign Off Rejected translations to Signed Off." And here is the description for Trados 2015 : "Click this to approve all translations in the document except those with Translation Rejected or Sign Off Rejected status. The approved translations are set to Signed Off status."

Wait WHAT?! WHY? Because of this (and the way our project templates are setup, I suppose), any changes made to translations in Review mode and accepted in Validation mode were not uploaded to our translation memories during the Finalize batch task, because the segments containing those changes retained their Translation Rejected status. Consequently, our translation memories are now essentially full of non-revised, sometimes incorrect segments...

Anyone have a workaround for this, other than having translators confirm all segments before clicking "Complete Sign-off"? I know I can also change what gets uploaded to translation memories in the project templates, but I don’t think we always want Translation Rejected segments to end up in the memories (or do we, since they’ll have been checked by someone anyway?)... Any other ideas are very welcome.

Thanks! (And sorry for the rant.)

Christine
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Hi Christine,

    I think this change is to correct the previous behaviour that looks wrong to me.  If you have rejected segments you don't want the status of all of them to change unless you have physically checked them.  Otherwise you risk approving things that were marked invalid before you have a chance to check them off.

    I guess the workaround would be to select all the segments, if this is what you want, and then change the status to approved.  Or, use the SDLXLIFF Toolkit to just do all the files in your project in one go... or maybe the Segment Actions plugin also from the OpenExchange which might be even easier... gives you these options you can apply on selected files with a right-click in Studio:

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    I totally agree with Paul.
    With just a minor correction: the sign-off process should confirm all translation confirmed AND translation rejected segments, as their status is from lower level.
    IMHO both revision and sign-off process shall not confirm the segments rejected at their own level, when using the "complete" button.
    So with "Complete" in review mode all translation rejected segments shall remain rejected. Same in sign-off mode - here the sign-off rejected segments shall remain rejected.
    Why? Because it happens much too often, that we need to translate segments, but do not want to have them in translation memory. For example all crappy segments, broken by paragraph marks - I do not wish to have this rubbish in my TM. So leaving them SIGN-OFF REJECTED is just perfect. And it is so easy to CONFIRM all what you need - much easier that keep things unconfirmed.
    BTW, the behavior we have now in Studio 2015 is exactly the same as it was, when track changes were first implemented. So for me this is a return to the good old behavior.

    _________________________________________________________

    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.