Enable Plain Text Spellchecker for Markdown#9271
Enable Plain Text Spellchecker for Markdown#9271lkishalmi wants to merge 1 commit intoapache:masterfrom
Conversation
b31a80a to
aab6cde
Compare
matthiasblaesing
left a comment
There was a problem hiding this comment.
The mimetype could be considered API as other modules could rely on the editor infrastructure to be in place for the concrete mimetype. Is there a reason not to use the "correct" mimetype? If we break this, why not do it only once?
For the change itself: The spellchecker has the option to be disabled on a per format basis. The implementation seems to be ugly:
The layer entries:
Are reflected into the UI:
And the settings is then used in the token list (see how the "hidden" attribute is found):
It seems strange that NB uses mimetype everywhere else, but names here.
|
Well, working on the Spellchecker Core at the moment. I think it's pretty old code and half of that was written by a contributor the other half by Jan. It has a few strange thing there how that handles Dictionaries and settings. It's tempting to change that, though I think it's better to leave that as it is. Also the recent upgrade of Lucene makes it possible to use HunSpell dictionaries. |
|
Nice! |
This adds the Plain Text Spellchecker which is not the best, though better than none.
Also made
text/x-markdownthe only MIME-TYPE used here for consistency.It might be tempting to use
text/markdownsince that's the official one from 2016 RFC 7763I've checked, that the previous MIME
text/x-markdown-nbwas not used anywhere else in the IDE.