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
Parents

  •    already mentioned that this is working in the cloud and I can remember the customer for which I logged the case. But I also agree with   who found out that the feature doesn't work as expected. I would also have expected a Studio package to contain only bilingual termbases. However, if the project contains more or all target languages, the feature no longer helps the user. We had also observed loading times of approx. 45 minutes and these are probably unavoidable with termbases with a large number of languages. This makes the work very time-consuming, especially if the package does not contain that many words for translation.

Comment

  •    already mentioned that this is working in the cloud and I can remember the customer for which I logged the case. But I also agree with   who found out that the feature doesn't work as expected. I would also have expected a Studio package to contain only bilingual termbases. However, if the project contains more or all target languages, the feature no longer helps the user. We had also observed loading times of approx. 45 minutes and these are probably unavoidable with termbases with a large number of languages. This makes the work very time-consuming, especially if the package does not contain that many words for translation.

Children
  • in reply to Achim Herrmann

    Thanks    - that particular change is not live yet. From what I know, it should go live in the next few week(s). I will also repeat that it's not good practice to work with terminology in offline workflows like this, as it creates unnecessary burden for the CAT tool downstream to do terminology imports for every package in every language, even if they are bilingual. It's better to see how online access to termbases can be given to the vendors and overall supply chain. But hopefully we'll soon see this enhancement anyway, where termbases will be bilingual for each offline package rather than multilingual like now. Thanks, Daniel

  • in reply to Daniel Brockmann

    Hi , I would appreciate if we could share the termbases online. For this to work however, unknown users (that do not have a user account in the Trados Enterprise server) would need to be able accessing the termbase. If you can cryptographically share a key with them via the LSP package that ensures that those are authenticated and associated with the vendors credentials and have exclusive access to the termbase as long as they are working on the given project, this would be highly appreciated. LSPs usually do not want to expose their translators to the companies tasking them - we could not take the burden to create company domain registered users for them (which is a requirement). If this is feasible and makes it into the product, I would be very happy :) . Thanks, Bernhard

  • in reply to Luis Lopes

    Hi  
    Thanks for sharing this information! I don't quite know if the new feature really solves the problem that is being discussed in this thread. After downloading some sdlppx packages (e.g. English>German) from Trados Enterprise and importing them into Trados Studio, I found that the packages still included the entire termbase with ALL languages rather than only listing the terms for the selected language combination.
    What I actually envisioned the new feature to enable is to only include the English>German termbase entries for an English>German sdlppx package - plus, potentially in a future release, how recently put it: "I’d like to see a solution that went even further and created a termbase that only contained the terms that would be found in that project for each language in the project."

    Also, I find the feature description to be quite vague: "When choosing to include termbases when downloading a package, we now only include termbases that contain language pairs corresponding to the selected tasks". It reads as if only termbases were included that match the language combination of the task without actually removing the languages that are not needed for the individual package.

    Thanks in advance for your feedback!

  • in reply to Julian Hamm

    Hi , I agree with on this.

    I did raise a support ticket on this issue because providing a large termbase resulted in taking 45 minutes plus for importing a Studio package on the Translation PJMs side because of redundant 38 languages being part of the Termbase export. If the languages are still part of the export, this does not seem to solve the particular issue I raised.