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.

  • Remove penalty on capitalization

    Daria Aleshkina
    • Under Community Review
    • 1 Comment
    Hi, It would be great to have a function that would allow removing penalties for capitalization. For certain projects it would allow having 100% matches for capitalized content instead of fuzzy matches, which could help save a lot of time.

  • Ability to add a comment to a segment without translation

    Daniel Hug
    • Under Community Review
    • 0 Comments
    Sometimes a segment has to stay untranslated, and it would be good to be able to add a comment to that segment, e.g. for bilingual reviews, so that other people in the workflow understand why it has been left untranslated. Daniel

  • Option to include/exclude repaired/fragment words from analysis

    Lieven Lannoo
    • Planned for Future Release
    • 0 Comments
    While the Repair function and the Fragment Matches have their advantages, we don't always need this information in the analysis reports. It would be handy to have an option to include/exclude the repaired/fragment word details in the Analysis Files Setting...

  • Ignore QA messages permanently across workflow

    Andreas Schmidt
    • Under Community Review
    • 0 Comments
    It would be useful if QA messages ignored e. g. by the translator would still appear as ignored when the proofreader opens his/her package and starts work. Maybe this information could be transported across the workflow in the sdlpj-file or another...

  • Explain what is delivered and in which version

    Michel Farhi-Chevillard
    • Under Community Review
    • 0 Comments
    I'm noticing that ideas get tagged as "delivered" or "partially delivered" but with no explanation, no mention of what minimum version supports it, etc. Please make it mandatory for SDL employees to fill this information.

  • Term Recognition Window - Make the tooltip break (instead displaying in single line)

    Burim Bektesi
    • Under Community Review
    • 0 Comments
    Can you please make the tooltip break? When hovering over an entry in the term recognition window, a tooltip opens, but goes in one line to the end of the screen and beyond. Expected behaviour: The tooltip should break, displaying a box rather...

  • change color of progress bars in file view

    Pascal Zotto
    • Under Community Review
    • 0 Comments
    Hi, Could you please add an option to change the color of the progress bars in file view (x% completed) It would be nice to be able to define colors for maybe every 10% step. 0-9% = red by default (all default colors can be changed by user) 10...

  • Enable text insertion cursor to blink permanently

    Former Member
    Former Member
    • Under Community Review
    • 5 Comments
    When I'm typing in the target segment, the cursor stops blinking after about 5 seconds. After that it becomes solid, partially obscuring the last character, especially if it's an l, i or t. It would be really helpful if the cursor could be set to blink...

  • Spellchecker functionality

    Jon Kittilsen
    • Under Community Review
    • 0 Comments
    The spellchecker using the MS Word dictionary works quite well, but I had hoped that the 2017 version of Studio would come with an Undo function. When spellchecking there is a lot of "Ignore All", and it is very easy to make a mistake, especially if the...

  • Add info about termbase used for QA check to the report

    Luciano
    • Under Community Review
    • 0 Comments
    Since you can change the termbase against which you perform your QA check it would be helpful to know which termbase was used for the speficic QA check you are reading. Similarly, the analysis report lists the TMs used for the analysis.