Start a new topic

Inconsistent behaviour when checking for misspelled words

The following happens when working with the list of words with unknow spelling.


Procedure:

  • Menu command 'Task' > 'List words with unknow spelling'
  • Tab opens

Procedure a:

  • double-click on a word, copy and paste it into the quick search bar
  • occurrence is found/not found (depending on sth I ignore)

Procedure b:

  • double-click on a word, press Ctrl-Shift-F3 to copy it to the quick search bar and search (here in project target)
  • occurrence is found/not found (depending on sth I ignore)

Now when pressing Cmd-F the culprit is found:

image


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.


Just to be clear: This only concerns trailing paragraph marks. Perhaps it is easier to find a solution having this in mind.

 

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?

> Why don't you simply perform QA > Check spelling in target segments?

Because it is faster to go through – in the QA > Check spelling there is even no highlighting, only a thin red line – and the user dict can be populated very easy this way.

 

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.

Just for some inspiration. This is the settings window from Papyrus, a German writingapp with a very detailed style correction.

image


It allows only tp change the text color or dotted lines, solid lines, dashed lines, crossed out sections or sections marked with X, always thick or small, plus the color chooser. And much more.

Why did you remind the developer of Papyrus? ;)

Sorry, I am not allowed to see this content (or maybe this is the joke). Poland-Germany 1:0.

 

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.

Login to post a comment