The Trados cloud platform will be undergoing maintenance on Saturday, 9th May 2026 between 05:00 to 17:00 UTC. During this time, you will not be able to log in to the Trados platform.

Alternatives to MultiTerm?

Hi.

I'm deeply unhappy with MultiTerm, I find it buggy, clumsy and not full-featured enough. My priority is not to have terminology available in Studio while translating -- the main reason for creating MultiTerm, I suppose -- but to have a fully-fledged terminology solution to store my terminological work, possibly with Studio-compatibility.

Which terminology solution do you know which could possibly interface with Studio?

Thanks

  • Hi Marco,

    XBench works very well. I have an XBench project that I just call "default project" that I load when I boot my computer in the morning. This project loads my termbases, which currently contain just under 1.8 million entries. To use it in Studio, just highlight the term you want to look up and hit Ctrl+Alt+insert (or whatever shortcut you define) and it gives you an instant response (because the whole lot is always loaded in RAM).

    I find it helpful to use MultiTerm (or any CAT tool's built in termbase system) only for enforcing terminological consistency within each individual project. Too many terms in MultiTerm results in nearly every word in source segments been flagged as a term, which is not what is wanted, quite apart from its problems of performance.

    I have been working with various CAT tools since 2005 and long ago concluded that massive termbases must be dealt with outside, not within, CAT tools.

    There are also some very good QA features in XBench, which can be invoked with the XBench plugin for Studio.