I don't know how much of a performance hit this will
occur, but a suggestion has been made to extend the
ispell functionality that's available in the story
editor to the comment editor as well. I am therefore
formally making this request here. If no one on the
team has the time to do it, but the idea is acceptable,
I have no problems with working on this myself and
submitting a patch.
Logged In: YES
user_id=144730
Seeing as how it was my rant which caused this request (all
information at
http://slashdot.org/~AntiFreeze/journal/15793\), I hereby
offer the following: I am more than willing to write a perl
script which takes text and finds and highlites (by adding
bold tags, or some predefined $tag) the misspelled words
within that text. I know nothing about Slash (never looked
at it) so it would be left to someone else to incorporate my
code into Slash if you thought it would be worthwhile.
Logged In: YES
user_id=3660
My guess is that the load on the server would be significant.
Maybe this can be a plum ...
Logged In: YES
user_id=144730
How about putting it into the preview page for just journals
to begin with? That way you can guage what kind of a hit it
might make to server performance. Also, this gives you the
added benefit of being able to say: "Well, if you really
want slashdot to spellcheck your comments, just preview it
in your journal before posting it." I know a lot of people
who would be quite content with spell checking in journals
if spell checking for all comments was unimplementable for
performance reasons.