ASPSpellCheck Demos
Examples with full source-code
> Website Forms Spelling Validation
> Spell Check almost any Rich Editor
> Spell Check when Submitting a Form
> Backend ASP SpellCheck Functions
> Multilingual Spell Check
> Spell Check HTML Elements
> AJAX Spell Check
WYSIWYG Editor Spell Check
Tutorial:
There are HTML numerous WYSIWYG editors available on the internet. A good resource to find one is http://www.htmlarea.com.
ASPSpellCheck is compatible with almost all of these Rich Editors (WYSIWYGs). We even have a plugin for FCKEditor.
For most editors, you need to ASPSpellCheck the Iframe which the WYSIWYG uses. The ASPSpellLink.Fields property should be set like...
e.g. myLink.fields="iframe:myWYSIWYGFrameId"
To spell check an iframe within another iframe (as is common for WYSIWYG Editors) use dot notation to identify its full path.
e.g. myLink.fields="iframe:myMainFrame.mySubFrame"
If you don't now the id of the WYSIWYG's iFrame then use
e.g. myLink.fields="iframe:0"
Iframe:0 points to the first frame or Iframe in the JavaScript DOM. iframe:1 points to the second etc...
Examples:
FCK Editor: A Free SpellChecker PlugIn for FCK Editor is now available.
Or you can use myLink.fields="iframe:MyTextArea___Frame.0"
YUSASP Editor (formerly Innova) :
myLink.fields="iframe:idContentoEdit1"
Where oEdit1 is the name of JavaScript name for the editor.
HTMLArea3 :
myLink.fields="iframe:0"
The iframe value may not be 0 if the WYSIWYG is not the only frame/iframe on the page.
MoxieCode MCE Editor:
myLink.fields="iframe:mce_editor_0"
Use mce_editor_0 for the first MCE editor on the page, mce_editor_1 for the second.....