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.

  • Add support for XSLT 2.0 or 3.0 in XML preview

    Daniel Hug
    • Accepted, Not Yet Planned on
    • 0 Comments
    Currently Trados Studio supports XSLT 1.0 (this is December 2021 now). XSLT 2.0 became recommended in 2007. XSLT 3.0 became recommended in 2017. It would be good to support at least XSLT 2.0, which has many advantages over 1.0. Daniel

  • "While you project"

    Adrian Komiński
    • Under Community Review on
    • 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.

  • Fix flag designs/patterns

    Michael Bauer
    • Under Community Review on
    • 0 Comments
    There are several issues with the flags representing locales which should be fixed. In no particular order: - remove the inset flags, in many cases, the inset is impossible to make out (English-Europe) or plain wrong (Scottish Gaelic is the *Irish*...

  • Option to Display Fragment Matches even if an Exact TM Match is Found

    Christine Bruckner
    • Under Community Review on
    • 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...

  • CTRL+, activates segment

    Daniel Hug
    • Under Community Review on
    • 0 Comments
    When selecting text in a non-active segment, the segment stays non-active. Once the user starts typing, the segment is activated and the selected text is replaced by the typed text. I would like to see this behavior also when text is selected and CTRL...

  • Filter for mixed-source language files

    Yulia Kovalskaya
    • Under Community Review on
    • 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

    Tomonori Shimada
    • Under Community Review on
    • 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...

  • Default behaviour in translation status - can it be changed?

    Özge Ünlü
    • Under Community Review on
    • 18 Comments
    Hello, When finishing translation in Trados Studio, the default behavior is that the project status changes to "In review", the progress bar of the translation is reset to 0. We would like to know if we can change this default behaviour and avoid that...

  • Generate in Advanced display filter 2.0 should work also in case of virtually merged files

    STEFANO DE ASTIS
    • Under Community Review on
    • 0 Comments
    Generate in Advanced display filter 2.0 is quite useful, allowing to export the filtered segment in a separate XLIFF file. However, it does not work when multiple files are opened at the same time as virtual merge, In that case the segments are filtered...

  • Improve fuzzy matching for single word segments

    Spiros Doikas
    • Under Community Review on
    • 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.