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.

  • 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

Comment
  • 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

Children
No Data