mailnews compose spell checker objects to quoted errors & names



MailNews: Message Display
13 years ago
12 years ago


(Reporter: Camilo Mesias, Unassigned)




Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050307
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050307

mailnews compose is being used to reply to a message with the original message
quoted in text form

The spell checker raises objections to the quoted text. I suggest that it is
generally undesirable to correct the spellings in quoted text, although it would
be interesting to see them, therefore it would be desirable to have the option
to ignore quoted spelling mistakes. 

Also the spell checker frequently objects to names of recipients. If the name is
matching the email address then it should not be regarded as a spelling error.

Reproducible: Always

Steps to Reproduce:
1. in text mode, reply to a message which contains spelling errors
2. include salutation with the recipient name as given in the address
3. spell check automatically before sending

Actual Results:  
spell checker raised objections to name and spelling errors in quoted text

Expected Results:  
ideally the option would be available to ignore spelling errors in quoted text,
and the name of the sender / recipient should always be allowed in a message.
The spelling errors would be notified only in the reply portion of the message.

Comment 1

13 years ago
bug 201866 comment #63 From Michael Kunz  2005-03-02 05:25 PST

"I just tested 1.8b1 and this version doesn't skip the quotes.
So I tested the oldest available nightly of 15th February and the newest nightly
of 1st March. In both versions the spellchecker doesn't skip the quotes.

Then I tested 1.8a6. This version does still skip the quotes. Therefore the bug
mus came back between the release of 1.8a6 and 15th February."


13 years ago
Severity: enhancement → normal


13 years ago
Keywords: regression
Version: unspecified → Trunk


13 years ago
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:
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.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.