MACOS X TIGER ~~ FINALLY GOT WORD TO WORK WITHOUT FONT PROBLEMS :))) !!!!!

[John McGhie [MVP - Word and Word Macintosh]]

Hi Scott:

On 1/9/05 10:03 AM, in article BF3B936A.DEA4%[email protected],

Word will load whatever fonts are enabled by the system at the moment it
launches. The "500" limit is just an indication, nobody knows what the
limit is, and I think it's system dependent. I am not referring to "font
families", I am referring to "number of lines in the list produced by the
Font menu." I think if that list gets longer than 250 items, problems will
begin to appear. But some users don't seem to get problems at all.

Could this be part of the
problem ­ an incomplete support for Unicode?

Well, I think it could be, but others do not agree. Word 2004 has full
Unicode support, but it gets it from Apple's ATSUI.

Isn¹t there any way for Microsoft to use the Adobe engine?

Short of paying for it? Nope

John, if the developers need me to do any testing, I am WILLING & ABLE to do
what I can to stomp this out!

I know the developers are currently testing proposed fixes for these issues.
If you are able to compile some extensive information from your system,
email me. I will ask them if they can use it. Note: The information
required would be laborious to collect: we would need the list of fonts that
"should appear", the list that appears in TextEdit, and the list that
appears in Word. These lists would need to be in text so they can compare
them.

Cheers

--

Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie <[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 4 1209 1410

 

[Scott Melendez]

John,

What kind of format would they want this in? I can provide screen shots, or
QuickTime movie, or however else they would want it.

 

[John McGhie [MVP - Word and Word Macintosh]]

Hi Scott:

They would want them as text, preferably in an Excel spreadsheet

In order to research the problem, the testers are going to have to create a
script to perform various operations on multiple computers to see which
system configurations the problem appears in

But before we get that far, I need an exact description of the problem you
are experiencing, so I can ask them whether they need any more data.

Please be specific and detailed. They will need the versions and levels of
everything.

Cheers

John,

What kind of format would they want this in? I can provide screen shots, or
QuickTime movie, or however else they would want it.

--

Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie <[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 4 1209 1410

 

[Scott Melendez]

Thanks John.

Where do you want me to send this information?

Scott

 

[John McGhie [MVP - Word and Word Macintosh]]

Best to email it to me. Probably not a good idea to post exact details of
your system configuration

Thanks John.

Where do you want me to send this information?

Scott

--

Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie <[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 4 1209 1410

 

[AeG]

Hi.

I'm having the same !@#$!* problem, could not understand what it i
that you did to fix it.

Could you list it again, step-by-step, super clearly so the non-tec
types can replicate?

I'd appreciate it SO much!!

Thanks,
Ae

 

[John McGhie [MVP - Word and Word Macintosh]]

Well, we think the fix Scott came up with was a bit of a false dawn. It
worked for a while then went sour on him.

The best guess I have at the moment is that it's Apple's ATSUI that's
causing the problem. Apple has apparently put out several updates, and they
haven't seemed to entirely fix the issue. Please don't quote me on that:
personally, I can't see how ATSUI could cause it, or rather, could be the
only cause of it.

Basically, the fix everyone is discussing is: delete both the System and
Microsoft font caches, then power-off restart the system to trigger a
clean-up.

Holding your fonts installed below 500 seems to help (or rather: the issue
seems impossible to solve if there are more than 500 fonts installed).
Chances are, if you can live with only a hundred or so fonts, the issue
won't occur. Some users never get it at all. It does not occur on Jaguar
or Panther.

Cheers

Hi.

I'm having the same !@#$!* problem, could not understand what it is
that you did to fix it.

Could you list it again, step-by-step, super clearly so the non-tech
types can replicate?

I'd appreciate it SO much!!

Thanks,
AeG

--

Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie <[email protected]>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 4 1209 1410