For future reference, I'm adding another solution, as suggested on the Ideas site by Jerzy Czopik and extended by me...

Quoting Jerzy: "If you use "open for review" and do some corrections, you only need to confirm the corrected segments. When closing the file all untouched segments will be brought to the status "Translation approved". In my opinion this is the correct way to make final corrections after the translation—not in translation, but in review mode.

There is a shortcut to select all segments and you can change the status to whatever you want, but this is obviously already known."

Now my addition: If you open the file in Review mode, when you close it, the following dialog opens:

Click 'yes' and the whole file will be confirmed as 'Translation Approved' and updated to the TM. You can tick 'Don't ask this question again' and it will just happen automatically. As you can see, I haven't ticked that box, because sometimes I want to close the file before I have finished proofreading or reviewing it.

All the best,

Ali

Actually, Alison's solution better answers my need, since my problem was to reconfirm all segments after a batch search and replace (e.g., of a character) in a large document. I had no problem with individual corrections, where confirming each segment after a individual correction is not an issue.
Thank you again :-)

You can try to filter segments after your batch edits (by Draft status), select across them all from segment 1 to the last one and press Ctrl+Enter.

Hi Philippe...This works well if you are required to deliver a "Reviewed" document, but if you are required to deliver a "Translated" document and pass it on to a Reviewer you are still stuck with having to change a large amount of segments to "Confirmed" without showing the magnifying glass (you know what I mean)...My solution was to:

- Select the segments you want to confirm;

- Go to "Change segment status" on the upper bar next to the Confirm button. This changes all your segments quickly to "Confirmed" but it does NOT update your TM. Then,

- Update your TM using Batch Tasks.

I hope this helps.

It's what I do too, but the fact is that it remains a workaround when it should be a available function....
Thanks anyway :-)

Philippe Riondel said:

It's what I do too, but the fact is that it remains a workaround when it should be a available function....

Philippe Riondel 

Why do you consider this to be a workaround? From my point of view this is the expected way to work. TM is only updated when segments are confirmed actively. And in my case this is always a project TM, so regardless how the segments are confirmed I need to run at least the TM update batch aftewards to have my main TM updated with the translation.

Philippe Riondel said:

It's what I do too, but the fact is that it remains a workaround when it should be a available function....

Philippe Riondel 

Why do you consider this to be a workaround? From my point of view this is the expected way to work. TM is only updated when segments are confirmed actively. And in my case this is always a project TM, so regardless how the segments are confirmed I need to run at least the TM update batch aftewards to have my main TM updated with the translation.

One example: when we, in French, have to batch-replace strait apostrophes with curly apostrophes at the end of a translation, this may unconfirm many segments. Yet, both of those segments deserve to be saved in the TM after that cosmetic action. It could take just seconds with a dedicated function, while it requires many key presses to confirm manually those segments for a person wo do not think of that so-called workaround. A dedicated function would be more straight forward than a 2-steps unintuitive process.

Philippe Riondel 

I dare to differ here. The action is fully intuitive, like filtering or selecting all are. Why do you run such a replacement instead of using the correct apostrophes or whatever already during the translation? This would be fully non-intuitive for me...

Because I dictate a lot, rather than typing (with Windows Speech Recognotion), and that that service does not allow to use curly apostrophes. Also, when copying and pasting a quote form another source, retrieving perfectible segments from a memory or using automatic translation, you have to live with existing characters.
But it is not only about apostrophes. you also may want to batch-insert a non-breakable space before %, $ or : signs, which Windows service does not do either...

Philippe Riondel 

Understood. In order NOT to change the segment status simply use the Toolkit for such replacements. Then you will only need to run the update TM batch.

Thank You Jerzy, I will explore that way later today.