Closed Bug 229888 Opened 21 years ago Closed 20 years ago

Spell Checker does not catch contraction errors

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: Anne, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040101 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040101 Spell Checker does NOT recognize the missing apostrophe in most contractions as an incorrect spelled word. ie: "cant" or "didnt", etc.. Some contractions such as "havent" are recognized as misspelled but no correct choice for replacement is available in dictionary Reproducible: Always Steps to Reproduce: 1.compose a message using contractions 2.do not use the apostrophe when spelling the contractions 3.run spell check Actual Results: Spell check says everything spelled correctly... with the exception of a few contractions such as "havent", which it does catch, but offers no replacement word with the apostrophe Expected Results: Detect contractions with a missing apostrophe and have the word in the dictionary with an apostrophe as a replacement
Summary: Spell Checker doen not catch contraction errors → Spell Checker does not catch contraction errors
Well, spell checker is not only for english user. There is not that type of contraction in french or spanish for example :)
according to http://dictionary.reference.com/search?q=cant, cant is a correct word. It is just not wat you wanted to type, but spellcheck can't know that. didnt is marked as incorrect. To add didn't as suggestion for didnt, bug 227214 will help.
QA Contact: esther → core.spelling-checker
this appears to be a dup of 218463, but I don't have permissions to mark it as such...
No, it isn't. This is about not catching words as wring, the other is about not suggesting the right word.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.