Closed Bug 234322 Opened 22 years ago Closed 20 years ago

Spell checker should handle punctuation/symbols appropriately (e.g. "etc", "etc.")

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mozilla, Assigned: mscott)

Details

User-Agent: Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.6) Gecko/20040210 Firefox/0.8 If I create a message which includes "etc.", the spell checker highlights "etc" and suggests changing it to "etc.", even though the fullstop is already there. Reproducible: Always Steps to Reproduce: 1.Write a message which includes "etc." 2.Run the spell checker Actual Results: Spell checker flags "etc" as wrong and suggests "etc." Expected Results: Spell checker should recognise the fullstop as part of the word and not claim a spelling error
should this bug be re-summed to just 'SpellCheck should recognize punctuation as part of a word?" I have the same problem with e.g. and http:// references; I know that this bug is really specific, but making it hinge on all punctuation would allow the http:// spellcheck-avoidance enhancement (bug 172186) to be a simple http://[^ ]+ entry in a dictionary on top of this bug.
I don't think it'd be a good idea to always include punctuation as part of a word, because every sentence-ending word would then be flagged, unless there were additional changes to account for this. Changing the summary to "Spell checker should handle punctuation/symbols appropriately" - even more general.
Summary: Spell checker recognises "etc." as "etc" → Spell checker should handle punctuation/symbols appropriately (e.g. "etc", "etc.")
There is some more odd behavior. For example, "couldnt" will be flagged with no suggested spelling while "could'nt" will have a suggested spelling of "couldn't". The spell check needed the apostrophe in someplace to suggest a spelling using an apostrophe.
version 1.0+ (20050803) Both "etc." and "etc" work for me. This was probably fixed by the new inline spellchecking bug.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.