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.

  • Provide shortcut for direct term insertion

    Spiros Doikas
    • Idea Delivered Partially on
    • 1 Comment
    Currently, one needs to start typing in order to see the term suggestions. The old functionality of ALT+arrow keys appears defunct. It would be useful if we could still use it to enter terms. I.e. ALT+down arrow to enter current term, ALT+ right arrow...

  • Prepare files for translation step

    Filip Jensen
    • Under Community Review on
    • 0 Comments
    Most of my files should be translated to 5 languages. It would be beneficial to have an optional "Prepare files" step where I could lock certain segments (usually because they should not be translated), or change the source text before creating projects...

  • API enhancements / Verification Messages / IntegrationApi.Document

    Patrick Andrew Hartnett
    • Under Community Review on
    • 0 Comments
    There does not seem to be a way to access the messages from the IntegrationApi.Document, that are reported through the message service -> generated from the project API batch tasks (Verify). The message service is accessible from the batch task / GlobalVerifier...

  • Export of the Analysis Statistics (Project View)

    Julia Skowronek
    • Under Community Review on
    • 0 Comments
    The only project analysis across all project languages is the Analysis Statistics in the Project View. To evaluate the matches further and calculate costs of the whole project an export function to Excel would be great. The Reports View only offers...

  • Automatically suggest or build term entries while working in the Studio editor

    Agenor Hofmann-Delbor
    • Under Community Review on
    • 0 Comments
    Some phrases tend to appear more frequently in the document, and not all users build their term bases on the fly. What I'm suggesting here is more or less what AutoSuggest is already doing, but simply using this information to automatically build a termbase...

  • Add the name of a MT provider in the Translation Results window.

    Wojciech Matyszkiewicz
    • Under Community Review on
    • 1 Comment
    I generally use 3-4 MT engines when translating, but I've found that depending on the type of the text one engine may be more reliable than others. The problem is that in the TR window you can't see which engine the results come from unless you click...

  • Allow Copying and Renaming Files in Files View/Projects View

    Jesse Good
    • Under Community Review on
    • 0 Comments
    The Files and Projects View in Trados Studio looks a lot like the explorer window under Windows. However, there is no way (I know of) to copy the file/project name or rename it with Trados Studio. It would be great to have this functionality.

  • Smarter plural handling of TM matches

    Michael Bauer
    • Under Community Review on
    • 0 Comments
    Currently the Studio TM isn't too smart when it comes to plurals. Let's say I have a file with strings like these and their corresponding translations: 1 month : 1 mhìos 2 months : 2 mhìos 3 months : 3 mìosan 4 months : 4 mìosan 11 months :...

  • Make term recognition work in real-time when auto propagating

    Takayuki Osato
    • Under Community Review on
    • 0 Comments
    It appears that term recognition does not work in real-time when the auto-propagation feature propagates through confirmed segments to the next unconfirmed segment. I need to go back a segment and then return to the current segment for the terms to be...

  • Update Studio and Multiterm simultaneously / SDL Update manager

    Agenor Hofmann-Delbor
    • Planned for Future Release on
    • 1 Comment
    The current situation is that Studio only updates when you run the application. The MultiTerm update is not synchronized with Studio in any way. It would be great to update both applications in one go. OR(!) change the updating policy entirely. Instead...