Welcome Guest Search | Active Topics | Sign In | Register

Spell Checker is not working with contractions correctly Options
sbenny
Posted: Thursday, June 3, 2010 3:24:14 PM
Rank: Newbie
Groups: Member

Joined: 11/27/2007
Posts: 3
Hello all,

We have added the spell checker to our ASP.Net web based application, and everything looked to work right at first. Then we came up with the problem where certain contractions that are in the dictionary we downloaded for use are being ignored.

For example, if the word didn't is in the text, the didn is being highlighted as not being a valid word. I checked the dictionary, and the word didn't is in the downloaded dictionary.

Any help as to why this could be happening, and of course how to fix it?

Thanks,

Scott
eo_support
Posted: Thursday, June 3, 2010 3:38:23 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

This appears to be a bug. In that case it will require code changes on our side to make it work. We will look into it and see what we can do.

Thanks!
sbenny
Posted: Thursday, June 3, 2010 4:01:37 PM
Rank: Newbie
Groups: Member

Joined: 11/27/2007
Posts: 3
Thank you. As an addition to the prior problem, I just noticed another strange thing. The spell check does find unknown words, but if the word is in more than one control being checked, the Ignore All button doesn't help (that is: for each control I have to hit Ignore All again). Perhaps that is the way it is supposed to work, but I had expected that it would continue to ignore the word until the dialog was closed.

Can you indicate if this is working correctly in this situation?

Thanks,

Scott
eo_support
Posted: Thursday, June 3, 2010 4:10:50 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

I assume that by "multiple controls", you meant by setting ControlsToCheck to include multiple controls IDs so that you can check all of them at once.

If this is the case, then yes, what you see is considered "correct" even though what you were expecting makes sense too --- it's a little bit of gray area without a clear cut here. The main reason for the current implementation is "Ignore All" affect what is currently shown to you. Because there is no way for you to see "ControlB"'s text while reviewing "ControlA"'s text, clicking a button while reviewing "ControlA" should not affect anything about "ControlB". That's why you need to click it once for each control.

Thanks
sbenny
Posted: Thursday, June 3, 2010 4:15:33 PM
Rank: Newbie
Groups: Member

Joined: 11/27/2007
Posts: 3
Yes, you understood my question correctly. Thank you.


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.