Hi, me again. I just tried on my colleagues pc with different projects, same problem. But I noticed, that it seems to happen only with EXCEL files.

Paul?

Hi Burim Bektesi

Thank you for your clear explanation.
However one point i want to establish is that file formats such as Excel vs something else has absolute no impact on how TM's are being updated.
Your colleague may have been able to reproduce the issue, but it would be been down to local settings of some description.

Your shortcuts intrigued me as there is a difference between updating TM on the fly using the supported short cuts

Vs Batch Task update which does the entire project/file

Are you still getting the problem of duplicates? If yes, Id be more than happy to help further

Lydia

I have the same problem. During manual translation if I confirm a segment with a different translation than what's already in the memory, Studio adds it a new segment instead of updating the existing segment.

Hi Lydia Simplicio 
Hi André Stryger  

Working with SB TMs, we discover(ed) this too and reported it under the following case numbers:

00795311, 00780441 and 00813808.

We did not change the shortcuts.

We tested in
- Trados Studio 2021 SR2 - 16.2.10.9305
- Trados Studio 2022 SR1 - 17.1.6.16252

using

- Server-based TMs on GS 2020 SR1 CU08.1

CRQ-35473 was logged and the defect may be addressed in a further version of GS or Studio; currently it is still in the backlog.

Best regards

Seraina

Dear Seraina,

I don't know when and why this happens, but we notice again and again, that during time our TMs have become full of duplicates, although we NEVER use the option of merging or keeping the old translations, but always overwrite. This is a huge problem and happened in projects of different customers and different (very experienced) project managers. I am astonished this hasn't become an issue in the community. I cannot believe that this happens only to us.

Hi Burim Bektesi 
Yes, same here. Our TMs are full of duplicates, too.
I hope this bug will be addressed asap by RWS development.

Same problem here too. Has been going on forever. It really defeats the whole purpose of using a translation memory.

Apparently it doesn't seem to be a big issue in the commuity so I don't think that someone at Trados is really looking into it. I made the experience, that as also myself, I have no time reporting and following up on all these things, others may have the same problem and do not report. Although - as you say Andre - it really makes you question the use of TMs.

Apparently it doesn't seem to be a big issue in the commuity so I don't think that someone at Trados is really looking into it. I made the experience, that as also myself, I have no time reporting and following up on all these things, others may have the same problem and do not report. Although - as you say Andre - it really makes you question the use of TMs.

If it's not a big issue in the community that the TM is picking not the segment you just corrected but the old one that contains an error, then I wonder what the community is busy doing.  Oh I know. Busy trying to get work done while firefighting all the bugs in Studio, so that we have no time reporting them. Not to forget being forced to pay for a new upgrade every two years where there are minimal improvements plus a flurry of new bugs since software developers don't seem to test anything anymore. 

This may be a bit exaggerated, but at the moment I do indeed have several bugs in Studio 2024 and just can't manage to work them up properly to report, although some of them mean that we can't use studio 2024 at all.

I would still like RWS to take a look at these and many ‘smaller’ requests instead of  trying to invent the big changes.

André Stryger , even if there is no time for reporting, I am still surprised at the (missing) number of upvotes?!

Though, I see, there are now votes here, just in the ideas section. Maybe it would make sense to add some kind of vote also here, to see the amount of consent.