Here's one way to confirm all segments: Click segment 2, then shift-click segment 1, then press Ctrl-Enter.

Here's one way to confirm all segments: Click segment 2, then shift-click segment 1, then press Ctrl-Enter.

This would not store your edits though. You have to run the Update TMs batch task. The same effect can be attained when you press Ctrl+Shift+A to select all segments and then change their status to Translated (confirmed but not stored)

Johnathan Barker 

It is always a good idea to use the Finalize batch at the end. This way you generate target and update the TM.

When you work with project TMs (as I always do), this is a simple necessity to have your final translations stored in your TM. IMO the habit in working with Studio should be:

• Open for translation, translate, save
• Open for revision, make your checks and changes
• Save copy of the sdlxliff file for tracking of the step done (must be done, if you are ISO certified, can be done for own tracking of work)
• Accept the changes done, change the status of changed segment to translated
• Close the file, confirm changing status of all segments
• Run finalize batch

Yeah, I see you often go like "I don't know why you may need that guys, for any reasons beyond my understanding, because I never do that. Do what I do..."
The workflow you described above is too long and complicated for a simple task like 'confirm all segments'. I should not be surprised if you create a project every time you get a translation assignment. However, I don't mind if you like it. It was just a kind reminder that you should remember to store segments.

Thank you Jerzy,
It is the ideal scenario, but I am not sure everybody follows that process in production. :-)

I am working only with projects in Studio, as this is the easiest way to keep track of what is happening.

Beside this, opposite to what you state, creating projects is the fastest way to work with Studio in case you have many different settings depending on the customer or other options. It is just calling a template and adding files, setting up paths and that's it. I understand there may be different needs, but having a defined way of working with a tool is a good method to avoid errors.

This said, I assumed, updating the TM AFTER you create your final translation is a general habit.

So funny, there's lots of discussion about the needs and the methods, but a much more efficient and up-to-date tool like MemoQ has features lik ethese incorporated  since ages....
Product development with Trados is way behind competition. Some clients force me to use Trados, otherwise I wouldn't even bother to keep it on; MemoQ is so much more flexible, user friendly and efficient. 

Willem Wunderink 

Well, I fully disagree here. You can confirm all segments in one go in Studio since ages now, too. And when talking about flexibility, there is no other tool on the market allowing me to use my own process, regardless what the customer does think. In memoQ you cannot do that. You cannot mix projects there, you cannot take files from one project into another, you cannot open one file or 10 files or 100 files within a project at once as needed without creating views. Merging or splitting segments is only possible, when allowed by the customer. Locked segments cannot be unlocked, even only to comment them. And many more.

Most of what you say there simply is not true, Jerzy.
If it was possible to confirm all unconfirmed segmenst at once in Trados, we wouldn't have discussions like in this topic. The moreover, the filter (complicated, much more efficient in MemoQ) doesn't even allow to select all unconfirmed segments to start with!
You may have exerienced that locked segments cannot be unlocked in MemoQ, for example, but that can only happen if it's a client project and the the client prohibits you to do so: it's simply a projects setting. But with standard settings it's all free. The creation of a view is a 2 second operation, offering you the flexibility to make your own selections within a project; a great feature. You apparantly don't work with both programs, as I do.

Just to name one single very important basic function that is missing in Trados: one cannot even sort segments as in memoQ. That is because Trados doesn't use a modern database as framework like MemoQ does, but a digital version of the document: wrong starting point....

No, compared to MemoQ the efficiency and flexibility of Trados is absolutely way behind. 
My output in MemoQ is some 30% higher compared to Trados: that sais it all.

 Willem Wunderink 

You confirm, that unlocking segment ist not possible, as it is project setting. So it is true what I say. But it is useless to discuss, as you are fully convinced with your product. Good luck with it. I have both on my PC (memoQ in the Project Manager version) and still prefer the flexibility of Trados. Another example of inflexibility in memoQ. You need to click every single error message in the QA report. I have never succeeded in moving around with keyboard.

What I compare are customer projects, not individually created projects, as in that terms even an Across is flexible...

And as you say: YOUR output. So this is individual and not really a reason to make a discussion here.

Well, it's useless to discuss indeed, as you deny the facts and choose to twist my words instead. 
Yeah, good luck to you as well, keep your blinkers on... :-)