Add spellchecking to documentation
See original GitHub issueProblem
As of #833, we won’t be doing any automated checking on .ipynb
and .md
files. We could get some meaningful automated feedback on these by applying spellchecking, which would both save review load, as well as find existing issues.
Suggested Improvement
- add
hunspell
andhunspell-en
to the environment - generate HTML example noteboks with nbconvert
- add a custom dictionary for terms of art and branding
- run
hunspell
duringdoit check
on the built docs and converted notebooks
Issue Analytics
- State:
- Created a year ago
- Comments:5
Top Results From Across the Web
Spellchecking | IntelliJ IDEA Documentation - JetBrains
Press Ctrl+Alt+S to open the IDE settings and select Editor | Natural Languages | Spelling. Add words to the Accepted words list. IntelliJ...
Read more >Lesson 1 - Add Spell Checking to Your Application
This topic will show how to add spell-check functionality to your application, using the SpellChecker component. Dictionaries for US English ...
Read more >spellcheck - HTML: HyperText Markup Language | MDN
The spellcheck global attribute is an enumerated attribute that defines whether the element may be checked for spelling errors.
Read more >Check your spelling & grammar in Google Docs - Computer
Check spelling & grammar · Open a document in Google Docs. · In the top left, click Spell Check Spell check . A...
Read more >Spell Checking - CKEditor 4 Documentation
If you have content in multiple languages, the spell and grammar check feature can automatically detect the text language properly. It is enough...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hm, thought I replied, but I think there were github (issues) issues.
Basically, we’d want to use
hunspell
in the places we havepytest-check-links
, against (nearly) the same set of documents. It is not available frompip
, so it wouldn’t go in requirements, and it also needs a dictionary, in this casehunspell-en
.The other file that will be needed is a
docs/dictionary.txt
.Here is a concrete ancestor of our
doit
setup using it in a doit task, pointed at that dictionary. Of note, that dictionary is super long, and I’ve found it best to try to cajole as many “code jargon” words as possible into appropriate tags, and skipping the generated index page. We’ll almost certainly have…But there will be many more! Another thing i’ve learned is to keep that file sorted, adding another
lint:dictionary
task.If that fails entirely another approach is to rewrite the HTML before emitting them, but that’s a bit hard.
Binder?
On Fri, Oct 28, 2022, 07:28 Kostya Farber @.***> wrote: