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.

  • Allow to hide some ressources for a specific target language

    Christophe Willefert
    • Under Community Review
    • 0 Comments
    It would help Passolo allowed us to hide the content for a specific language Example : we do not want to translate some resx contained in a .Net Dll as the targert language is not concerned by a specific module. So, we should be able to hide the...

  • Differentiate icons for Passolo editions

    Anna Kadlecik
    • Under Community Review
    • 1 Comment
    usecase: I work with a translation bundle and a project (professional or collaboration edition) on the same computer. The icons of these two programs look the same in the taskbar - very confusing. Would it be possible to Differentiate them? Thank you...

  • Add source and target text and sort function on Check results window (for inconsistent translation errors)

    Sophia Wessin
    • Under Community Review
    • 0 Comments
    Currently, when you check strings in Passolo (2016 CU11) for inconsistent translations, you get an - from the source text point of view - unsorted (and unsortable) results list containing only the string ID and the error category, in this case "Inconsistent...

  • Show number of occurrences in the Pre-translation dialog

    Lars Hjorth
    • Under Community Review
    • 1 Comment
    When pre-translating strings it would be a great help to know how many times each suggested translation is used. This will give a quick hint as to which alternative translation would be the most relevant to choose. See screenshot below for suggested...

  • Make "Find All" button the default // more prominent than "Find (next) button"

    Stefan Sliwka
    • Under Community Review
    • 2 Comments
    When translators and proofreaders use Passolo, most of them tend to click the "Find" button instead of "Find all" button. This is due to the fact that the button is located right next to the search field where one enters the word to be searched. Actually...

  • Include handling of JSON files which start with an Array into built-in JSON parser

    Marion Kämpfer
    • Under Community Review
    • 3 Comments
    SDL support provided a workaround consisting in adding a root element manually to a JSON source file starting with an array since the built-in JSON parser cannot currently handle such JSON files. The workaround is fine but maybe enhancing the JSON parser...

  • Possibility of using glossaries during pretranslation

    Nils Jörn
    • Under Community Review
    • 1 Comment
    Hello, we're using the pretranslation function of Passolo with some translation ad-ins and we've some glossaries as well as a MultiTerm database connected, too. In the MultiTerm database as well as in some glossaries, forbidden terms/words are stored...

  • Use History for Pretranslation

    Dominic Buchheit
    • Under Community Review
    • 2 Comments
    Minor changes in strings cause the string to appear fully untranslated. Minor changes are for example changes in punctuation: "Hello. This is an example." --> "Hello ! This is an example." Since the string is changed and not deleted, i.e., not added...

  • JSON parser - Conserving spaces as source

    PB Localization
    • Under Community Review
    • 0 Comments
    Currently, using the JSON parser in Passolo 2018, the localized target files' structure is not strictly identical to the source file. Indeed, the number of spaces found before each string is divided by two. For instance, in the source en.json files...

  • Add sort to Check results

    Anna Kadlecik
    • Under Community Review
    • 0 Comments
    Hello, when reviewing / checking after translation, I would welcome the possibility to sort errors by type - it would increase productivity of the task. Thanks