Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!lll-winken!uunet!tektronix!tekig5!tekig4!briand
From: briand@tekig4.LEN.TEK.COM (Brian Diehm)
Newsgroups: comp.sys.mac
Subject: Re: MS Word 4.0 --- First (and Last) Impressions
Keywords: Bugs
Message-ID: <3956@tekig4.LEN.TEK.COM>
Date: 2 May 89 18:17:16 GMT
References: <3914@tekig4.LEN.TEK.COM> <29495@apple.Apple.COM> <3950@tekig4.LEN.TEK.COM>
Organization: Tektronix Inc., Beaverton, Or.
Lines: 35


I have griped about MS Word 4.0 here before, and I have promised to stop
because I didn't want to be accused of Microsoft bashing.

But. This is simply too much. I am now thoroughly pissed off at these arrogant
jerks.

Microsoft has not even bothered to bring their program into compliance with
the standard usage of the system. WORD 4.0 STILL REMEMBERS FONT ASSIGNMENTS
BY FONT NUMBER INSTEAD OF FONT NAME. There was some excuse in version 3; the
system was still in flux and only far-seeing companies did it right back then.

There is no excuse today. Apple first published Tech Note #191 on April 2,
1988. It was last revised on August 1, 1988. It specifies the use of font names
rather than numbers. It even gives sample code of how to do it right! The
reason is specifically because the Font/DA Mover no longer even attempts to
maintain standardized font numbers. When you install a font now, if there is a
number conflict the Font/DA Mover will simply assign a new number to the font.

How does this affect you? It means that if you take your magnum opus to some-
one else's machine, all your text could lose its font assignment and appear in
Geneva (or whatever the default application font is set to). Or if that system
uses that font number for something else, then your tome might just appear in
something else entirely, like, say, Zapf Dingbats or Carta! The problem is its
most insidious when you send your book off to that nice Linotronic service
bureau to get 2450 dpi film masters at many $ a shot.

Of course, the solution is well-known. PageMaker 3.0, by contrast, has done it
right for a couple of years now. Apparently Microsoft simply couldn't be
bothered. Chuq, where were you? Too busy reconfiguring the menus and having fun?

-- 
-Brian Diehm     (SDA - Standard Disclaimers Apply)
Tektronix, Inc.
briand@tekig4.TEK.COM   or  {decvax,cae780,uw-beaver}!tektronix!tekig4!briand