Jenny Grela 

I don't know what ticket this is under, but have you got a workaround in the meantime?  The most common problem relates to this attribute:

o-tmf="some text in here"

If you delete this attribute altogether the import often just works.

Dear Paul,

thank you for answering.

I don t know under what ticket it is. I was just told that the technical team was working on it since you couldn t solve the problem. 

I do work on trados 2017 now. I import the files there and open the document up in trados 2022.

I was just worreid as I have updated mu trados 2017 to 2022 so my trados 2017 will disappear if a buy a new computer or my computer crashes and then I am not able to work with trados 2022 since none of the files in the TMX are imported and I get no suggestions at all.

My internal case number: CRQ-31197

Kind regards

Jenny

Thanks Jenny Grela , by ticket I actually needed CRQ-31197, so that was helpful.

The work isn't planned in yet so I don't think we can provide a fix date, but the suggested solution was related to what I said.  If you delete the o-tmf="some text in here" attribute then you'll be able to import your TMX.

I do recall this being a problem in even older versions of Studio, it all depended on what value the o-tmf used.

So simple fix for you for now, and I'm sure the dev team will get around to this and include in a future version once it makes sense to plan it in with other work.

Thanks Jenny Grela , by ticket I actually needed CRQ-31197, so that was helpful.

The work isn't planned in yet so I don't think we can provide a fix date, but the suggested solution was related to what I said.  If you delete the o-tmf="some text in here" attribute then you'll be able to import your TMX.

I do recall this being a problem in even older versions of Studio, it all depended on what value the o-tmf used.

So simple fix for you for now, and I'm sure the dev team will get around to this and include in a future version once it makes sense to plan it in with other work.