Let me know if you saw this feature in other web projects (specially open source). What I would recommend for you to use is a tool called IE Spell. I tried it once and it seemed fine, however, I didn't use it for a long time. It is freeware.

See the following url for more details:
http://download.com.com/3000-2378-10220980.html?tag=lst-0-1

I am not sure if there are equivalent tools for other browsers.

edited on: 05-14-04 11:12

number of open source html editors integrate iespell as an editor.

iespell however, has now gone towards being commercial - it's 'freeware' for personal use, any other user requires a license.

same open source html editor, also supports using MS Word as a spell checker (provided the mantis install is in trusted sites zone in IE - i.e. you need to be able to run activeX controls)

e.g. http://www.fredck.com/FCKeditor/ supports both MS word and Iespell for spell checking.

I saw an html based spell checker integrated into GPL licensed PHP weblog. For more details see http://www.b2evolution.net

There's always this:

http://www.master-technology.com/demos/spell/

Alot of phpBB sites use it. Shouldn't be too hard to integrate into Mantis.

There is a spell checker plugin built into SquirrelMail and uses apell/ispell as the backend. It works very well, and the source for it could be hacked up to be used with mantis.

For more info:
http://www.squirrelmail.org/wiki/en_US/SquirrelSpell

Origional Author:
Konstantin Riabitsev, http://www.mricon.com/

I don't feel that a spell checker belongs in a web-based tool. I feel that a spell-checker belongs in an operating system or in a web browser. Mac OS X, for example, offers an OS-wide spell checker, which works great in the Safari web browser and all others that use standard Mac OS X text services.

If someone did want to implement this, it would need to be done as a plugin now.

Whilst back in 2004, this was indeed a good suggestion, the modern browsers that now exist tend to have spell check built in - At least chrome,firefox and IE11.

Given the above, I think we can mark this as resolved "won't fix" - nothing has been done in 10 years to fix this issue, and the browsers probably now do a better job for us, such that implementing something would probably be more confusing for the end user.