Bug 86040 - Spell Checker doesn't work in mail?
Summary: Spell Checker doesn't work in mail?
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: evolution
Version: phoebe
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-03-12 21:50 UTC by Daryll
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-03-12 22:21:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Daryll 2003-03-12 21:50:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030206

Description of problem:
I noticed that if I write a mail message and then hit ctrl-shift-L the spell
checker always says that no words are misspelled.

Version-Release number of selected component (if applicable):
evolution-1.2.2-1

How reproducible:
Always

Steps to Reproduce:
1. Create a new mail message
2. Type a misspelled word
3. Press Ctrl-Shift-L
    

Actual Results:  Dialog box says that no misspelled words were found.

Expected Results:  If you misspelled something it should have done something to
check it. 

Additional info:

Comment 1 Jeremy Katz 2003-03-12 22:02:23 UTC
Do you have a language selected for use in the composer settings?

Comment 2 Daryll 2003-03-12 22:11:46 UTC
Nope. Didn't have a language set. Setting english fixed the problem, but that
means we should change the bug. 

Saying no spelling errors found is a problem. It really should warn me that I
had no language selected.

It would be nice if Red Hat at least defaulted to english (but that would be
wrong for other countries) or set the language according user's language
preferences at login time.


Comment 3 Jeremy Katz 2003-03-12 22:21:44 UTC
There are some changes occuring upstream with the gnome-spell configuration
fitting in better with the composer


Note You need to log in before you can comment on or make changes to this bug.