Yes. I don't have office 2003 so can't go further. ----- Original Message ----- From: Lora To: jfw@xxxxxxxxxxxxx Sent: Saturday, December 16, 2006 12:14 AM Subject: RE: Spellcheck in Word 2003 I checked two files for which JAWS is not reading the spell checking box. The first was in 10-point Times New Roman, and the second in 12-point Arial. Peculiar. ------------------------------------------------------------------------------ From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf Of Flor Lynch Sent: Friday, December 15, 2006 5:03 PM To: jfw@xxxxxxxxxxxxx Subject: Re: Spellcheck in Word 2003 Perhaps it is not the font that is causing the problem; but it is known that JAWS gets sluggish with very large fonts. (Perhaps 24 pt and upwards; there shouldn't be this problem below that or around 14, which is 'normal' size.) ----- Original Message ----- From: Lora To: jfw@xxxxxxxxxxxxx Sent: Friday, December 15, 2006 11:01 PM Subject: RE: Spellcheck in Word 2003 I'll check to see if the font is large next time. I did try changing the font for the entire document, but that didn't help. ---------------------------------------------------------------------------- From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf Of Flor Lynch Sent: Friday, December 15, 2006 6:25 AM To: jfw@xxxxxxxxxxxxx Subject: Re: Spellcheck in Word 2003 JAWS does have difficulty with large fonts, if that's your situation. ----- Original Message ----- From: Lora To: jfw@xxxxxxxxxxxxx Sent: Friday, December 15, 2006 1:05 PM Subject: Spellcheck in Word 2003 I believe I posted this question to the list some months back, but I don't think I ever saw a definitive answer. I'd hoped it would be fixed with JAWS 8, but no luck. Sometimes, in Word, when I run spell check, JAWS says: Not in dictionary ... Then it doesn't say anything else. You don't know which word is misspelled, or what suggestion Word is offering. Other times, the spell checker will work properly. If it doesn't work, it will never work for that file, and if it does work, it will always work for that file. I've heard it might be related to font, but that doesn't seem logical to me. If anyone knows what's going on, let me know, especially if there's a way to correct this. Thanks, Lora __________ NOD32 1923 (20061215) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com __________ NOD32 1924 (20061215) Information __________ This message was checked by NOD32 antivirus system. http://www.eset.com