GDM 

I think this probably originates from some changes that were made between the versions regarding the way the origin of the TU is stored and handled.  Can you share a snippet of your TMX file for such a segment?  I can't find the details of what the change was right now but will look when I get a bit more time... unless someone else happens to have this info to hand?

Hello Paul,

thank you for your help. Here is the tmx!

Best,

Gianpierokaspersky1109_IT.zip

GDM 

Thanks for the TM.  Daniel Brockmann can probably confirm but I believe this was changed at the request of our users generally.  The idea being that you only want AT or NMT in the status column if the result is coming from an engine in real time.  If you import into a TM it is assumed you are doing so after checking it for accuracy.

So, if you have not done this then the solution would be to use a filter penalty... maybe something like this:

So the idea being you apply a penalty for the last used by field to ensure unchecked MT results in a TM are not seen as 100% matches.  Once you confirm them they will become 100% matches as you can see from segment #3 which I confirmed and therefore changed the Last Used By value.

You can set the penalty to whatever value you wish supported by the software.

GDM 

Thanks for the TM.  Daniel Brockmann can probably confirm but I believe this was changed at the request of our users generally.  The idea being that you only want AT or NMT in the status column if the result is coming from an engine in real time.  If you import into a TM it is assumed you are doing so after checking it for accuracy.

So, if you have not done this then the solution would be to use a filter penalty... maybe something like this:

So the idea being you apply a penalty for the last used by field to ensure unchecked MT results in a TM are not seen as 100% matches.  Once you confirm them they will become 100% matches as you can see from segment #3 which I confirmed and therefore changed the Last Used By value.

You can set the penalty to whatever value you wish supported by the software.

Hi there GDM  and Paul  - this is a remaining side effect of a bigger change we did around TU statuses a while back. This particular symptom where the creation user is "MT!" will be corrected in the next cumulative update (tentatively planned for first half of September); in the meantime the workaround is exactly as you describe Paul - put a penalty on the MT! user. Thanks, Daniel

Hello Paul and Daniel Brockmann ,

thank you very much for your support. I am glad to hear this is a general issue; I feared something had gone wrong when I installed Studio 2022 SR1 on my machine. I am releaved to hear that this issue will be corrected soon!

Best,

Gianpiero

Hello Daniel Brockmann , do you know if the problem with MT results has been solved with the new update of Studio 2022 released at the end of September? I can't find any reference to this issue in the relase notes. Thanks, Gianpiero

Hi ghere GDM  - yes it should, it's this bullet point in the knowledge base article at Cumulative Updates for Trados Studio 2022 (sdl.com):



Thanks, Daniel