SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
I work with Trados 2017. There's this thing that keeps happening to me and that is driving me round the bend:
I seem to be hitting some weird combination of keys that causes Trados to mark all segments as translated, even empty ones. I know how to undo the damage (just change segment status), but what I'd really like to know is: What's causing it? Is there a key combination or button that I am inadvertently hitting??
Grateful for any ideas on what's going on...
It really depends on the way you work. When searching & replacing, I do not need to have the segments updating my TM in this very moment, having changed the status to "Translated" or whatever needed is…
This happens to me when I select and confirm several unconfirmed translated segments. Then all empty segments are confirmed too.
There is a shortcut for "Confirm all" - simply go to File -> Options -> Keyboard Shortcuts, locate this particular one and deactivate it. When done, an accidental confirmation of all segments should not happen again.
Thank you for your reply.
But I do not use the shortcut "Confirm all" - this one is deactivated in my case.
I just select e.g. 3 translated segments out of 100 empty ones. And I want to confirm only this 3 segments. But Studio confirms the whole file.
Adrian Palme said:I just select e.g. 3 translated segments out of 100 empty ones. And I want to confirm only this 3 segments. But Studio confirms the whole file.
Can you elaborate please:
1. Now I´m using Studio 2019 ver. 18.104.22.1683. But this is problem known to me since years, in Studio 2014-2017 too.
2. No filtering, all segments in the file are displayed. I select 3 contiguous segments of course - with the mouse or with Shift+Down/Up. Then I conform with the hotkey "Confirm and move to next unconfirmed segment". Or with "Confirm and don´t move to the next segment".
I tried it right now with a huge file I´m working on. All remaining 500 empty segments were confirmed. Studio froze for several minutes. Then I found out, that CTRL-Z has stopped working once again...
That is happening from time to time.-I am a version 2017 user, have no idea about version 2019
Have you checked, if the shortuct for confirming all segments isn't active in your Studio version?
When CTRL+Z stops working, you have to close Studio and restart it. Usually, when that happens, Studio will freeze in the near future or crash completely.
The shortcut for confirming all segments is not active.
As for not working CTRL+Z: I was told by the SDL support, that this bug will be corrected in S2019 SR2. Did not happen.
I suppose that restarting Studio all the time is not the way translators want to use it on daily bases...
Unfortunately it is the same in 2019 too.
More specifically, this "feature" is available since Studio 2014.