We have moved to GitHub Issues
Created by Shannon Deminick 19 Dec 2013, 00:12:09 Updated by Douglas Robar 11 Mar 2014, 10:01:32
Relates to: U4-2060
Currently we've enabled the browser to do it's in-built spell checking in the rte editor which is far more reliable and we don't have to maintain code for undocumented google APIs. This is the same functionality you see in any web browser's textboxes.
For example, in chrome: http://screencast.com/t/PERQvtjkZn
If this is unsatisfactory for whatever reason, in future versions we'd have to migrate some code from U4-2060 to a proper location in the v7 codebase and tweak it to work with the new version of tinymce
I've implemented this in a much better way that requires no server side implementations - it enables spell checking by the browser in the RTE which is heaps better and less code for us.
In 7.1.0 beta I'm not seeing any way to do spell checking in the RTE. There is neither a button to enable on the RTE to initiate spell check, nor does Chrome (33 on Win7) nor IE11 automatically do any spell-checking as you type. What am I missing to make this work?
Hi Doug, this issue was only completed yesterday so it is not included in the beta release.
See the above screencasts.
Thanks, Shannon. This is perfect! I look forward to seeing it in action, which is why I was trying it in the beta.
One last question about this... if I were working on a Spanish site (set with Cultures and Hostnames dialog) even though I typically have my browser set to English as you do, will the RTE advertise to the browser that I'm writing in Spanish and apply the appropriate built-in spellchecker? If that works (or can be made to work) that will be the very best this could be!!
Hey doug, not really sure about that one, I have a feeling it will default to whatever language the browser is configured for - the rte trick to make this work is just an html trick to tell the browser to apply its spell checking to it. There might be some secret html attribute to specify culture, not sure, will have to investigate.
Seems like there isn't a simple way to 'alert' the browser which language to use. I was hoping that a meta entry in the markup or similar technique would do that. Seems like it's a manual task for users of Chrome and Firefox (and presumably others):
Google settings: http://support.google.com/chrome/answer/95604 Firefox settings: http://support.mozilla.org/en-US/kb/how-do-i-use-firefox-spell-checker
Assignee: Shannon Deminick
Backwards Compatible: True
Due in version: 7.1.0