Under Community Review

Provide a full fledged converter from TTB to SDLTB

Many user will still be on 32-bit versions of Studio and would need a SDLTB to work. TS2026 works only with TTB, so when you get a project, SDLTB will be converted internally to TTB. However, in a case the customer or anyone else would ask for an amended termbase after project delivery, you have no chance to do that. So an exporter for TTB is needed.

Jerzy Czopik

  • Couldn't agree more with what's being raised here. The move to TTB in Studio 2026 solved some real problems, but it also quietly took away things translators and terminologists relied on every day — there's no way to open a TTB and simply look at what's inside, conversion only runs one file at a time, and building a new TTB from a plain bilingual list means hand-crafting an XDT definition and an XML import file first. That's a reasonable ask for a developer, but it's simply not realistic for the average linguist or terminology manager trying to get work done.

    I ran into this same wall on real projects, so I built a companion tool to close the gap while Studio's native tooling catches up (although with my tool, I guess Trados developers do not really exert any more effort into this, now that this already exists). It gives you a real termbase editor and viewer for TTB files — you can open one and actually see and search every entry, including image and media fields rendered right in the grid, something the older SDLTB workflow really offered cleanly but now it is not available in the TTB format anymore. Conversion runs in true batch mode, so a folder of SDLTB files becomes TTB (or the reverse) in one pass instead of one file at a time. And creating a brand-new TTB from a bilingual TM, spreadsheet, or termbase export is just a straightforward import — no XDT authoring, no manual XML wrangling.

    It's built for speed, too — termbases with tens of thousands of entries open and save in seconds rather than minutes, so it holds up on the large, real-world resources agencies and enterprise teams actually work with.

    I've recorded a short video showing it end to end and I'm happy to share it here if it's useful to the thread. Hoping this helps in the meantime, and hoping Studio brings native support for this eventually too, though not needed I would say after all the efforts I have put into creating this APP.



    I hope you all like this APP, as I built it while testing Studio 2026.

    Sameh Ragab

  • Yes, because otherwise the only option is to open the package with both versions, work in 2026 then do the final verification with 2024... That's not satisfactory because, for example, any changes made to the ttb are not present in the sdltb... You also have to juggle the termbases and/or files...