You are currently working on UAT 

This place is where you can suggest, discuss, and vote on ideas. If you want to create an idea for an other related product choose the appropriate group on this page.

When you select to create a new idea, there are a few things you can do to ensure RWS Development and other community participants understand the idea. See here for Idea best practices.

  • Create return package task should contain the "Translation count" task

    • Under Community Review
    • 9 Comments
    When working with translation packages, quite often you need to run a translation count task before the delivery, as Trados Studio not always updates the wordcount in the project. Would the "Create return package" task already include the translation...
  • Workiva integration

    • Under Community Review
    • 0 Comments
    More and more banking and financial institutions are using Workiva to produce their regulatory and prudential documents. Facilitating Trados Studio integration with Workiva will make many translators' lives easier. At the moment, we need to export content...
  • Add "PE" for "post-edited" next to 100% pre-translated segments that were originally machine translation

    • Under Community Review
    • 6 Comments
    Wouldn't it be practical for translator and project manager alike to be able to distinguish between those 100%-matches that were made from scratch and those that were post-edited from NMT? It would help to recognize the potentially more direct translations...
  • Enable merging segments by default

    • Not Considering
    • 0 Comments
    Merging segments across paragraphs should be enabled by default, also when translating single files. It is annoying that the options "Allow source editing" and "Disable merging segments across paragraphs" have to be changed in each project.
  • Selecting termbase or termbases to add your terms on-the-fly

    • In Progress
    • 2 Comments
    It's really tedious to have to change your primary termbase several times during translation when you have several various termbases added to your project. In my projects I often use 3 termbases for cuisine, general terms and travel terms, and I found...
  • Bring back "Use TM from previous analysis"

    • Under Community Review
    • 1 Comment
    Trados 2007 used to have an option "Use TM from previous analysis" It allows us to determine if it was more cost-effective to process the files in order. It would be a useful feature to have this during the project preparation under the Task Sequ
  • Locked Segments in Studio Analysis Statistics of Files View

    • Planned For Future Release
    • 2 Comments
    After activating the option "Report locked segments as a separate category", locked segments will be reported correctly as locked segments in the analysis report (and also in the filter results of the Editor view), but not in the Analysis Statistics tab...
  • Penalty for single word terms

    • Under Community Review
    • 1 Comment
    It would be nice to be able to assign a penalty to single word terms, as these are prone to be erroneously populated in pre-translation and auto-propagation. A penalty with configurable number of words would be even better.
  • Auotmatically adding TM as AnyTM when appropriate

    • Under Community Review
    • 0 Comments
    The current behavior when attempting to add a TM that doesn't match the project languages is that Studio will give a warning message and finish by saying "Consider adding this TM via AnyTM". Instead of this, I would like to have Studio ask whether I want...
  • Studio analysis - detailed retrieval for each TM

    • Under Community Review
    • 0 Comments
    When I use more than one Translation Memory in my projects, I miss an option for analyse files that tells me from which TM are the fuzzies and pretranslated segments retrieved. Like a breakdown for each memory. I think this feature would become very handy...