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.

  • Pre-assign internal fuzzy leverage values to segments

    Johnny Speiermann
    • Under Community Review
    • 0 Comments
    The larger a project the more internal fuzzy matches, and the number of segments with a high fuzzy match value can be quite big. To save time during review it would be great to be able to start the project translating 0% matches that will not later...

  • Add visual distinction to CM/100% TC and fuzzy TCs

    Jurgita Kunsmanaite
    • Under Community Review
    • 2 Comments
    Currently, for segments containing track changes, segment status appears as "TC" and their full true TM status is visible only if looking at Translation Result window (as there we can see if it is CM/100%, or a fuzzy). It would be helpful to have some...

  • Ask users if they really want to save the file without running Verification / Spellchecking

    Former Member
    Former Member
    • Under Community Review
    • 1 Comment
    Alternatively - this could be applied when generating target file or a return package. "Are you sure?" messages are always annoying, but this one would be a fully justified one. Example: "You didn't run QA Verification against this file. Are you...

  • Handy "tag counting option" for invoicing purposes

    Caroline Rösler
    • Under Community Review
    • 1 Comment
    I would love to see for invoicing purposes an easy to use "tag counting option" as I would like to charge more for tag-overloaded texts which use to be much more labour-intensive.

  • Lock TUs in the TM

    Ulrike Michiels
    • Accepted, Not Yet Planned
    • 2 Comments
    It would be great to be able to lock a translation unit in the TM, thus making sure that it will be auto-propagated as perfect match and always remain exactly the same.

  • Add support for JSX in the Markdown filetype

    Paul
    • Under Community Review
    • 0 Comments
    It would be a good enhancement to support *mdx files in the markdown filetype: https://mdxjs.com/ The current filetype supports these files well apart from the jsx parts: https://reactjs.org/docs/introducing-jsx.html Seems like a worthwhile enhancement...

  • Editor : allow odd font sizes

    Olivier
    • Under Community Review
    • 1 Comment
    Hello! In Studio 2022, in the editor configuration, font sizes can only be adjusted in increments of 2 : font sizes 10, 12, 14, and so on. Sometimes, size 14 is too big and size 12 is too small. It would be nice to also have the "odd" font sizes...

  • Different color settings and layout for Project Settings and File - Options

    Former Member
    Former Member
    • Under Community Review
    • 0 Comments
    In my experience, users often mix up Project Settings and File-Options. The reason for that is simple - both trees of settings look very similar and it could be confusing for someone not familiar with the software. I would like to suggest introducing...

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

    Wojciech Matyszkiewicz
    • Under Community Review
    • 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...

  • Delete target segments custom batch task

    Spiros Doikas
    • Under Community Review
    • 0 Comments
    In some cases files imported for translation may have the source text copied to target. A batch task to empty those segments (with options, i.e. only segments were source and target are identical; excluding locked segments, apply to all unlocked segments...