If you are using Firefox as your browser I thoroughly recommend the Spellbound extension.
I would but a client wants it “built in.”
I’m willing to pay for one that works in WP 1.5 or WP 2.0 with a wysiwyg editor.
What about that new Ajax spell checker? Doesn’t it use aspell?
A spell checker that doesn’t use aspell? Just how much are you offering, and when do you want it? And what did you want it to use instead of aspell?
More info: has to work in IE and Firefox.
I have a spell check plugin which doesn’t use aspell, has lots of Ajax goodness, and will probably be easy enough to make work with WP 2.0’s WYSIWYG interface. (It currently doesn’t.) It’s BSD licensed. Contact me if you’re interested. 🙂
Hi again, I’ve messed around with Ajax spell checker some and it works great except doesn’t work in IE. Wondering how yours is different?
http://exotic4.nipne.ro/~iacobs/work/wordpress-plugins/ajax-spell-checker/
Error: Would you like to email me? Use http://www.tornadodesign.com/contact
Wondered if anybody else was interested in this project?
I’m interested in this as well. I made a wysiwyg plugin that supports spell checking using Speller Pages and ieSpell, but people have been having problems setting up the server to use aspell (for Speller Pages).
Being able to use an ajax spell checker would make things much easier.
If anyone is still interested in this topic, you can try the phpSpell hack for my WYSIWYG plugin. phpSpell is a MySQL/PHP only plugin, so no aspell needed.
Alternatively, you could find a way to incorporate Jacuba, though your client may not be interested, since Jacuba does spell checking via their server.
Whatever you do, don’t use the Google Bar spell checker.
If you want to see what it does to a post being edited with the WYSIWYG interface take a look here:
http://www.wildtangents.net/2006/02/04/how-to-get-spellbound-spell-checker-working-with-firefox-1501/
I haven’t found anything that works yet.
I’ve been using the Xhina Here! plugin for Firefox to do my writing/editing. It doesn’t have a spellcheck either, so once I go back to WordPress (with the WYSIWYG editor turned off) I have to use the Google toolbar for spellcheck. It works fine if the WordPress WYSIWYG is turned off.
But that’s adding an extra step to the whole process.
I’m probably going to go back to using ecto as my blog editor, and just use the WordPress interface for updating my theme, adding links, and other admin-related tasks. Yeah, I <i>could</i> just use the quicktags or do the coding myself but I’d rather not even <i>see</i> code when I’m tryin gto write or edit.
thicke: Yes, the spell checker in the Google bar is very good, but not for the Rich text editors. It incorporates spelling suggestions and other niceties in your post.
And it also locks up the post sometime, so you can’t publish. Naughty behaviour indeed. I’d like to use the Rich editor, but I’m also in real need for spell checking.
A good thing is that it’s working here ( I hope 🙂
EditorMonkey offers 3 spell-checking options: client-side (ieSpell/SpellBound), server-side (SpellerPages aspell), and 3rd-party (Jacuba). All of these have been integrated into the editor.
It should be fairly easy to copy over these features to Xinha or the normal WordPress 2.0+ install. For the latter, copy the jacuba and/or spellerpages plugins from the editormonkey/tinymce/plugins directory. You’ll need to add these to the tiny_mce_gzip.php file in the wp-includes directory of your WordPress install.
