Open
Bug 128122
Opened 23 years ago
Updated 2 years ago
RFE: Spell checker does not recognize capitalization errors.
Categories
(Core :: Spelling checker, enhancement, P3)
Core
Spelling checker
Tracking
()
NEW
People
(Reporter: dslmichael, Unassigned)
References
(Depends on 1 open bug, )
Details
(Whiteboard: [GS])
Steps to reproduce:
1. Launch Composer
2. Type the sentence "i think It would be Nice if this found Capitalization
errors"
3. Click on the spell check icon on the toolbar
Actual results:
"No misspelled words"
Expected results:
I would expect that spell checker would at least point out the obvious errors.
For example I used as a word, and the first word of a sentance.
I am seeing this issue as far back as NS 6.2.1 and this is happening on all
platforms and OSes.
The spellchecker doesn't care about capitilization and the location of the word
in a sentence. This is an RFE, moving to FUTURE.
Priority: -- → P3
Summary: Spell checker does not recognize capitalization errors. → RFE: Spell checker does not recognize capitalization errors.
Target Milestone: --- → Future
Updated•21 years ago
|
Severity: minor → enhancement
*** Bug 237483 has been marked as a duplicate of this bug. ***
Assignee: kinmoz → nobody
Component: Editor: Composer → Spelling checker
QA Contact: sujay → core.spelling-checker
Comment 4•21 years ago
|
||
*** Bug 237276 has been marked as a duplicate of this bug. ***
kinmoz@netscape.net said....
>> The spellchecker doesn't care about capitilization and the
>> location of the word in a sentence. This is an RFE, moving to FUTURE.
I beg to differ.
The spell checker does know about "Internet" but it does NOT know about
"internet" -- and even worse, it does not suggest "Internet" when it says that
"internet" is misspelled.
Bug 237276 discusses this.
I don't know if Bug 237276 is a dupe of this bug or not. While I am glad that
Mozilla has a working spell checker again, it is frustrating to use dozens of
times per day.
Jay
jay@jaysmith.com: what kin wrote is correct
all the spellchecker sees is a single word, it doesn't know where the word is in
a sentence.
now the spellchecker's dictionary cares about case. Its dictionary says that
"Internet" is a word, and "internet" is not. But that's not the same thing as
the engine knowing or caring about context (it doesn't).
Target Milestone: Future → ---
Comment 7•19 years ago
|
||
*** Bug 303869 has been marked as a duplicate of this bug. ***
Comment 9•17 years ago
|
||
Stop Press Guys.
I was more concerned about the failure to correct "i think" to "I think" BUT, when I finally found out how to change to the ENGLISH UK (rather than the English US) dictionary, imagine my surprise when a lone "i" was flagged with suggestions "ii" and "I" which is what I wanted AND incidentally, what I remembered from my last installation.
So...
IF all you want (as I did) was to detect "i" as an error, then change to the English UK dictionary.
You will have to address UK/US issues over colour/color, flavour/flavor, sensitize/sensitise etc but we Brits gave you the angled deck aircraft carrier, the jet engine, supersonic flight, the Computer and the Merlin engine and in return we got the Boston Tea Party, bad spelling and Microsoft. Ha.
It does beg the question why the UK and US dictionaries should behave differently in this respect.
Anyway, Firefox knocks outlook Express into a cocked hat so be proud.
Comment 10•15 years ago
|
||
'internet' problem WFM after Hunspell (Firefox 3.0).
Re: comment 9, All single letters such as i, j, k are included in the en-US dictionary, I think. It hardly seems worth switching to British spelling just to get your I's capitalized.
Other issues will require a grammar checker that knows about sentence breaks. Marking dependent on 395327.
Depends on: 395327
Updated•13 years ago
|
Whiteboard: [GS]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•