Hi Fatima Zohra Boubendir ,

Go to File > Options > Editor > Auto-propagation and change the default settings (in my opinion, they are not very logic ...). My settings are the following:

I hope that helps.

Best regards, Annemieke

Thank you so much Annemieke for your help. I really appreciate it, and you are right, the settings are not very logical. 

That does not work for CM, PM segments or Translation Approved, Translation Signed off etc...



(YES; I KNOW that that such segments are supposed to be OK - but you all know that people are sloppy and disorganized and this process is fine in theory, but does not work in practice)

Hi Frank Jensen  and  Fatima Zohra Boubendir

Actually for the situation Fatima presented - already confirmed segments that needed replacing to update them - you have this option in Trados- File- Options - Editor - Auto-Propagation- Auto-Propagate exact matches to confirmed segments, that is aside the manual find and replace. And of course here people make their own other settings according to their needs.

Best regards,

Anca

You are not reading what I wrote. This function does not work with CM and PM and the segments I mentioned.

I did Frank, but I referred to what Fatima posted she needed help with. She wasn't referring to CM or PM, she needed to replace exact matches from the new TM she updated and I quote "I have now an updated TM but I was wondering if there is a way I can auto-propagate the new updated translations into the already confirmed segments?" - and the above option can help with that.

As for how users work and make changes and decide to go back on a translation already confirmed, that is something no software can control. Each person decides on a workflow and sometimes it may not be the best choice - nevertheless, it is a choice.

Well, this is a well-known problem amongst Trados users. You get a pre-translated file with both CM matches and some PM matches, BUT even though they are CM and PM the clients expects consistency to be incorporated - could be due to glossary updates and other reasons - but they do not change the match category because they do not want to pay for them all, but only the segments that actually has to be changed.

Now, auto-propagate is not build for that, but why isn't there an option where one can force replace to ALL segments no matter what?  Or is there such an option??

F

Well, this is a well-known problem amongst Trados users. You get a pre-translated file with both CM matches and some PM matches, BUT even though they are CM and PM the clients expects consistency to be incorporated - could be due to glossary updates and other reasons - but they do not change the match category because they do not want to pay for them all, but only the segments that actually has to be changed.

Now, auto-propagate is not build for that, but why isn't there an option where one can force replace to ALL segments no matter what?  Or is there such an option??

F

If you know exactly what you need to replace and are sure it may not cause issues with your translation, you can also use the Find and Replace and opt to Replace all - it works with one word of phases or an entire segment content even when a segment has been confirmed.

And even if Auto-Propagate's main role is different, it can be adjusted to fit other needs.

As for how project managers set the projects or the packages for the translators, that again in something out of the software producer's control - be it Trados or any other one.

A project manager can set various limitations for a project or a package depending on a software's capabilities and depending on what they want from the translator and how they want their text/content to be handled. For example, and  it is a well known situation, there are companies that want the translator to use only the TM or TB they send and limit the use of other resources, like MT or AI. That is something a translator knows when accepting a job.

There are functions and features in a CAT tool designed to make things easier, but these functions cannot always go over the settings of the package itself if the package was created with certain limitations.