The "Add Word Personal Dictionary" in Spell Check doesn't learn the new words. Also any proper name, if not capitolized, comes up with no suggested spellings.

RESOLVED DUPLICATE of bug 338291

Status

RESOLVED DUPLICATE of bug 338291
15 years ago
9 years ago

People

(Reporter: komodo, Assigned: sspitzer)

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20030925
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20030925

Actually I did once find (but now I don't know where it was) a file with my
"personal dictionary" spellings, but even with the new words spelled out
corectly, in spell check they still come up as a misspelled word.  In the file
that had my "personal dictionary", there were the same words listed multiple
times from each time I had spell check add it to the dictionary.  The words were
added to the personal dictionary, but spell check didn't use them.

As far as the "proper name" spellings, if I type "pennsylvania" it will come up
as misspelled, but without the suggested spelling capitolized as "Pennsylvania".

Reproducible: Always

Steps to Reproduce:
1.type an email with "LOL". 
2.Check spelling
3."LOL" comes up as misspelled, click the "add word" button.
4.type a new email with "LOL".
5.check spelling and "LOL" comes up as a mispelled word again over and over.

Actual Results:  
I think I already told you?

Expected Results:  
Learned the added word "LOL" in the personal dictionary so the next time a spell
check is done, "LOL" doesn't come up as a misspelled word.  This is true for ANY
words added to the personal dictionary.
If you click on "edit..." in the spellcheck window to edit your personal
dictionary, do the words show up?

Updated

15 years ago
QA Contact: esther → core.spelling-checker
Product: MailNews → Core
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core

Updated

9 years ago
Resolution: EXPIRED → DUPLICATE
Duplicate of bug: 338291
You need to log in before you can comment on or make changes to this bug.