It’s great to see this, and just getting going on seeing how useful the headed-for-real -3 features are.
I do note the new spell checker is a bit unsorted as yet. In particular:
a word like Carré, as in Le Carré, is picked up with a red wavy underline, but nothing is offered if you right-mouse it for spell-checker functions. You have to do a full doc spell check, get to this item, and only then can add it to the user dictionary.
if you do a full doc spell correct successfully, your present Scrivener file will still show the red wavy mistake indicators as if you hadn’t. You have to mouse on another segment and back on, in order for the alerting indicators to clear.
if you go off Scrivener in the midst of a spell check session, say to check if what you had actually was acceptable via web dictionaries, spell check seems to have forgotten itself when you come back, and you’ll have to start over for the entire file.
Anyway, elegant and getting more so, thus a thank you.
Well, not sure what I was seeing there, though I kind of remember.
Trying it now, I’ve successfully gotten Scrivener 2.9.0.4 spelling to learn words with French and German diacriticals – and even to learn Korean syllablic characters properly. Pretty impressed with the latter (the syllables have alpha-like symbols, though they arrange in fully 2-dimensional arrays)…
What I see taking a bit more time now, and it may be the original complaint, is that when you first have spelling encounter an unknown word, the following sequence applies:
You get the wavy red line
On right mousing, you get a short list of often not-very-related words
With an accent on the end, as Carré, you may get what looks like missing pieces – Carr – though these are not quite incorrect guesses
You tell it instead to learn, and the menu goes away
But: the wavy red line remains…still saying it’s a spell error
Only when you mouse or arrow key to the right end, and then type an advancing space, does the red fault line actually go away.
So I would say that point c. may have confused the issue, but that point e. is the most important problem, and a soluble one: once the spelling has been accepted, the red wavy error line should immediately go away.
I was probably prejudiced on that first quick look by memory of how the speller used to go completely awry in earlier releases, so I was expecting or accepting more error than I actually saw. It does seem what’s described here should be repaired, and again, it’s simpler.
Yes, spelling not updating correctly is an issue we have filed, so hopefully when that is cleared up the rest of the issues will go away as well. Once that happens let us know if you still encounter anything odd.
Just a little more on this fault area, which it looks like you may already know.
I opened Scrivener Windows today, perhaps fatefully after using it on the same project on an iPad, and found that the previously mentioned spelling corrections all are showing red lines again.
Some details:
right-mouse Spelling > Recheck Spelling didn’t help anything
redoing the right-mouse Learn Spelling operated, still leaving red lines
the trick of clicking to the right of a word and entering a space did clear all the red lines, not just on that word
closing, reopening gave back the red lines, so it wasn’t the iPad excursion, only Windows Scrivener itself
the end-of-word-space trick didn’t work on the reopened project; you would have to go through Learn Spelling again…
