RT Spell Check

In getting ready to deploy RT, the boss was reviewing the system, liked the customizations we’d make to “soften” it down a little (we’ve got sales and accounting people using this system too and we all agreed that the default UI was WAY too confusing to be usable by anyone but a tech)
He had one request… “The web mail thing needs a spell checker. I hate it when I get email and it’s loaded with spelling errors”

Aside from copy/pasting the messages in from another program, does anyone have any thoughts on how to go about plugging a spell checker into this thing?

Brian

Without doing something client-side (like a java applet that came with a
pre-loaded speller/editor), anything you do will be clunky. You could insert
an interface to ispell within RT’s correspondence method or doing one of a
few other possibilities, but in the end you’d accept a correspondence, spell
check it, then respond with an error about all of the misspellings for the
user to then hunt around. I believe that your best, easiest course would be
to ask users to write their messages in an external application and then
paste in the result.

Thanks,
Christian

Christian Gilmore
Technology Leader
GeT WW Global Applications Development
IBM Software Group

-----Original Message-----
From: rt-users-admin@lists.fsck.com
[mailto:rt-users-admin@lists.fsck.com]On Behalf Of Brian Shellabarger
Sent: Thursday, November 07, 2002 1:27 PM
To: rt-users@lists.fsck.com
Subject: [rt-users] RT Spell Check

In getting ready to deploy RT, the boss was reviewing the
system, liked the customizations we’d make to “soften” it
down a little (we’ve got sales and accounting people using
this system too and we all agreed that the default UI was WAY
too confusing to be usable by anyone but a tech)
He had one request… “The web mail thing needs a spell
checker. I hate it when I get email and it’s loaded with
spelling errors”

Aside from copy/pasting the messages in from another program,
does anyone have any thoughts on how to go about plugging a
spell checker into this thing?

Brian


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at
http://fsck.com/rtfm

winmail.dat (2.67 KB)

Without doing something client-side (like a java applet that came with a
pre-loaded speller/editor), anything you do will be clunky. You could insert
an interface to ispell within RT’s correspondence method or doing one of a
few other possibilities, but in the end you’d accept a correspondence, spell
check it, then respond with an error about all of the misspellings for the
user to then hunt around. I believe that your best, easiest course would be
to ask users to write their messages in an external application and then
paste in the result.

In a former life I wrote a spellchecker into a CMS that used an
HTML-only interface. The back-end was ispell with Debian’s HTML syntax
patch (invoked by a Perl script called by the form submission handler
(PHP)). The handler would pull back the results from ispell and
generate a new with pulldowns (values were ispell suggestions)
and entry boxes for misspelled words. The second submit would be
considered authoritative (i.e., if it’s still misspelled just trust the
user).

Frankly, having implemented and deployed this I can guarantee it’s
overkill (did I mention that CMS also hooked into GIMP for logo
generation?).

These days my advice is to simply get users who can spell – it’s more
cost-effective, and in this economy one can afford to be picky :wink:

Rick
http://www.rickbradley.com MUPRN: 461 (60F/60F)
| I’ll try to figure
random email haiku | it out attach things under
| a different file.

Well, I disagree.

Writing a spell checker for RT has been on my todo list for sometime,
(Albeit low on said list =] ), I think that there is room for an
elegant server side solution.

I was thinking of something very similar to Rick Bradley’s solution.
Except that I had planned on putting a seperate button for spell check,
and then just replacing the contents of the update box once the check
was complete. My plan is to offer suggestions in a drop down box, with
a couple of other options in addition. Having an Add' andCustom’
option in each. The Add' option would add the word to the user's dictionary. TheCustom’ option would mark the word and prompt the user
for a suitable replacement. I was planning on adding another text box
field to the user preferences to manage the user dictionary.
My first scratch was not planning on implementing the custom dictionary.
I was planning on using Aspell as the spell checker.
I think that it can be done very elegantly with no clunk at all.
After all I think that the StockAnswers module (packaging problems
aside) was a fairly elegant solution.

That’s just my opinion, I could be wrong.

-Michael

Christian Gilmore wrote:

I really don’t like server side spell checkers. I don’t like the idea to
use ten different spell checking systems, one for each web application.
Different features, dictionaries, usage, user dictionaries.
Spell checking is a task the client should do.

I suggest “ieSpell” to my clients. It is a free Internet Explorer
browser extension that spell checks text input boxes on a web page (see
http://www.iespell.com/).

Unfortunately there is no such tool for Netscape up to now. Maybe you
wanna help the Mozilla-Developers implementing this:
http://bugzilla.mozilla.org/show_bug.cgi?id=16409

– FlorianAm Don, 2002-11-07 um 21.52 schrieb Michael Grubb:

Well, I disagree.

Writing a spell checker for RT has been on my todo list for sometime,
(Albeit low on said list =] ), I think that there is room for an
elegant server side solution.

I was thinking of something very similar to Rick Bradley’s solution.
Except that I had planned on putting a seperate button for spell check,
and then just replacing the contents of the update box once the check
was complete. My plan is to offer suggestions in a drop down box, with
a couple of other options in addition. Having an Add' andCustom’
option in each. The Add' option would add the word to the user's dictionary. TheCustom’ option would mark the word and prompt the user
for a suitable replacement. I was planning on adding another text box
field to the user preferences to manage the user dictionary.
My first scratch was not planning on implementing the custom dictionary.
I was planning on using Aspell as the spell checker.
I think that it can be done very elegantly with no clunk at all.
After all I think that the StockAnswers module (packaging problems
aside) was a fairly elegant solution.

That’s just my opinion, I could be wrong.

-Michael

Christian Gilmore wrote:

Without doing something client-side (like a java applet that came with a
pre-loaded speller/editor), anything you do will be clunky. You could insert
an interface to ispell within RT’s correspondence method or doing one of a
few other possibilities, but in the end you’d accept a correspondence, spell
check it, then respond with an error about all of the misspellings for the
user to then hunt around. I believe that your best, easiest course would be
to ask users to write their messages in an external application and then
paste in the result.

Thanks,
Christian


Christian Gilmore
Technology Leader
GeT WW Global Applications Development
IBM Software Group