Under Community Review

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

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, we find this very, very, very disadvantageous as well as not intuitive - because, at least in our projects, you will want to find all instances of a specific word/string and correct them consistently (at least in 99% of the cases). The Find button will only find the next occurance of a searched term, and that is also dependent on the current cursor position in the text list, which is also unfavorable for our use case where you want to make sure to "catch them all" (the mistakes, that is).

By default, the search function should use "Find all" and hence the button position should be reconsidered. From a user-experience perspective, the "Find next" function is only useful as you advance in your list making/checking for specific/known issues and in that case, pressing the F3 button for browsing the occurrances is more useful than opening the search dialog clicking "Find" (over and over again).

Parents
  • I always use the "Find all" button and never "Find (next)". I work a lot with proofreaders that use Passolo maximum 2 times per year. In order to check and correct the translations for a specific source term, they should always search for all strings concerned. However, I realized that the proofreaders very often forget to change from the preselected "Find (next)" to the "Find all" button. So they do not get all hits and often create inconsistent corrections. It would be great if the UI could support this user demand.

Comment
  • I always use the "Find all" button and never "Find (next)". I work a lot with proofreaders that use Passolo maximum 2 times per year. In order to check and correct the translations for a specific source term, they should always search for all strings concerned. However, I realized that the proofreaders very often forget to change from the preselected "Find (next)" to the "Find all" button. So they do not get all hits and often create inconsistent corrections. It would be great if the UI could support this user demand.

Children
No Data