I use it on a 64-bit PC and it works allright. I often encounter small issues, but they can generally be solved fairly quickly. There are many other issues that make Trados slow and hard to use with confidence. Not 64-bit PCs. Unless you work on very very large projects.

For what it's worth, I have completely given up on this issue being resolved within my working lifetime (I'm retiring in 2026). My solution is to retain the use of Trados Studio for compatibility with the workflow of clients who use it, but to import the sdlxliff (the segmented one in the directory \projects\project name\language-variant) into MemoQ, together with the memories. This is a quick operation that means that I work in an environment that does not crash, is fast and has much better "intelligent" search and replace for faster post-editing.

When the translation is done, just export to the same directory, open it in Trados, and deliver to your client. All QA and all other processing is done in MemoQ and XBench.

I am currently doing a project with around 450,000 repeated segments and I dread to think of the problems it would cause in Studio.

I already thought of doing the same, but I was not sure to be able to rely on a perfect compatibility of xliff files.

Thank you

I can confirm that there is no problem with compatibility. The only thing you need to be aware of is that when importing any sdlxliff files created from Microsoft Office documents, you will get a warning (not an error) saying that a filter has been used for which MemoQ cannot display formatting and that this formatting will now be handled as tags. All this means in practice is that where you might, for example, see a part of a sentence highlighted in yellow in Studio, it will be surrounded by tags in MemoQ. Once it is exported back to Studio, it will show as yellow again.

There is one other thing to be aware of. In Studio, auto-propagation will automatically insert changes of numbers or tags, which I consider to be Studio's unique selling point. In MemoQ these are automatically inserted as high matches but not 100%. To compensate for this in MemoQ you need to open up the TM settings and check "return an exact match if only recognized numbers are different". Then they will be automatically inserted as 100% matches or you can run pretranslate occasionally to compensate for the fact that these segments don't auto-propagate.

Just had to buy memoQ a couple of days ago, for two new clients who work with it, and still exploring it. If Studio remains, IMHO, far more ergonomic, memoQ is far more fast and reliable at this point of my experience. Also, I can find some more features in it and customization options. Even real time preview, that never worked well in Studio since 2009, works fine in memoQ.

That just shows how Studio does not evolve for a couple if years. Or, more specifically, how RWS puts efforts on useless features such as cloud functions, at the expense of long time issues fixing or long time reqested new core fonctionalities.

It's a pity, since I really like Studio, but it sounds like if RWS does not listen to its user base. In the same time, competition progresses.

Interesting to hear you do this as I do, too. Almost all my clients run Studio and I do everything in memoQ, exactly as you describe. Plus I also provide Studio support for them now and then, especially regarding terminology handling, or rather the lack of it :).

As to that 100% match propagation, I think it's the only thing I do like about Trados. I'll be using your tip for memoQ. The need to regularly run pre-translate here is a pain.

Interesting to hear you do this as I do, too. Almost all my clients run Studio and I do everything in memoQ, exactly as you describe. Plus I also provide Studio support for them now and then, especially regarding terminology handling, or rather the lack of it :).

As to that 100% match propagation, I think it's the only thing I do like about Trados. I'll be using your tip for memoQ. The need to regularly run pre-translate here is a pain.