Idea Delivered Partially

Setting to delivered partially for cloud project flows but aware this is not available with file or server-based projects (not without third party solutions from the Trados ecosystem).

Only include target language-specific entries from a termbase when creating project packages

For some clients we work with large file-based termbases and a lot of target languages on a regular basis. When creating project packages, Trados Studio includes the entire termbase with all target languages
instead of creating smaller termbases that each exclusively contain the relevant language pairs, with the major downside being that unpacking and opening the project in Studio takes a lot of time.
This especially holds true for SDLPPX packages downloaded from Trados Enterprise and processed in Trados Studio, given that those packages include the XML+XDT instead of the SDLTB file,
thus adding extra time for Trados Studio for the conversion.

I think it would be quite handy to add an option to only include the target language-specific entries from a termbase in the package creation options.

Julian Hamm
  • in reply to Bernhard Hoell

    Hi Bernhard, thanks for the feedback. I guess what I would ask is if the process can be reviewed somehow. Downloading a 17.5k Termbase in every package obviously is not the goal.

    - Could the users work with Terminology online? Trados Terminology is setup to be used online tightly integrated with Studio. If you don't include the package, we can include a seamless link to the online TB. (would need users to be able to login to your tenant).

    - If the above is not possible: could the termbase be provided once and then only updated in regular intervals (we added the option to not download a TB inside the package now, as a choice to linguists, so they don't have to wait 45 mins)

    - Work with Support to see why it takes 45 mins, seems excessive.

  • in reply to Luis Lopes

    Thanks Luis, makes sense - on the other hand we have here a situation where the users in Studio need to wait more than 45 minutes for the project to import - we had to ask them to disable the termbase to be imported as it would take too long - we have a 17.500 entry termbase with 35+ languages in the project.

  • in reply to Bernhard Hoell

    A Studio package in a cloud project will contain the project languages in the termbase. Not just the language a linguist downloads. Reason being, we create the project termbase during the workflow, not on download. If we moved this to the download package process, a user would wait for many minutes until the export process completed.

  • in reply to Daniel Brockmann

    Hi Daniel, we have logged a support ticket on this as even for a translation into just one language it would export all the languages into the studio package. What am I missing?

  • in reply to Daniel Brockmann

    I don't think this is the solution a lot of us were looking for...