Currently, Sigil does not consider Numbers as "words".
This means that Spellcheck can't catch entire classes of errors, because many "words" don't display in the Spellcheck List (Tools > Spellcheck > Spellcheck).
I've attached an Example EPUB to show the issue.
The Problem
This includes the "Current Spellcheck List" vs. "Proposed Spellcheck List" in Spoilers.
Example 1: Centuries or Years:
Code:
In the 21st century, [...]
In the 1800’s, there was [...]
Example 2: Pounds/Shillings/Pence/Money
Code:
The device cost £14 8s 2d.
Example 3: Hyphenated Years or Age:
Code:
In the 10-year period between [...]
The 10-year-old girl [...]
Example 4: Weights/Measures
Code:
It weighs 100.5lbs.
The length is 100.5km and 2ft.
Example 5: Indexes/Footnotes
Code:
Dogs, 123n., 125, 130n.
See p. 123ff.
Example 6: A very common typo (especially because of OCR):
Code:
In the 196os, the president was [...]
In l941, the samples were [...]
Good argument, h0wever, you are [...]
It in Action
Calibre already includes numbers in their Spellcheck:
and it is extremely helpful.
Proposal
There is one downside to the Calibre-method though, because the Spellcheck List gets flooded with numbers. Especially when dealing with HTML tables full of data (or in Indexes):
To get around that issue:
- Ignore all "words" made completely of numbers + punctuation
- Although I could see a usage for still keeping this (catching typos)
- Include the "Numbers as Words" as a checkbox/toggle.
- Similar to "Show All Words"
- Probably default to OFF.
- This could allow the user to choose whether they want to display those full-numbers or not.