Closed Bug 294887 Opened 20 years ago Closed 20 years ago

When composing new messages, text appears underlined (underscored) in red.

Categories

(SeaMonkey :: MailNews: Message Display, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: michael.graubart7, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050518
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050518

When composing a new e-mail message, each time a word is completed and followed
by a space, that word appears underlined in red. If, however, the word is
followed by a punctuation mark (period, end-of-quotation, etc.), the word is not
underlined in red.

When the message is sent, the recipient sees it without the red underlining; so
this bug is an irritant to the writer rather than to the reader.

NB: For American readers: please read 'underscore' for 'underline'.

Reproducible: Always

Steps to Reproduce:
1. Select mail -> compose.
2. After entering address and title, begin to type message in the message pane.


Actual Results:  
All words followed by spaces appear underlined in red.

Expected Results:  
Unless 'Underline' has been selected, the text should appear without underlining
(and if 'Underline' has been selected, the underlining should be in the same
colour as the text itself).

eMac G4, OS X 10.3.9, Classic theme.
I should have added: this bug appears for the first time in Build No.2005051810.
The previous build available from 'Latest nightly builds', i.e. 20050504, did
not show this bug.
Hey, this is no bug, this is a feature :)! This is called Spell as you Type and
shows you misspelled words. Try right clicking on a underlined word to see a
suggestion. Maybe you don't have a Dictionary in your language installed? Anyway
if you can confirm this, resolve bug as invalid.
Hey, this IS a bug! Are you telling me that absolutely every word I type is
misspelt, but that putting a comma after it makes the spelling OK? Come on!
Normally it should work :D (here it does), what language do you have selected
under Options-Check Spelling... ? Does this dialog also mark the same words as
wrong as the Spell as you Type?
I have English (US) installed and selected. I downloaded German and English
(GB), as I would prefer to use English (GB), but after they were installed,
Preferences -> Appearance -> Languages said 'Update required' for German and
English (GB), and after selecting them and restarting Mozilla, they return to
being unselected.

So where do I get the updates from?

It is perfectly true that if I unselect 'Spellcheck as you type', the red
underlining stops. But the next time I type a new message, 'Spellcheck as you
type' is on again. So with this new build of Mozilla, writing e-mails has become
much too troublesome.

I repeat: with English (US) installed and selected in Preferences, EVERY word is
underlined unless it is followed by certain punctuation marks (comma, quote).

By the way, under Options, the ONLY option is 'Spellcheck as you type'. Neither
'Check Spelling...' nor 'Spell as you Type' exists. And (as you might have
noticed from my details) I use a Mac, so I can't right-click.

My humble apologies –- almost! I have discovered how to install dictionaries and
how to deselct 'Spellcheck as you type' globally in Preferences. Everything is
working correctly now -- almost! But I have installed the English (GB)
dictionary, and with 'Spellcheck as you type' selected again, Mozilla mail still
insists on US spelling, not GB spelling. (The English [GB] entry under Languages
in Preferences still says 'Update required.)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Is English (GB) selected in the Options -> Check Spelling dialog?
As indicated before, there is no active option for 'Check spelling' in
'Options'. It is dimmed out.
I was using Build 20050518. I have now downloaded 20050520, and 'Check spelling'
now appears and I can select the language I want. Thank you.
You need to log in before you can comment on or make changes to this bug.