M
MTB
Word 2008 Mac Crashes after Spell check. I have removed it and reloaded it to no avail.
C
CyberTaz
Reinstalling rarely is the the fix for Office-related issues on a Mac and is
*never* the first step to take - it can further compound the problems &
cause others, especially if the removal isn't done properly (BTW: dragging
stuff to the Trash isn't it
).
In order to help resolve it you'll need to provide a bit more information:
What type of Mac & what specific version of OS X?
How did you initially install? (Was this an upgrade of a previous version,
did you migrate from another Mac? Any details would help). Did you or do you
still have a previous version of Office or Word installed on the Mac?
Does this happen with one specific document or *every* time you run the
spell check in *any* document? Describe the document(s) involved including
any foreign language formatting.
Is there any error message that comes up? If so, what is the exact message?
Regards |:>)
Bob Jones
[MVP] Office:Mac
*never* the first step to take - it can further compound the problems &
cause others, especially if the removal isn't done properly (BTW: dragging
stuff to the Trash isn't it
).In order to help resolve it you'll need to provide a bit more information:
What type of Mac & what specific version of OS X?
How did you initially install? (Was this an upgrade of a previous version,
did you migrate from another Mac? Any details would help). Did you or do you
still have a previous version of Office or Word installed on the Mac?
Does this happen with one specific document or *every* time you run the
spell check in *any* document? Describe the document(s) involved including
any foreign language formatting.
Is there any error message that comes up? If so, what is the exact message?
Regards |:>)
Bob Jones
[MVP] Office:Mac
K
kimob
I have the same issue.
I can easily reproduce this problem by opening word, typing in some
words (correct and incorrect), then spell check. After it has finish
and I click OK, word crashes, and the reporter opens up to send the
info to Microsoft.
Macbook CoreDuo 2.0Ghz / 2GB Ram
10.5.1
I had office 2004 installed before, and did an install of 2008, which
in the end allowed me to remove 2004.
I have tried the following:
- Removed Office 2008 Preferences from the systems/users Library
(which seemed to have not fixed anything)
- Removed Microsoft .plists from systems/users Library (which seemed
to have "reset" office, but didn't fix the problem)
I am not in front of my system right now so I cannot copy/paste the
crash info, but I will do that when I get home.
Thanks
Kimo
I can easily reproduce this problem by opening word, typing in some
words (correct and incorrect), then spell check. After it has finish
and I click OK, word crashes, and the reporter opens up to send the
info to Microsoft.
Macbook CoreDuo 2.0Ghz / 2GB Ram
10.5.1
I had office 2004 installed before, and did an install of 2008, which
in the end allowed me to remove 2004.
I have tried the following:
- Removed Office 2008 Preferences from the systems/users Library
(which seemed to have not fixed anything)
- Removed Microsoft .plists from systems/users Library (which seemed
to have "reset" office, but didn't fix the problem)
I am not in front of my system right now so I cannot copy/paste the
crash info, but I will do that when I get home.
Thanks
Kimo
V
vegaz
I had to disable spellchecking altogether just to have Word starting.
Otherwise it kept crashing even before I could write a single letter.
M
MTB
Thanks for responding Bob. Here is my info.
Word 2008 Mac Crashes after Spell check
Like Kimo with the same problem, I can easily reproduce this problem by opening word, typing in some
words (correct and incorrect), then spell check. After it has finish
and I click OK, word crashes, and the reporter opens up to send the
info to Microsoft.
Macbook Pro CoreDuo 2.4Ghz / 4GB Ram
10.5.1
I had office 2004 installed before, and did an install of 2008, which
in the end allowed me to remove 2004.
I have tried the following:
- Removed Office 2008 Preferences from the systems/users Library
(which seemed to have not fixed anything)
- Removed Microsoft .plists from systems/users Library (which seemed
to have "reset" office, but didn't fix the problem)
I have also used the Microsoft "remove Office" and totally reinstalled Office.
I also tried to remove "Normal" and let Word rebuild it again but no fix.
Here is the report in brief.
Microsoft Error Reporting log version: 2.0
Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-02-07 15:37:38 -0500
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.0.071130
Crashed Module Name: CoreFoundation
Crashed Module Version: unknown
Crashed Module Offset: 0x000745e4
Blame Module Name: CoreFoundation
Blame Module Version: unknown
Blame Module Offset: 0x000745e4
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
No foreign language or words used.
No other Office versions on my HD
Thanks for helping.
MTB
Word 2008 Mac Crashes after Spell check
Like Kimo with the same problem, I can easily reproduce this problem by opening word, typing in some
words (correct and incorrect), then spell check. After it has finish
and I click OK, word crashes, and the reporter opens up to send the
info to Microsoft.
Macbook Pro CoreDuo 2.4Ghz / 4GB Ram
10.5.1
I had office 2004 installed before, and did an install of 2008, which
in the end allowed me to remove 2004.
I have tried the following:
- Removed Office 2008 Preferences from the systems/users Library
(which seemed to have not fixed anything)
- Removed Microsoft .plists from systems/users Library (which seemed
to have "reset" office, but didn't fix the problem)
I have also used the Microsoft "remove Office" and totally reinstalled Office.
I also tried to remove "Normal" and let Word rebuild it again but no fix.
Here is the report in brief.
Microsoft Error Reporting log version: 2.0
Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-02-07 15:37:38 -0500
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 12.0.0.071130
Crashed Module Name: CoreFoundation
Crashed Module Version: unknown
Crashed Module Offset: 0x000745e4
Blame Module Name: CoreFoundation
Blame Module Version: unknown
Blame Module Offset: 0x000745e4
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
No foreign language or words used.
No other Office versions on my HD
Thanks for helping.
MTB
T
Teo
Hi,
I have the same problem with an iMac G5 and Leopard (10.5.1). I have
an Eglish version of Office and spelling crashes only when checking
documents in Italian (works for English and German).
Matteo
V
vegaz
Teo said:
yes, I have tried with another machine and the Italian spellchecker
still makes Word crash. There is something wrong there.
J
John McGhie
Yes, this has now been confirmed by Microsoft as a bug. They have a team
working on a fix.
In the meantime, Microsoft Software Development Engineer in Test Curt Laird
has published a work-around:
To work around the problem, try this:
1. Quit Word
2. Go to System>Preferences | International and change your input local to
US English
3. Launch Word
4. Go to Word>Preferences | Spelling and Grammar and disable both
5. Return your input local to Italian
Hope this helps
--
Don't wait for your answer, click here: http://www.word.mvps.org/
Please reply in the group. Please do NOT email me unless I ask you to.
John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]
working on a fix.
In the meantime, Microsoft Software Development Engineer in Test Curt Laird
has published a work-around:
To work around the problem, try this:
1. Quit Word
2. Go to System>Preferences | International and change your input local to
US English
3. Launch Word
4. Go to Word>Preferences | Spelling and Grammar and disable both
5. Return your input local to Italian
Hope this helps
--
Don't wait for your answer, click here: http://www.word.mvps.org/
Please reply in the group. Please do NOT email me unless I ask you to.
John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]
V
vegaz
John McGhie said:
thanks John, I knew it because it was in a thread with me and you that
Curt suggested this workaround, IIRC...
J
John McGhie
Hi Vegaz:
Yeah, I knew that you knew. But these answers are here on display for the
next 100 years or so, so I thought I would put the answer into its "correct"
thread, just so other people looking for the cure to this problem can find
it
That's why I jumped all over Matteo for hijacking threads. He doesn't mean
any harm, he's just trying to get his problems fixed.
Thread hijacking is "business as usual" on UseNet. We all say we shouldn't
do it, and we all keep doing it ‹ it's a fact of life I've just done it
with this response
The "master" of these discussions, communities, or blogs is actually a
UseNet Newsgroup. Most of the MVPs (all of them, I think) are actually
working on a UseNet newsgroup. We don't even see the server you guys are
looking at.
It's just that right now, when we are all trying to find answers to a brand
new product, threadjacking becomes potentially serious for someone looking
for help.
By linking the wrong answers to a specific problem, we potentially send
other newcomer users around a frustrating circle, during which they can make
their problem much worse, for the next ten years
Cheers
--
Don't wait for your answer, click here: http://www.word.mvps.org/
Please reply in the group. Please do NOT email me unless I ask you to.
John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]
Yeah, I knew that you knew. But these answers are here on display for the
next 100 years or so, so I thought I would put the answer into its "correct"
thread, just so other people looking for the cure to this problem can find
it
That's why I jumped all over Matteo for hijacking threads. He doesn't mean
any harm, he's just trying to get his problems fixed.
Thread hijacking is "business as usual" on UseNet. We all say we shouldn't
do it, and we all keep doing it ‹ it's a fact of life
I've just done itwith this response
The "master" of these discussions, communities, or blogs is actually a
UseNet Newsgroup. Most of the MVPs (all of them, I think) are actually
working on a UseNet newsgroup. We don't even see the server you guys are
looking at.
It's just that right now, when we are all trying to find answers to a brand
new product, threadjacking becomes potentially serious for someone looking
for help.
By linking the wrong answers to a specific problem, we potentially send
other newcomer users around a frustrating circle, during which they can make
their problem much worse, for the next ten years
Cheers
thanks John, I knew it because it was in a thread with me and you that
Curt suggested this workaround, IIRC...
--
Don't wait for your answer, click here: http://www.word.mvps.org/
Please reply in the group. Please do NOT email me unless I ask you to.
John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]
V
vegaz
John McGhie said:Yeah, I knew that you knew. But these answers are here on display for the
next 100 years or so, so I thought I would put the answer into its "correct"
thread, just so other people looking for the cure to this problem can find
it
OK John, I got the point. Maybe the reason I thought the problem of
Matteo could simply be the same that I have is that I have never
experienced a "real" Word crash on startup, but rather, as you said in
the other thread, just a crash "immediately after" the startup.
J
John McGhie
Yeah: Crash during startup is quite common, but some users never get them.
I haven't had one since the beta, when I had a Normal template full of
rubbish
Cheers
--
Don't wait for your answer, click here: http://www.word.mvps.org/
Please reply in the group. Please do NOT email me unless I ask you to.
John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]
I haven't had one since the beta, when I had a Normal template full of
rubbish
Cheers
OK John, I got the point. Maybe the reason I thought the problem of
Matteo could simply be the same that I have is that I have never
experienced a "real" Word crash on startup, but rather, as you said in
the other thread, just a crash "immediately after" the startup.
--
Don't wait for your answer, click here: http://www.word.mvps.org/
Please reply in the group. Please do NOT email me unless I ask you to.
John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]
C
Cassandra
Hi John
Re My problem with Word 2004 crashing when I use spell check.
Yes the problem has been happening with all documents and the language is marked English (Australian).
I've now followed your advice above - removed Australian from the input menu, kept US and it seems to have solved the problem. Also, it only happens on my Mac (not my PC) and only to me, not my colleagues who all use Macs.
Sorry - before I posted the first question I DID search for this thread and didn't find it - used the exact same words today and it came up...
Thanks
Cassandra
Re My problem with Word 2004 crashing when I use spell check.
Yes the problem has been happening with all documents and the language is marked English (Australian).
I've now followed your advice above - removed Australian from the input menu, kept US and it seems to have solved the problem. Also, it only happens on my Mac (not my PC) and only to me, not my colleagues who all use Macs.
Sorry - before I posted the first question I DID search for this thread and didn't find it - used the exact same words today and it came up...
Thanks
Cassandra
C
Cassandra
I spoke too soon - problem not solved, curses. I've tried variations with the input language, to no avail. I've realised that it doesn't happen if there are no spelling errors and when it does happen, a dialogue box comes up saying "Spell/grammar check is complete. Text set to (no proofing) was skipped...etc" (even though there's no special formatting).
Here's the error message:
Microsoft Error Reporting log version: 1.0
Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-03-11 15:33:31 +1100
Application Name: Microsoft Word
Application Version: 11.3.8.070817
Module Name: MCPZ.stb
Module Version: 11.4.0.080117
Module Offset: 0x0006aed8
Extra app info: Reg=English Loc=0x0409
Thread 0 crashed:
# 1 0x005dbe68 in (MCPZ.stb + 0x0006aed8)
# 2 0x02381f34 in (Microsoft Word + 0x003624d4)
# 3 0x0261dea0 in (Microsoft Word + 0x005fe440)
# 4 0x0212f08c in (Microsoft Word + 0x0010f62c)
# 5 0x021d4fe4 in (Microsoft Word + 0x001b5584)
# 6 0x026e1e14 in (Microsoft Word + 0x006c23b4)
# 7 0x020f3b70 in (Microsoft Word + 0x000d4110)
# 8 0x01020820 in (Microsoft_Office_2001Z + 0x0000a280)
# 9 0x01020bb8 in (Microsoft_Office_2001Z + 0x0000a618)
# 10 0x010502f8 in (Microsoft_Office_2001Z + 0x00039d58)
# 11 0x0104fddc in (Microsoft_Office_2001Z + 0x0003983c)
# 12 0x0104fdac in (Microsoft_Office_2001Z + 0x0003980c)
# 13 0x00593b38 in (MCPZ.stb + 0x00022ba8)
# 14 0x901c516c in ___CFRunLoopDoTimer + 0x000000F0 (CoreFoundation + 0x0000516c)
# 15 0x901c24cc in ___CFRunLoopRun + 0x000005C4 (CoreFoundation + 0x000024cc)
# 16 0x901c69e0 in _CFRunLoopRunSpecific + 0x00000144 (CoreFoundation + 0x000069e0)
# 17 0x92886e0c in _RunCurrentEventLoopInMode + 0x000000A8 (HIToolbox + 0x00006e0c)
# 18 0x9288d4b0 in _ReceiveNextEventCommon + 0x000000F0 (HIToolbox + 0x0000d4b0)
# 19 0x928fe6b0 in _ReceiveNextEventInMode + 0x00000044 (HIToolbox + 0x0007e6b0)
# 20 0x0059381c in (MCPZ.stb + 0x0002288c)
# 21 0x020f3ab8 in (Microsoft Word + 0x000d4058)
# 22 0x020205f8 in (Microsoft Word + 0x00000b98)
# 23 0x01023460 in (Microsoft_Office_2001Z + 0x0000cec0)
# 24 0x02020074 in (Microsoft Word + 0x00000614)
# 25 0x02b070ac in (Microsoft Word + 0x00ae764c)
PPC Thread State:
srr0: 0x005dbe68 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x20000007 lr: 0x02381f34 ctr: 0x006b5300 mq:0x00000000
r0: 0x006b5300 r1: 0xbfffdff0 r2: 0x0077d000 r3:0x00000000
r4: 0x00000001 r5: 0x006d2580 r6: 0x01e3fbb7 r7:0x00000000
r8: 0x00000000 r9: 0x00000000 r10: 0x018001c8 r11:0x00001100
r12: 0x0077daa0 r13: 0x00000000 r14: 0x00000000 r15:0x00000001
r16: 0x00000058 r17: 0x00000157 r18: 0x00000004 r19:0xbfffeb30
r20: 0x00df00a7 r21: 0x00000006 r22: 0x00000000 r23:0x031750c0
r24: 0x0317343c r25: 0x0317b850 r26: 0x0316cf74 r27:0x03171a78
r28: 0x01e3f800 r29: 0x00000000 r30: 0x00000006 r31:0x00000001
Thread 1:
# 1 0x900127c8 in _clock_sleep_trap + 0x00000008 (libSystem.B.dylib + 0x000127c8)
# 2 0x9000d9b8 in _nanosleep + 0x00000078 (libSystem.B.dylib + 0x0000d9b8)
# 3 0x9002d9a8 in _sleep + 0x00000048 (libSystem.B.dylib + 0x0002d9a8)
# 4 0x0177115c in _MerpUnregisterCFMFragment + 0x00000BAC (ShMem + 0x0006715c)
# 5 0x01770628 in _MerpUnregisterCFMFragment + 0x00000078 (ShMem + 0x00066628)
# 6 0x01770754 in _MerpUnregisterCFMFragment + 0x000001A4 (ShMem + 0x00066754)
# 7 0x01771234 in _MerpUnregisterCFMFragment + 0x00000C84 (ShMem + 0x00067234)
# 8 0x9002492c in __pthread_body + 0x00000024 (libSystem.B.dylib + 0x0002492c)
PPC Thread State:
srr0: 0x900127c8 srr1: 0x0000d030 vrsave: 0x00000000
xer: 0x00000004 lr: 0x9000d9b8 ctr: 0x900127c0 mq:0x00000000
r0: 0xffffffc2 r1: 0xf0080af0 r2: 0xf0080ac4 r3:0x00000507
r4: 0x00000001 r5: 0x00000001 r6: 0x00000000 r7:0xf0080b30
r8: 0x00000000 r9: 0x00007850 r10: 0x2fd6be85 r11:0xa000470c
r12: 0x900127c0 r13:
Here's the error message:
Microsoft Error Reporting log version: 1.0
Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-03-11 15:33:31 +1100
Application Name: Microsoft Word
Application Version: 11.3.8.070817
Module Name: MCPZ.stb
Module Version: 11.4.0.080117
Module Offset: 0x0006aed8
Extra app info: Reg=English Loc=0x0409
Thread 0 crashed:
# 1 0x005dbe68 in (MCPZ.stb + 0x0006aed8)
# 2 0x02381f34 in (Microsoft Word + 0x003624d4)
# 3 0x0261dea0 in (Microsoft Word + 0x005fe440)
# 4 0x0212f08c in (Microsoft Word + 0x0010f62c)
# 5 0x021d4fe4 in (Microsoft Word + 0x001b5584)
# 6 0x026e1e14 in (Microsoft Word + 0x006c23b4)
# 7 0x020f3b70 in (Microsoft Word + 0x000d4110)
# 8 0x01020820 in (Microsoft_Office_2001Z + 0x0000a280)
# 9 0x01020bb8 in (Microsoft_Office_2001Z + 0x0000a618)
# 10 0x010502f8 in (Microsoft_Office_2001Z + 0x00039d58)
# 11 0x0104fddc in (Microsoft_Office_2001Z + 0x0003983c)
# 12 0x0104fdac in (Microsoft_Office_2001Z + 0x0003980c)
# 13 0x00593b38 in (MCPZ.stb + 0x00022ba8)
# 14 0x901c516c in ___CFRunLoopDoTimer + 0x000000F0 (CoreFoundation + 0x0000516c)
# 15 0x901c24cc in ___CFRunLoopRun + 0x000005C4 (CoreFoundation + 0x000024cc)
# 16 0x901c69e0 in _CFRunLoopRunSpecific + 0x00000144 (CoreFoundation + 0x000069e0)
# 17 0x92886e0c in _RunCurrentEventLoopInMode + 0x000000A8 (HIToolbox + 0x00006e0c)
# 18 0x9288d4b0 in _ReceiveNextEventCommon + 0x000000F0 (HIToolbox + 0x0000d4b0)
# 19 0x928fe6b0 in _ReceiveNextEventInMode + 0x00000044 (HIToolbox + 0x0007e6b0)
# 20 0x0059381c in (MCPZ.stb + 0x0002288c)
# 21 0x020f3ab8 in (Microsoft Word + 0x000d4058)
# 22 0x020205f8 in (Microsoft Word + 0x00000b98)
# 23 0x01023460 in (Microsoft_Office_2001Z + 0x0000cec0)
# 24 0x02020074 in (Microsoft Word + 0x00000614)
# 25 0x02b070ac in (Microsoft Word + 0x00ae764c)
PPC Thread State:
srr0: 0x005dbe68 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x20000007 lr: 0x02381f34 ctr: 0x006b5300 mq:0x00000000
r0: 0x006b5300 r1: 0xbfffdff0 r2: 0x0077d000 r3:0x00000000
r4: 0x00000001 r5: 0x006d2580 r6: 0x01e3fbb7 r7:0x00000000
r8: 0x00000000 r9: 0x00000000 r10: 0x018001c8 r11:0x00001100
r12: 0x0077daa0 r13: 0x00000000 r14: 0x00000000 r15:0x00000001
r16: 0x00000058 r17: 0x00000157 r18: 0x00000004 r19:0xbfffeb30
r20: 0x00df00a7 r21: 0x00000006 r22: 0x00000000 r23:0x031750c0
r24: 0x0317343c r25: 0x0317b850 r26: 0x0316cf74 r27:0x03171a78
r28: 0x01e3f800 r29: 0x00000000 r30: 0x00000006 r31:0x00000001
Thread 1:
# 1 0x900127c8 in _clock_sleep_trap + 0x00000008 (libSystem.B.dylib + 0x000127c8)
# 2 0x9000d9b8 in _nanosleep + 0x00000078 (libSystem.B.dylib + 0x0000d9b8)
# 3 0x9002d9a8 in _sleep + 0x00000048 (libSystem.B.dylib + 0x0002d9a8)
# 4 0x0177115c in _MerpUnregisterCFMFragment + 0x00000BAC (ShMem + 0x0006715c)
# 5 0x01770628 in _MerpUnregisterCFMFragment + 0x00000078 (ShMem + 0x00066628)
# 6 0x01770754 in _MerpUnregisterCFMFragment + 0x000001A4 (ShMem + 0x00066754)
# 7 0x01771234 in _MerpUnregisterCFMFragment + 0x00000C84 (ShMem + 0x00067234)
# 8 0x9002492c in __pthread_body + 0x00000024 (libSystem.B.dylib + 0x0002492c)
PPC Thread State:
srr0: 0x900127c8 srr1: 0x0000d030 vrsave: 0x00000000
xer: 0x00000004 lr: 0x9000d9b8 ctr: 0x900127c0 mq:0x00000000
r0: 0xffffffc2 r1: 0xf0080af0 r2: 0xf0080ac4 r3:0x00000507
r4: 0x00000001 r5: 0x00000001 r6: 0x00000000 r7:0xf0080b30
r8: 0x00000000 r9: 0x00007850 r10: 0x2fd6be85 r11:0xa000470c
r12: 0x900127c0 r13:
R
Redneckerson
Hello..Has this issue been solved? I am a NOVICE NOVICE ROOKIE at anything mac (read less than a month). I installed Office 2008 for mac and I noticed it does NOT check for spelling errors when I have it set to do so automatically. When I do it manually, it ONLY checks in the footer/header, while ignoring clearly misspelled words. Then when I tell it to check the next word it crashes and prompts me to send a report. Any help? (THANKS in advance.)
J
John McGhie
Welcome to Mac
Right: The Office 2008 Spelling Checker has some nasty bugs in it that o
make it crash, particularly in specific languages, and we're waiting for
fixes.
Keep sending the reports: it will hasten the speed with which the fixes
arrive.
Your spelling is controlled by the "Language" marked in the text of the
document. If you have managed to mark the text of the document with the "No
Proofing" Language (by checking the "Do not check spelling or grammar" box)
then, it ... Ummm ... Won't
To get you going, Select the whole of the text, and use Tools>Language to
set the text to the language you want to use. Make sure "Do not check" is
set to "OFF".
Then look up Custom Dictionary in the Help and make sure that it is set to
"(none)" -- No Language. This makes sure that your custom dictionary can be
used for any one of the 29 flavours of English you may encounter in pasted
text.
Finally, go to Tools>Spelling and Grammar and hit "Recheck Document". This
resets all the words that have previously been "Ignored" during a spell
check.
Then come back and tell us what has changed. These problems can be a bit of
a steeple-chase to track down once they go bad.
Hope this helps
--
Don't wait for your answer, click here: http://www.word.mvps.org/
Please reply in the group. Please do NOT email me unless I ask you to.
John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]
Right: The Office 2008 Spelling Checker has some nasty bugs in it that o
make it crash, particularly in specific languages, and we're waiting for
fixes.
Keep sending the reports: it will hasten the speed with which the fixes
arrive.
Your spelling is controlled by the "Language" marked in the text of the
document. If you have managed to mark the text of the document with the "No
Proofing" Language (by checking the "Do not check spelling or grammar" box)
then, it ... Ummm ... Won't
To get you going, Select the whole of the text, and use Tools>Language to
set the text to the language you want to use. Make sure "Do not check" is
set to "OFF".
Then look up Custom Dictionary in the Help and make sure that it is set to
"(none)" -- No Language. This makes sure that your custom dictionary can be
used for any one of the 29 flavours of English you may encounter in pasted
text.
Finally, go to Tools>Spelling and Grammar and hit "Recheck Document". This
resets all the words that have previously been "Ignored" during a spell
check.
Then come back and tell us what has changed. These problems can be a bit of
a steeple-chase to track down once they go bad.
Hope this helps
--
Don't wait for your answer, click here: http://www.word.mvps.org/
Please reply in the group. Please do NOT email me unless I ask you to.
John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Sydney, Australia. S33°53'34.20 E151°14'54.50
+61 4 1209 1410, mailto:[email protected]