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.

  • Enlargement of the "Close document" symbol in the Editor

    Christina Clausing
    • Under Community Review on
    • 2 Comments
    Nearly every time I want to close the document I have finished translating, I miss the tiny "Close document" symbol and hit one of the expandable elements to the right instead (filters, previwe, useful tips, ...). I then have to close the pop-up before...

  • Be able to run Terminology verifier with multiple termbases, not just the default termbase

    Naroa Lasarte
    • Duplicate on
    • 0 Comments
    Is it possible to run QA verifying multiple termbases at the same time? As far as I am concerned, it just lets me run the QA just with the default termbase.

  • Different colour for edited 100%-matches in bilingual review document

    Daniela Bartaky
    • Under Community Review on
    • 0 Comments
    We often have to edit 100%-matches and CMs. In the review document, edited matches still show up green, just the same as untouched ones. This is inconvenient, as the reviewer then has to read all green lines. Please implement a different colour for mathces...

  • Merge previously merged segments

    Seraina Hartmann
    • Idea Delivered Partially on
    • 1 Comment
    Dear development team I would appreciate the option to merge a segment with another segment that has already been merged before: Segments 152 to 155 = 1 sentence: When you merge segments 152 and 153, the remaining two segments (154 and 155)...

  • Add "Sentence case" to "Change Case" feature

    Will Mowat
    • Under Community Review on
    • 1 Comment
    Under Advanced -> Change Case you can change the case of highlighted text in various ways. The one very useful option that's missing is "Sentence case", i.e. making everything lower case and the first letter upper case.

  • XML filter - A new setting request for ignore/skip a specific section of the DOCTYPE declaration

    Maki Jay
    • Under Community Review on
    • 2 Comments
    When creating a new TRADOS project for an XML file as a source, I would like a setting that ignores the DOCTYPE declaration at the top of the source file, such as below. ========================== <!DOCTYPE view [ <!ENTITY mdash "&#x2014;"> <...

  • QA checker : make it checking the presence of a non breaking space

    Manuella Lange
    • Idea Delivered Partially on
    • 5 Comments
    Currently we can check that there is a space before the French punctuation marks (!:;) . But we can not check that the space is indeed a non breaking space as required by the language. My personal tweak is to filter on the punctuation and to manually...

  • Count affected TUs before batch editing TMs

    docConsult Support
    • Under Community Review on
    • 0 Comments
    Batch editing TMs can be risky, especially when a wrong filter is selected. An indicator counting all affected TUs before proceeding would help avoiding mistakes. There might have been such a feature already, back in Studio 2011.

  • More efficient use of the QuickPlace function

    Danilo Lopes Barbosa
    • Under Community Review on
    • 0 Comments
    The best way to explain what I mean is through an example. In the segment: two Placeables were identified. When I'm typying the translation, and I reach the point to insert the first Placeable ("PULSUM"), I type "CTRL + ," and a list containing the...

  • True AutoText

    Former Member
    Former Member
    • Under Community Review on
    • 0 Comments
    I believe that the AutoText feature in Studio is a useful one. Nevertheless, my experience has shown that many users do not use it. My suggestion is to make AutoText truly automatic so that everyone uses it straight away. Create a dialog box for AutoText...