Camille Bertrand-Sittler

We probably need a bit more info here.  Things like:

• what settings do you use when updating the TM via the batch task?
• are you using any field values in the TM?
• if you are how have they been set up?

Camille Bertrand-Sittler

We probably need a bit more info here.  Things like:

• what settings do you use when updating the TM via the batch task?
• are you using any field values in the TM?
• if you are how have they been set up?

Hi Paul!

No, we don't use any fied values.

This is the settings I'm using. 

Thanks!

Camille Bertrand-Sittler

Might be related to the use of this:

Could also be related to this if you have some segments that are not set as the status you expect:

They'd be the first things I'd investigate in your shoes.

To avoid issues like this, I always use either “Overwrite existing translation units” or “Keep most recent translation units”. However, if you are working with an agency, you have no control over how they manage the TMs, so, even if you do this, you might always end up seeing those old translations in the TM, or even getting them as 100% hits in your bilingual files, over and over again.

If I remember correctly, ever since Tag Editor times, it has always been the default behavior of Trados to save both the old and the new translation - and then, when pretranslating a new file (for a reason unknown to me), use the _old_ translation by default. I can understand the first, but not the latter.

Great. I'll check that. And what about the fact that I have to use the Update Main Translation Memories function to erase the old segment? Is there a setting in the project that I have to use to overwrite the old translation automatically? Or do I have to use the Update Main Translation Memories function each time?