Georgios Anagnostou 

It has never been possible to import these filetypes into a Trados Studio TM.  If you want them in a TM open them for translation and use a batch task to update the contents into a TM.

Thank you for getting back to me, and for your useful advice. I can assure you that importing these file types into a Trados TM was possible before installing SR2. I used to do it very often.

Georgios Anagnostou 

I'm sure you think you did this but I can assure you that you did not!  There is no mechanism in this product to import any files into an SDLTM directly apart from *.tmx, *.tmx.gz, *.sdlxliff, *.ttx, *.itd and *.sdlalign.

I have been here for over 17-years and this has never been possible since the start of Trados Studio, or before.  I also know memoQ reasonably well and have looked at the compatibility between these products in some detail over the years.

But if you still think you're right send me the files you have and I'll happily install any version of Studio you like and show you.

Georgios Anagnostou 

But I am curious enough to always have a small niggle of doubt... so I uninstalled SR2 and reinstalled SR1 and tested.  I was surprised to see that it does actually try to import them... very surprised!  Cannot tell you enough just how surprised!  But the results aren't good and nothing is actually imported:

So it actually read that there are 10 translation units, which is correct, but fails to import any of them.

However, I'm going to apologise because even this is more than I expected.  I can't check with anyone who might know from the dev team at the moment, but I will ask the question and also test a bit more.

I really am surprised!  I recall fairly recently speaking to a developer responsible for this and he explained why we could not even handle normal XLIFF never mind MQXLIFF.  Just goes to show we're always learning!

Georgios Anagnostou 

But I am curious enough to always have a small niggle of doubt... so I uninstalled SR2 and reinstalled SR1 and tested.  I was surprised to see that it does actually try to import them... very surprised!  Cannot tell you enough just how surprised!  But the results aren't good and nothing is actually imported:

So it actually read that there are 10 translation units, which is correct, but fails to import any of them.

However, I'm going to apologise because even this is more than I expected.  I can't check with anyone who might know from the dev team at the moment, but I will ask the question and also test a bit more.

I really am surprised!  I recall fairly recently speaking to a developer responsible for this and he explained why we could not even handle normal XLIFF never mind MQXLIFF.  Just goes to show we're always learning!

Paul said:

However, I'm going to apologise because even this is more than I expected.

Hi Paul. No need to apologize. As humans, we all make mistakes and we don't know everything.

Paul said:

Cannot tell you enough just how surprised!  But the results aren't good and nothing is actually imported

If you keep testing, you may be also surprised to see translation units imported into the TM. That's exactly what used to happen in my case. I don't know the reason, but it was very practical.

Georgios Anagnostou 

Well... this just gets more and more interesting.  Both the Product Manager for Trados Studio and the Senior Developer with responsibility in this part of the product are completely unaware of this.  It was never an intended feature and not even tested.

I also still can't actually import any TUs with my own testing so if you have got some files that will import I'd be very interested to see them.

However, given this was never an intended feature I'm afraid there won't be any work carried out to try and support it either so unless you get lucky again you're probably out of options.  I suggest you create an idea in the ideas site and mention that this did work for you previously, even if not by intention, and it would be helpful if it could become a supported feature of the product.  Until then I think my original response is the only way you'll get them into the product.

One more thing...I'd be interested to know if other users, like Jerzy Czopik for example, have used this in the past and were aware it was possible?

Paul 

Thanks for the mention. I indeed do work a lot with mqxliff files, but never ever tried do add them to my TMs. This would spoil my way of working, as I use my personal TMs for all customers, where only my own translations are stored. The rest is in a TM send by customer and thus I do not need to import anything there.

Thanks Jerzy Czopik ... perhaps some other user who works with memoQ can share some info on this.  Or maybe it's a remarkable discovery only Georgios Anagnostou had made!