The following happens when working with the list of words with unknow spelling.
Now when pressing Cmd-F the culprit is found:
Usually I would dissuade user from using procedure a (in the documentation/tooltip), although it is not really strange to search the terms like this.
The strange thing: Sometimes both procedures work both like charms, sometimes not. It dies not depend on the way of marking it (double-click or drag the mouse around the word). But at least procedure b should really work always.
The simpliest thing would be to quit any carriage return/paragraph mark (it is not visible in the quick search bar) when searching. And using the S/R field for this kind of search is cumbersome (just to see if carriage returns are used - really?). Honestly, how often do we a search with the need of having a carriage return?
A simple link to the concerned segment inside this list would be another possibility, but probably harder to code.
> A simple link to the concerned segment inside this list would be another possibility, but probably harder to code.
Why don't you simply perform QA > Check spelling in target segments?
A better highlighting (by customizing the line) and/or an integration of LanguageTool (did I already mention this? it can be installed on your server and has an API) would be welcome.
No, it's not a joke. Your mentioning Papyrus brought back to memory the funny movie about a designer and the Papyrus font that I saw the other day on Saturday Night Live.