Spell check issues

MrC's Avatar


23 Sep, 2022 05:46 AM

Hi Brett,

Here are a bunch of spell check issues I've encountered while checking a technical document. You're likely aware of these, but just in case, here is my list of issues:

  • If a document has been changed externally, and Preferences > Preview > Scroll to first edit is enabled, after learning/ignoring a spelling, the preview jumps back to last change marker position. The only way to fix this is to close / re-open the document, and this means re-calculating spelling, etc. for the entire document, and starting from the beginning of the document. (This happens also on any refresh, such as when adding CSS changes.)

  • Ignore spelling doesn't actually seem to gnore anything - the word/term continues to appear as a spelling error.

  • Spelling error markers on the left hand column don't work properly in a TOC that has been CSS'd to use multiple columns (I can provide a sample document if you want one). No red error dot appears on the left-hand column, but if you hover over and through text in the TOC, the dot appears / disappears. Using a keyboard jump shortcut will place the red dot on a TOC row, and then it immediately disappears. Some entries in the TOC have errors, but no wavy line, so it's impossible to find the error.

  • It would be nice if the checker for technical documents could better handle command-line options such as --ignoretimestamps. If I write "use option --ignoretimestamps", the grammar checker wants me to write "use option -- percategory" (despite being formatted as code).

  • Spelling errors appear in TOC entries for headers that contain code-styled options (as per above) show wavy red-lines under the option name, but not the double dashes (I really want to ignore all of "--ignoretimestamps").

  • Spelling errors for the above don't show any suggestions in the left-hand (yellow) suggestion box when clicking on the red spelling error dot (the green context box shows the problematic text).

  • "Go to next error" always goes back towards the top of a document if there is an error above the one just corrected. Due to some of the issues mentioned above, this always takes me back to my TOC.

  • Right-clicking a red-lined spelling error provides Unlearn even if the word has not been learned. The left column red dot shows the ability to Learn, so why shouldn't the right-click of the word itself offer this (and at least be consistent)?

Combined, these issues make spell-checking in Marked 2 rather challenging and time-consuming. I'm betting many of these are macOS API issues.

  1. Support Staff 1 Posted by Brett on 23 Sep, 2022 05:05 PM

    Brett's Avatar

    Yeah, you've run into a lot of the frustrations I have with implementing it. macOS does not allow for spell checking in a web view at all, so the entire implementation is hacked around that. All highlighting and underlining is hacked into HTML/javascript, and none of what you'd expect to happen is inherintly available.

    The learn/unlearn quirks are definitely something I can look at, but the positioning of dots and underlines, especially when using non-standard themes, is something I only have so much control over.


  2. 2 Posted by MrC on 23 Sep, 2022 07:35 PM

    MrC's Avatar

    Thanks for the reply. Understood, and low priority of course.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac