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.

  • Search Tool - 01

    Ulrich Schramm
    • Under Community Review
    • 0 Comments
    This problem: - doubelklick a word --> Word is marked - CTRL-F --> Opens the Serach Tool Window with the marked word - Don't close the Search Tool Window, but doubleklick (mark) a different word - CTRL-F --> The Serach Tool Window don't show the...

  • Allow users to leave TM Recognizers switched on without losing Context Matches at each TM update

    Frank Lempp
    • Under Community Review
    • 0 Comments
    Since some SDL Trados Studio users take the distinction between Context Matches and 100% Matches seriously, it would be good if a user can leave TM settings like "Recognize Number" switched on all the time ... ... without losing Context Matches at...

  • Retain Studio source comments in the target file.

    Melissa Symoens
    • Under Community Review
    • 0 Comments
    Dear, We are dealing with source documents that include comments that should not be translated but that do need to be kept in the target file. However, when copying the source to the target segment, those comments (highlighted in yellow) are not taken...

  • avoid duplicates in word suggestions when typing

    Pascal Zotto
    • Under Community Review
    • 0 Comments
    Hi, Would it be possible to add some filter in order to avoid duplicates for the suggestions showing when typing a word? Let's say we want to type "information" Studio now finds "information" in our termbase and in results from exisint translations...

  • set spell check option per project or language and not globally

    Pascal Zotto
    • Under Community Review
    • 0 Comments
    Hi, It would be good if we could set spell checking option either globally per language or per project. e.g. For German Word grammar and spell checker is better but for Luxembourgish Hunspell is better. So I now have to switch to global options...

  • Better automatic search in MultiTerm when using Studio

    Ulrich Schramm
    • Under Community Review
    • 1 Comment
    I’ve two MultiTerm-Termbases open in Studio. In both I have an entry for "Ufficio Commerciale". But only one Termbase shows me a translation. Only after deleting the "old" term in the “old” Termbase, the "new" Termbase shows me the translation correctly...

  • Permanently store filters within TMs

    Burckhardt Rueffer
    • Under Community Review
    • 0 Comments
    We make extensive use of fields to organize data in our TMs. In order to export translation units from a TM, we often need to filter for conditions to be met. This works well for simple tasks but when we need extensive filters, especially when selecting...

  • Length verification when pre-translating files

    Julia Skowronek
    • Under Community Review
    • 0 Comments
    When creating a Project and applying the Batch-Task Pre-translate files the CM- and 100%- matches are confirmed even if there has been set a length restriction in the QA checker. After running the task the too long translations for this particular project...

  • Split sdlxliff in equal portions...

    Stepan Konev
    • Under Community Review
    • 0 Comments
    ... just the same way as multi-volume archives do. Say Trados could skip 100% matches and repetitions for calculation purposes and then equally divide all other segments (fuzzy and brand new) by any requested number. It would be even better being able...

  • Add comment on content selection or range

    Patrick Andrew Hartnett
    • Under Community Review
    • 0 Comments
    API enhancement to the Sdl.TranslationStudioAutomation.IntegrationApi.Document Expose a new method in the public API to add a comment on the selected content in the source or target segment and/or include the ContentRange as an argument