Citlalli Mejía 

I think you seem to have at least two problems.  First all of these strings are alphanumeric so this means Studio will AT them all unless you disable that.  Second problem is you seem to have some strange setting I can't actually replicate because you are getting identical matches for every string with a completely different source and I can't achieve that at all.

Please can you share screenshots of your relevant settings?

• TM language resources
• TM Search settings (from your project settings)
• Auto-Substitution settings
• Auto-propagation settings

Also can you confirm your workflow for getting to this stage?  How were the files handled... did you do the entire project on your own?

Lastly... it would be good to know what version of Trados Studio you are using, and maybe how many TMs are in your project?

Hello Paul,

Thank you, and apologies for the delayed response. That project left me completely drained, and I’ve only just regained the energy to investigate what might have gone wrong.

I resolved the issue at the time by working hard rather than smart — I disabled autopropagation and reviewed the segments manually, one by one. However, I’d still like to understand what triggered this behavior so I can prevent it in the future.

I’m using SDL Trados Studio 2019. I was reviewing a project, so I received both a project package from the PM and a return package from the translator. Everything seemed normal until I began the QA phase. When I hit Ctrl + Enter to confirm an alphanumeric segment, a pop-up appeared with a progress bar, indicating autopropagation across numerous segments. I confirmed two before realizing what was happening. After that, I stopped confirming segments to avoid exacerbating the issue and just proceeded with QA.

I've attached some screenshots of the project settings below in case they help clarify the problem.

Thanks again for your help,

Hi Citlalli Mejía,

I once had a similar issue with autopropagation and the cause turned out to be erroneous entries in the TM I used. The faulty entry was either in one of the project TM or one of the master TM, I'm not 100% sure. Anyway, I had to go through all my project and master TM, searching for partial matches of the autopropagated translation and deleting the erroneous segments. In my case, this solved the issue.

You may have already checked this, in which case, please disregard my reply. 

I can confirm I encountered the same issue, which was caused by an incorrect entry in the translation memory. I believe RWS should implement a fix to prevent the potentially serious consequences of such errors.

I can confirm I encountered the same issue, which was caused by an incorrect entry in the translation memory. I believe RWS should implement a fix to prevent the potentially serious consequences of such errors.

tommaso maria minardi  and others in this thread

Well, would you sue the vendor of a digicam in the same way, if your photos would bad due to wrong setting of the shutter or sharpness or diaphragm? Certainly not, as these settings must be properly used. In that respect Studio is exactly the same as a very professional digital camera. A good artist can create perfect pictures with it, while an amateur will achieve only average results.

The autopropagation in this very case was triggered by the recognition of alphanumeric strings. Such strings consists only of so called "word characters", which are letters, numbers and underliners in this case. Something like Ab_2 is an alphanumeric string. Another setting with similar effect are acronyms, as when activated BMW or AUDI will be treated the same way as DANGER or CAUTION.

Please do not get me wrong, but this is OUR responsibility to use the tool delivered by RWS in proper way. The settings responsible for this "error" may be very useful in certain scenarios, while in other scenarios they are problematic. But these are only settings, which can be changed. This is not in any way an error in the software and does not need to be fixed at all.

Sorry but I never talked about a sue, nor a claim or anything like this... The answer is maybe a bit overreacting. I was just suggesting that maybe a fix or a control could be provided, as I've heard of this issue several times and by experienced linguistis. If I'm wrong, apologies, t.

My intention was only to offer another possible explanation from on my own experience. In my case, the issue was caused by a prior mistake made during translation (I blame my habbit of pressing CTRL+Enter too quickly). As far as I'm concerned, the autopropagation feature works as expected.

Some kind of verification sounds like a great idea. But I think this has to be implemented by the user, because only they know when they do want autopropagation and when they do not want it. IMHO the software provides quite a few options that can be used to that end.

Wishing everyone a great week!