Re: Second screen scrolling bug. Has it gone away?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

In article <C0A66AC4.3A1D4%john@xxxxxxxxxxx>, John McGhie [MVP - Word
and Word Macintosh] <john@xxxxxxxxxxx> wrote:

The "Corrupt Fonts" bug and the "Can't Save" bug are all that it will take
to keep this professional wordsmith away from Tiger :-)

If I upgrade, I "might not" get those bugs. If I don't upgrade, I know for
certain that I "won't" get them.

No-brainer, really :-)

I have been Tiggered from the get go. I never see either of those as a
Mac bug. I don't see the second one at all, since I don't edit files
from an external server. I'd always use some kind of source control to
check the whole thing out, edit locally and check it back in. The
problem appears to be related to Word's cavalier choice of directories
for work files without checking whether it has write access to the
directory as well as its contents. Not what I'd call a Tiger bug.

Corrupt fonts? I have only seen as a corrupt font cache, and the only
evidence was a beach ball at startup while Word, and Word alone,
claimed it was optimising fonts. I saw that in Panther too.

Other font issues flowed from the transition to Word 2004 from v.X.
Nothing to do with Panther to Tiger. All of those were due to
Microsoft's cavalier attitude to my font collection as it sprayed new
Unicode versions of its own identically named little favourites into
the wrong directories, unbidden and unannounced.

I had a play with Word on an Intel iMac in the London Apple store. Its
performance under Rosetta is no worse than on my 1GHz Powerbook G4. Not
much better either. On those grounds, if you must buy a lappy at the
end of the month, you might as well get a PC at half the price.

I gotta say that equating once off font corruption to the malware
maelstrom over on the dark side has me puzzled.

I'm keeping my PowerBook till Microsoft and Adobe have universal binary
versions of Office and CS respectively.

However, if the rumoured 8-way Conroe makes its way into a Mac sometime
soon, I might break down and buy a quad G5 killer desktop for video
editing. I'd never buy a new machine till it is at least 4 times
quicker than the one I have already.
.

Relevant Pages

  • Re: Disabel Font Menu Optimization
    ... All programs seem to give the same font menu ... >> How did you do the Tiger upgrade? ... Upgrade, Archive and Install, Erase and ...
    (microsoft.public.mac.office)
  • Re: PostScript fonts in MsOffice 2007
    ... a "bug" is a fault or flaw in the system that results in improper operation. ... However, there is at least one consequence of that operation-as-designed of the font substitution system, it gives an intended result, the font is substituted according to the rule set; however, you see a failure to render the Cyrillic glyphs properly. ... I would suggest contacting Monotype and seek their advice on changing your corporate font to one that has the look and feel you want and whose files will work with Office 2007 and the operating system possibly an Open Type Gill Sans. ... Check your computer for any variety of Gill Sans in Truetype format. ...
    (microsoft.public.word.printingfonts)
  • Re: Font switching on different sizes???
    ... I'm not sure if I have to be happy that I managed to identify a rare MFC ... It is very easy to reproduce the bug... ... also with every font specified... ... and when specifying positive value instead - The bug ...
    (microsoft.public.vc.mfc)
  • Re: StyleRef Formatting Frustrations
    ... I do not have to protect the document in order to provoke the bug. ... macros and templates for Microsoft Word ... the font change immediately. ... apply the styles prior to inserting form fields. ...
    (microsoft.public.word.docmanagement)
  • Re: PostScript fonts in MsOffice 2007
    ... you will better be able to offer the managers good advice. ... stipulation of the request for improving the company font, ... I mean how to formulate them the request 'To buy Gill Sans Cyr Open Type or ... I am not sure that what you are seeing is a "bug" in the strict sense. ...
    (microsoft.public.word.printingfonts)