tag:support.multimarkdown.com,2013-02-12:/discussions/problems-v4/1294-spell-check-continues-to-flag-words-as-misspellingsMultiMarkdown Software, LLC: Discussion 2018-05-01T12:52:00Ztag:support.multimarkdown.com,2013-02-12:Comment/450671042018-04-12T00:21:26Z2018-04-12T00:21:26ZSpell Check Continues to Flag Words as Misspellings<div><p>Paul,</p>
<p>My apologies -- I drafted a response yesterday but it seems to have<br>
disappeared and apparently was never sent.</p>
<p>Short version -- Apple's NSTextView/Core Text API is powerful, but there<br>
seem to be a few gaps. One of which affects spelling. In order to get<br>
Composer 4's faster syntax highlighting to work I have to override<br>
certain aspects of NSTextView. In doing so, I discovered (or more<br>
likely one of my users... ;) that spelling and related features were<br>
disabled. There is no obvious way to "just enable them." It required<br>
manually re-implementing the logic to automatically check spelling, and<br>
I'm 1000% certain the algorithm I came up with is not exactly like<br>
Apple's. I would love to have macOS handle this automatically, like<br>
Composer 3, but that breaks other things....</p>
<p>That said, I can't replicate the behavior you describe. Whether I<br>
automatically correct spelling mistakes or manually correct them, the<br>
underlining goes away.</p>
<p>UPDATE: More testing -> I can occasionally replicate it with automatic<br>
spelling correction, but it seems to happen only with certain words or<br>
certain circumstances, and I'm not sure what those are. Perhaps if I<br>
can nail down what triggers the behavior I can fix it.</p>
<p>Additionally, when it does happen and I continue typing additional words<br>
in the same sentence, it does go away a couple of words later.</p>
<p>I'll try to dig into this more in the next week or so. If you find<br>
anything consistent between when it works properly and when it doesn't,<br>
please let me know.</p>
<p>Fletcher</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/450671042018-04-13T20:27:44Z2018-04-13T20:27:46ZSpell Check Continues to Flag Words as Misspellings<div><p>I'll try and record something the next time I'm writing so that you can see what I'm typing and the results.</p></div>Paul Solttag:support.multimarkdown.com,2013-02-12:Comment/450671042018-04-24T19:29:49Z2018-04-24T19:29:49ZSpell Check Continues to Flag Words as Misspellings<div><p>Long explanation short -- early in development, it seemed that I had to override a core piece of Apple's text view code. Which meant I had to write a bunch of workarounds to get other core Apple functionality to work (including spelling).</p>
<p>I <em>think</em> I was able to correct an underlying assumption, which now allows me to use more of the core Apple code, which means that I can now revert to built in spelling/grammar. Which means that these sorts of things should now work better.</p>
<p>This will be included in version 4.4, assuming nothing else is broken in my testing!</p>
<p>Thanks for your patience!</p>
<p>Fletcher</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/450671042018-05-01T12:51:57Z2018-05-01T12:51:57ZSpell Check Continues to Flag Words as Misspellings<div><p>I posted a 4.4 beta release that should fix spell checking, as well as a few other things. Once it's been tested, it will be pushed out for general use:</p>
<p><a href="http://support.multimarkdown.com/discussions/betas/384-composer-44-beta">http://support.multimarkdown.com/discussions/betas/384-composer-44-...</a></p></div>Fletcher