Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Spell Checking in the Blog Editor #2340

Closed
EisenbergEffect opened this issue Mar 5, 2014 · 5 comments
Closed

Add Spell Checking in the Blog Editor #2340

EisenbergEffect opened this issue Mar 5, 2014 · 5 comments

Comments

@EisenbergEffect
Copy link

As a blog author, I want to use the online editor as the sole tool to create my content. However, I tend to make spelling mistakes as I type...and sometimes my brain just gets things wrong too. The current editor has no feedback on misspelled words so it's easy to miss them and publish content with errors. I can get around this by proofing 3-4 times and using an external document editing tool, but I'd rather not have to do that.

People have become accustomed to spell checking as a base line feature in any document editing software. Seeing that it was absent was immediately off putting for me and is a constant source of pain for me (a paying customer). When people ask me about the ghost product I can list a lot of positives, but in trying to be honest, I have to list this as a major shortcoming right now.

@halfdan
Copy link
Contributor

halfdan commented Mar 5, 2014

This is a duplicate of #1543, #2314, #2340 and #1240. Please do a search according to our contributing guidelines before opening an issue. Spell checking is definitely important, but currently not possible with the editor we're using. The editor will at some point be revised, here's the roadmap: https://github.com/TryGhost/Ghost/wiki/Roadmap

@EisenbergEffect
Copy link
Author

I did do a search and looked at those issues. Here's the problem: all of
them were closed without actually making any fix. Also, the collective
issue #1294 has it listed and crossed out as "won't fix." Clearly the same
issue is coming up over and over again and there's no clear indication in
the github issues as to what is going to be done now or in the future. So,
I created a new issue to emphasize the point in hopes of getting a
definitive statement. It sounds like you are planning to fix it as part of
a new editor implementation. Great. I personally can't emphasize how
important that is. I've been a paying customer for about one month or so
and I've written about three blog posts. After my third, I resolved myself
not to use the ghost editor again. It's not usable in its current form for
this and other reasons. I'm going to be doing all of my editing in an
external tool and then pasting the content in. I think that's a real shame
and I hope I don't have to do that for long.

On Wed, Mar 5, 2014 at 10:16 AM, JohnONolan notifications@git.luolix.topwrote:

Closed #2340 #2340.

Reply to this email directly or view it on GitHubhttps://github.com//issues/2340
.

Rob Eisenberg,
President - Blue Spire
www.durandaljs.com

@javorszky
Copy link
Contributor

Hi.

I understand it's something that people would want, however given the sheer number of languages, language corpi of those languages and contextual differences of words, implementing a spellchecker in the editor is simply not viable. (There are perks when university publishers are among the clients I work on).

That said most operating systems have built in spell checking functionality, and I'm sure there are extensions for browsers that would handle this (didn't check though).

Hope this helps.

@halfdan
Copy link
Contributor

halfdan commented Mar 5, 2014

@EisenbergEffect #1240 clearly states that this is scheduled for later: #1240 (comment)

@dandv
Copy link

dandv commented Mar 9, 2018

#9311 should solve this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants