Hi Berthold, I presume you can use the filter All segments > Automatically translated so that you view only automaticaly transalted segments. At that point select them all (Shift+right click on the first and last segments), right click again and select Change Segment Status > Draft (or Not Translated, whatever was their status earlier). HTH

(PS. I think you accidentaly pressed some key combination that unconfirmed the segments. If it happens again and you notice, just press Ctrl+Z to undo the last step and the file(s) will go back to the previous state.)

Hi Adriana,

Many thanks, this helped and now I have all like it was before, also the fuzzy matches.

Indeed I went immediately on the undo symbol on top left, but most certainly there was already a step in between, I realized too late that all of them  were confirmed. Now everything is again as it should be.

Happy it helped! :)

This has been a bug in Trados Studio since 2009. I reported how to reproduce it here.

One thing you can do when this happens is immediately quit Trados Studio without saving, then restart it and use the auto-saved version of your file.

You can handle this bug quite easily.

Use CommunityAdvancedDisplayFilter, just like this screenshot.

After filtering, you select all of them and "Change Segment Status > Not Translated".

a little bit more convenient style is to use AutoHotkey programming language.

To fix a Bug [Confirm ALL Empty Segments Error]
https://community.rws.com/product-groups/trados-portfolio/trados-studio/f/autohotkey/27636/to-fix-a-bug-confirm-all-empty-segments-error-i

You could make it as a form of Trados Studio PlugIn which implement the same logic as AutoHotkey, then way better.

Of course, the best solution is not happen this bug again with the improvement of Trados Studio.
The root cause is not from User side but from Trados itself, because the other CAT tool does not make this kind of vexing situation ever.

John Fry

John Fry said:

This has been a bug in Trados Studio since 2009. I reported how to reproduce it here.

Probably the reason this doesn't get any serious attention is for two reasons:

1. your explanation involves doing something that has never been a feature in the first place.  Better to right-click and change the status if you want to confirm multiple segments in one go.  Using the Confirm command will not add all the selected entries to a TM anyway so that action is pointless.
2. It's not a bug (your explanation of the problem) because it only happens when you attempt something that isn't supported anyway.  So the product manager, if he's even aware of this, is very unlikely to see this as an urgent issue that needs to be resolved ahead of other things.

I think you can all refer to this as a bug if you like.  But it won't help to get anything changed.  A better approach might be to suggest the Confirm action does nothing at all when multiple segments are selected.  That seems a more sensible and achievable solution. Having the Confirm change the status and also update a TM is very unlikely to get development time as we have a batch task for that purpose.  Either way I suggest to post your thoughts on this in the ideas section and get others to vote on it.  If it's really a problem that affects so many users surely it'll be easy to get more than enough votes to get a little support.

If you just wanted a quick way to change the status of multiple segments then perhaps use the segment status switcher from the appstore.

Paul, I think this happens by accident, not because users *want* to confirm multiple segments. The relevant facts as I see them are: (1) Users press Ctrl+Enter hundreds of times per day; (2) Every time you press Ctrl+Enter there is a small chance that all of the segments in your file (in some cases thousands of them) will be confirmed, creating an extremely stressful situation for a freelancer on a deadline (like Berthold) who is not prepared for it.

There is a shortcut for "Confirm all":

So before you do anything else check if there is NOTHING assigned, what could (and would) be pressed accidentally. In this very case I strongly suppose the reason were subsequently but unintentionally pressed shortcuts, what led to confirming all segments. There is no bug in the software responsible for this. It happens to all of us every now and then, but this is so rare, that I never would blame the software. In my opinion the problem here is sitting in front of the computer.

John Fry

John Fry said:

I think this happens by accident, not because users *want* to confirm multiple segments.

I see.  That isn't what I can derive from your explanation of how to reproduce it or the rest of the conversation in that thread.

It would be very helpful to know how to reproduce this problem from a single keystroke without doing something else first that selected multiple segments.  Perhaps this is the solution:

Paul said:

A better approach might be to suggest the Confirm action does nothing at all when multiple segments are selected. 

That at least would ensure this problem could not happen, even by accident.