"custom dictionary not available" issue

[How...@officeformac.com]

Version: 2008 Operating System: Mac OS X 10.6 (Snow Leopard) Processor: Intel Every 2-3 weeks I get the message that my custom dictionary cannot be accessed. I do what others have posted here and on other forums: I go into Preferences/spelling and grammar, make sure no language is selected, check the dictionary file for odd things (asterisks, etc.) and clear. But both times I've tried it, it doesn't fix the problem, and I start a new custom dictionary...

Which works for a few weeks until AGAIN the dialog box pops up saying the Custom Dic. is not available. I've repeated twice now and since it keeps happening, I thought it'd be good to ask...

I am new to Mac but far from new to Word.

thanks!

howardm

[John McGhie]

Hi Howard:

We really don't know "why" this happens, but we can tell you "what" happens:
the Custom Dictionary gets into the wrong encoding and Word can't read it.

I think there is some embarrassing bug in the system where all parts of Word
write to the dictionary in Unicode except one, which writes in ANSI, meaning
that if that module ever fires, the dictionary gets corrupted.

Normally, simply editing the dictionary to add and remove a space, then save
it, will fix it.

I am guessing that this issue occurs when the spelling engine (not the
dictionary) somehow switches to a language other than English.

Sorry to not know...

Cheers

On 16/02/10 11:37 AM, in article 59bb2...@webcrossing.JaKIaxP2ac0,
"How...@officeformac.com" <How...@officeformac.com> wrote:

This email is my business email -- Please do not email me about forum
matters unless you intend to pay!

--

John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:jo...@mcghie.name

[How...@officeformac.com]

John: Much thanks; it's always good to understand even if there isn't a fix, per se...I mean, it's "Mactopia," not UTOPIA.

Howard

> Hi Howard:
>
> We really don't know "why" this happens, but we can tell you "what" happens:
> the Custom Dictionary gets into the wrong encoding and Word can't read it.
>
> I think there is some embarrassing bug in the system where all parts of Word
> write to the dictionary in Unicode except one, which writes in ANSI, meaning
> that if that module ever fires, the dictionary gets corrupted.
>
> Normally, simply editing the dictionary to add and remove a space, then save
> it, will fix it.
>
> I am guessing that this issue occurs when the spelling engine (not the
> dictionary) somehow switches to a language other than English.
>
> Sorry to not know...
>
> Cheers
>
> On 16/02/10 11:37 AM, in article 59bb2...@webcrossing.JaKIaxP2ac0,