Hi Pavel Tsvetkov ,

First thing to come to my mind: Have you checked the language combination of the TMX and the TM? They both should match?

You can check the language combination of the TMX if you open it with an Editor. In notepad++ would look like this (en-GB as Source and es-ES as Target languages):

Hi Jesus,

Thank you for your suggestion.

I have just checked with the GB-BG variant of the accepting TM and the result is the same. From experience, having a different variant of English (US, GB) in the accepting TM has never precluded Trados from importing a .tmx file. This is how my four EU translation memories (US-BG, BG-US, GB-BG, BG-GB) have grown so much over the years while using the same EU documents which are not offered in the US variant anyway.

So, there must be another culprit but I am not sure what it is.

Best regards,

Pavel

Hi Jesus,

Thank you for your suggestion.

I have just checked with the GB-BG variant of the accepting TM and the result is the same. From experience, having a different variant of English (US, GB) in the accepting TM has never precluded Trados from importing a .tmx file. This is how my four EU translation memories (US-BG, BG-US, GB-BG, BG-GB) have grown so much over the years while using the same EU documents which are not offered in the US variant anyway.

So, there must be another culprit but I am not sure what it is.

Best regards,

Pavel

Pavel Tsvetkov 

If there is one, try remove the o-tmf attribute altogether.  It's not needed at all, but it often causes import problems.

Hi Paul,

Thank you for your message.

Where can I find said attribute and how can I remove it?

Best regards,

Pavel

Pavel Tsvetkov 

Sorry... I assumed you'd know that... my bad.  In the header:

Hi Paul,

Is this the one:

Just delete it and save the file?

Best regards,

Pavel

Yes, but delete the whole thing.  So delete this string:

o-tmf="SDL TM8 Format"

Save it and run the import again.  Might not help as some values seem ok, some do not, but worth trying.

Hi Paul,

1. I deleted the string o-tmf="SDL TM8 Format" and the import completed successfully.

2. However, since you mention that some of the values do not seem to be OK, I am wondering if I should import the .tmx in the remaining of my EU TMs. Could that mess up my TMs that I have been compiling over the last several years? I still keep the original versions of the TMs so I could alternatively just restore the original version of the TM that I have just imported the .tmx file to...

3. What values do not seem OK? I created the .tmx file like I always do: from a TM that is the result of the alignment of the Engilsh and Bulgarian version of a document downloaded from the EU portal:

 – EN version of Resolution (EU) 2022/1702

 – BG version of Resolution (EU) 2022/1702

Best regards,

Pavel

Pavel Tsvetkov 

Pavel Tsvetkov said:

What values do not seem OK?

I'm only referring to values of the o-tmf attribute.  In your case the value was "SDL TM8 Format", but depending on where the TMX was created this value could anything.  Sometime Studio stumbles over this value... I don't know why... and sometimes it doesn't. So you can safely remove this whole string for your imports and just avoid the problem.

Pavel Tsvetkov said:

I am wondering if I should import the .tmx in the remaining of my EU TMs. Could that mess up my TMs that I have been compiling over the last several years?

Why not.  The TUs will be the same.  We don't use the o-tmf attribute for anything, other than apparently checking to see if we like where it came from.

OK, Paul!

Thank you for your help!

Best regards,

Pavel

Hi all,

I am not a real expert, but just to let you know (maybe it is useful). I am using Trados Studio 2021. I had the same problem as Pavel Tsvetkov. I tried to follow Paul's instructions. I found the string o-tmf="TW4Win 2.0 Format" to be deleted and I deleted it. But the import failed again. I then tried to replace this string with o-tmf="SDL TM8 Format", and the import was successful!

Best regards

Carla