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.

  • Enable optional whitespace normalizing in IDML files

    • Under Community Review
    • 1 Comment
    Changing the whitespacing in InDesign source documents leads to leverage loss. However, if the client is not willing to pay for the adjustment of the resulting high fuzzy matches, we confirm and lock them as they are, since the whitespacing is taken care...
  • Add independent source and translation pairs directly into memory

    • Not Considering
    • 1 Comment
    It would be very practical if we could add independent source and translation pairs in any memory. Even when adding one or two segments to a memory, we need to use a file such as Word or Excel or create a dummy project. Entering them directly into the...
  • "While you project"

    • Under Community Review
    • 0 Comments
    Here's an idea: employ a better proofreader for your interface. And before you do that, correct the "Please wait while you project is being prepared…" typo.
  • Requently used languages

    • Under Community Review
    • 2 Comments
    There should be the possibility to remove languages from the list of requently used languages.
  • Sorting parser rules

    • Not Considering
    • 2 Comments
    Dear development team, would it be possible to add a sorting feature to the parser? It would be helpful to be able to sort the rules according to their properties, rather then just using the "Search for" field. Sorting is available in the Reports...
  • Option to Display Fragment Matches even if an Exact TM Match is Found

    • Under Community Review
    • 0 Comments
    Currently (Studio 2019 SR-1 CU 15), fragment matches are not displayed if an exact match is found. However, when working with "penalized" reference TMs or machine translation proposal TMs, it would be helpful to get fragment matches from "real" TM content...
  • Define spelling of language codes yourself

    • Under Community Review
    • 0 Comments
    We are using a CMS and it expects "en-gb" as the language code for English XML files. But Trados Studio only generates files with "en-GB". So it would be great to be able to define the spelling of the language codes yourself.
  • Filter for mixed-source language files

    • Under Community Review
    • 0 Comments
    Dear Community! 1. would highly appreciate if the next Studio Update included a feature for filtering mixed-source language files by language. We often come across documents drafted in two, even three languages. In most cases, modifications are added...
  • Change to default Japanese segmentation rules regarding double quotation marks after full stops

    • Under Community Review
    • 3 Comments
    Currently, with the default segmentation rule for Japanese, any quotation mark (") after a full stop (such as 。) is included at the end of the previous segment, rather than at the beginng of the next segment. However, this behavior is often inappropriate...
  • Improve fuzzy matching for single word segments

    • Under Community Review
    • 6 Comments
    Currently this is far from optimal, resulting in irrelevant matches as seen below. Even a no match situation would have been much better.