-
Notifications
You must be signed in to change notification settings - Fork 489
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 check feature back in OLW #130
Comments
This is a big issue IMHO. Don't know about others. But, I relied on the Live Writer spell check quite a bit even though I consider myself a decent speller. |
+1 |
A pull request #213 already exists to fix this. |
Issue #130 - Add spell check feature back in OLW
Huge thanks to @bbowyersmyth for fixing this issue! Spell checking will be enabled in the next official Open Live Writer release. |
Thanks @bbowyersmyth !! How often do official releases get put out? |
Should make it very clear that spell check feature is only supported on Windows 8 and above, as "the Spell Checking API is available beginning with the Windows 8 or Windows Server 2012". |
@lextm you mean like we did in the blog post detailing the release? http://openlivewriter.org/news/release/2016/02/13/version-0-dot-6-now-available.html |
@ScottIsAFool no Scott. I don't mean that. The release notes look great though. Many threads/issues on GitHub on the other hand, only contains partial information, which is my concern. For example, if anyone comes to this thread, he/she might not get the key information like which OS is supported by spell check feature, and then he/she will be surprised to see this feature is disabled (on Windows Vista or Windows 7 as #209 revealed). Even googling "spell check Open live writer" won't lead us to the 0.6.0.0 release notes easily. I believe we need a better way to tell the users. Maybe a pull request to enhance the spell check feature, so that it explicitly tells the users on Windows Vista/7 that they should upgrade. |
We can use the built-in API provided by windows Spell check API!
The text was updated successfully, but these errors were encountered: