Matches from TM populated with MT output does not show as AT

Question

Hello, 
 I am tring out Trados Studio 2022 SR1 and I have a problem I did not have with Studio 2021. I have a tmx which contains machine translated segments (not machine-translated with Trados). I have then created a blank TM and imported the tmx. When I start translating, matches from that TM are not identified as AT (automated translation), but as normal fuzzy matches. 
 If I try the same process with Studio 2021, I do not have that problem. 
 If I create the TM with Studio 2021 and import the tmx with Studio 2021 and then open the project with Studio 2022, I do not have that problem, so the problem seems to lay somewhere in the TM creation process or in the tmx import process in Studio 2022. 
 Any ideas how to solve this? 
 Kind regards, 
 Gianpiero De Merulis 
 
 EDIT: I have narrowed down the problem to the process of importing the tmx. Regardless of which version I use to create the TM, if I import the tmx with Studio 2022, I get fuzzy matches, whereas if I import the tmx with Studio 2021 I get AT matches. It's as if, when importing tmx into the TM, Studio 2022 does not store the information that segments in the tmx are machine translated, while Studio 2021 does it.

Daniel Brockmann · Accepted Answer

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

Paul · Answer

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.

Daniel Brockmann · Answer

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

Trados Studio > 1. Trados Studio

Matches from TM populated with MT output does not show as AT

Top Replies