Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!rpi!brutus.cs.uiuc.edu!apple!Apple.COM!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac
Subject: Re: Installing Fonts & DA's in applications
Message-ID: <7115@goofy.Apple.COM>
Date: 10 Mar 90 00:26:41 GMT
Sender: usenet@Apple.COM
Organization: Objects-R-Us,  Apple Computer, Inc.
Lines: 64
References:<39241@apple.Apple.COM> <1990Mar6.112240.1783@hellgate.utah.edu> <39273@apple.Apple.COM> <1990Mar8.202458.22809@eplrx7.uucp>

In article <1990Mar8.202458.22809@eplrx7.uucp> leipold@eplrx7.uucp (Walt 
Leipold) writes:

> As hard as Apple's been pushing the object-oriented applecart (if you
> like mixed metaphors), it's really sad to see them copping out on
> something like this.  "Don't you _dare_ put fonts in application or
> document files!"  

Object-oriented programming has nothing to do with the ability to put 
fonts in applications.  One is a high-level design strategy, and the other 
is a low-level technical detail.

Other people have already noticed that certain print drivers (e.g., Glue) 
won't work properly when the fonts are stored in applications.  That's a 
consequence of the fact that if fonts come from applications then the 
application resource file has to be opened to access the font.  (I would
venture that Glue has never worked properly with fonts stored in 
applications.)

Apple went to some lengths to ensure that this works with background 
LaserWriter printing, but the solution is not ideal.  Glue would have to 
do the same thing (ie, copy the application fonts to its output file.)

From reading the relevant Tech Note (192) it appears that if the 
application font isn't used for printing, then there's no problem.  

Also, note that putting fonts in documents, has rarely worked.  (Old 
timers might recall discussions about putting fonts in MacWrite documents.) 
That's because most applications either don't use the resource fork of 
documents, don't keep it open, or build a list of available fonts when the 
appliation starts up.

> beauties of the original Mac system; you could put any resource
> anywhere, and it would get used at the appropriate time.  And the user
> didn't even have to _know_ about it; the machine just did it right.

This is an overgeneralization.  The Resource Manager does look up 
resources, but it doesn't magically find them where ever they may live.  
In the case of printing, the Resource Manager can't find fonts stored in 
applications, unless that application resource file is opened or the fonts 
are somehow copied to the spool file (or Glue picture).

> Orthogonality and flexibility were Good Things back when the elegance
> of the Mac meant something, but now Apple sells enough of 'em that they
> don't have to bust a gut to keep things elegant and simple.  

Well, if we take out background printing, then things will be simple 
again.  The Glue printer driver still won't work, however.

In general, the system software people have busted many guts trying to 
maintain backward compatibility, while moving the system software forward.  
Fonts in applications do work with background printing, although the Tech 
Note points out the disadvantages.  (Take a look at Tech Note 268 to see 
what the sound people did to accommodate application.)

Things would be much easier if we didn't try to add all those new features 
(like background printing), but I doubt that users would prefer that 
alternative.  

Larry Rosenstein, Apple Computer, Inc.
Object Specialist

Internet: lsr@Apple.com   UUCP: {nsc, sun}!apple!lsr
AppleLink: Rosenstein1