• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 431 subscribers
  • Views 489 views
  • Users 0 members are here
Options
Related

New termbase view in Trados Studio 2026 does not offer any possibility to edit termbase.

Katharina Schuhmann

Hi,

I've just downloaded the 2026 release of Trados Studio, especially to benefit from the 64-bits build (finally!) and to experiment with the new termbase view. Unless I'm doing something wrong, however, I'm very disappointed with this view. It only offers termbase management options, but nothing to really edit termbases, i.e. add new terms, change terms, etc.

Is management the only use case here? That would mean we'd have to everything related to editing terms in the Editor view? Seems strange to me, especially since the email notifying me that the 2026 release is now available claims that MultiTerm is no longer needed for file-based termbases.

Any clarification would be appreciated! Slight smile

Regards,
Katharina

PS: This is what the termbase view looks like with a termbase opened:

Screenshot of the Trados Studio termbase view showing options like open termbase, create termbase, import terms, export terms, and settings. The main area displays a termbase in German and French.

Generated Image Alt-Text
[edited by: RWS Community AI at 7:02 AM (GMT 1) on 29 Jun 2026]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    And ... I just noticed that the new MultiTerm version cannot handle the new .ttb files from the integrated Studio termbase view, whereas Studio 2026 cannot handle the old .sdltb files. As it is then, Studio 2026 is quite useless for real terminology management because you'd always have to open a translation project first. Managing your termbases in MultiTerm 2026 is also useless because you cannot use them in Studio 2026 without converting them to the new format first. Seems like a huuuuuge waste of time.
    emoji
Reply
  • 0

    And ... I just noticed that the new MultiTerm version cannot handle the new .ttb files from the integrated Studio termbase view, whereas Studio 2026 cannot handle the old .sdltb files. As it is then, Studio 2026 is quite useless for real terminology management because you'd always have to open a translation project first. Managing your termbases in MultiTerm 2026 is also useless because you cannot use them in Studio 2026 without converting them to the new format first. Seems like a huuuuuge waste of time.
    emoji
Children