home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!CAMB.COM!BOB
- Errors-to: epmdf@YMIR.BITNET
- Organization: Cambridge Computer Associates, Inc.
- X-Envelope-to: PMDF-L@IRLEARN.BITNET
- X-VMS-To: IN%"DAN@INNOSOFT.COM"
- X-VMS-Cc: IN%INFO-PMDF,TINKELMAN
- MIME-version: 1.0
- Content-type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-transfer-encoding: 7BIT
- Message-ID: <01GNU9B7W60I94E1OY@INNOSOFT.COM>
- Date: Fri, 21 Aug 92 19:15:07 GMT
- Sender: PMDF Distribution List <PMDF-L@IRLEARN>
- From: Bob Tinkelman <bob@CAMB.COM>
- Subject: RE: PMDF-FAX installation and [ghostscript]fontmap.
- X-To: DAN@INNOSOFT.COM
- X-cc: ipmdf@INNOSOFT.COM
- Newsgroups: bit.listserv.pmdf-l
- Lines: 20
-
- > in V4.2 we'll make the installation dio what we do with things like
- > master.com: rename the previous master.com to master.old.
-
- Thanks. That'll be an improvement. But using the case of master.com
- as an analogy, there you have made changes to avoid the necessity of
- user editing of the command file. Is there a way that you could do
- the same thing here?
-
- Rough idea: Have a file called local_fontmap which is in the same
- format as fontmap. If it exists (in [ghostscript]) it is invoked
- either just before fontmap, or just after, depending on which makes
- the implementation easier. If it's invoked before, then the functions
- that are used in fontmap would have to be changed so they would do
- nothing if the named font already existed. If it's invoked after,
- then the functions could simply override prior font definitions.
-
- Every time we can eliminate something that I need to remember to do after
- running an installation, it's a *big* help.
-
- Thanks for all your assistance - Bob
-