Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!ingr!b11!dwig
From: dwig@b11.ingr.com (David Wiggins)
Newsgroups: comp.windows.x
Subject: Re: Banish 'font not found' errors forever!
Message-ID: <6847@b11.ingr.com>
Date: 15 Dec 89 00:03:02 GMT
References: <6808@b11.ingr.com> <8912121349.AA23926@expire.lcs.mit.edu>
Organization: Intergraph Corp. Huntsville, AL
Lines: 21

In article <8912121349.AA23926@expire.lcs.mit.edu>, rws@EXPO.LCS.MIT.EDU (Bob Scheifler) writes:

>     The sendfont extension allows clients to
>     propogate fonts on demand with no intervention by the user.
> 
> Well, only sort of.  You must be assuming the entire contents of all those
> fonts are embedded in the application, rather than being in files (blech).

The font data can come from anywhere: it can be embedded in the code,
generated on the fly, or stored in a file.

> Otherwise, finding those files is equivalent to finding a font server.

Lots of existing applications and utilities find files that they need at
run time with no help from the user, usually by looking in fixed
locations.  Maybe that's inelegant, but it seems to be widely accepted
practice.  Would it be as acceptable for a client to expect a certain
machine name to be the fontserver?  Maybe so; I can't say.

David P. Wiggins			uunet!ingr!dwig or dwig@ingr.com
Software Analyst, Intergraph X-Team