Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!ukma!usenet.ins.cwru.edu!eagle!data.nas.nasa.gov!noc.arc.nasa.gov!gutierre
From: gutierre@noc.arc.nasa.gov (Robert Gutierrez)
Newsgroups: comp.sys.amiga.applications
Subject: Re: Post and Mkbmap
Message-ID: <1991Jun14.070051.18716@nas.nasa.gov>
Date: 14 Jun 91 07:00:51 GMT
References: <1991Jun13.195310.8387@javelin.sim.es.com>
Sender: news@nas.nasa.gov
Reply-To: gutierre@noc.arc.nasa.gov (Robert Gutierrez)
Organization: The Ranma Project
Lines: 29

dingebre@imp.es.com (David Ingebretsen) writes:
> I have been trying to use these two applications with varying success.
> For example, a post script file generated by TeX at my work that prints
> without error on a post script printer will not run on Post. Adobe type I
> fonts that will load into Post will not work with Mkbmap.

I used the standard Adobe Type 1's from the IBM Adobe Type Manager, and they
worked fine.  Strange that the docs mention the use of Type 1 in _ascii_
format, but the Type 1's in ATM were binary as far as ed was concerned.

I created a few dozen fonts with mkbmap, and they all seem fine!

First, you *MUST* use post.library v1.5, NOT v1.3, as it will choke on the
older library version.  my command line is:

	mkbmap -n fonts:testfont/* Helvetica 32

the "-n" is to update the .fonts file (ie: Fixfonts) and the "32" is the
point size.

System: A3000/25, 2.0, 2mb-chip/4mb-fast, 50mb/hd, 2 Syquests.

I've also used the "Shadow Maker" utility to make shadows on the fonts,
and it's worked fine (except their colortext-type wedge is giving me problems
on a piece of titling software, and I don't exactly like 3 bit plane color
fonts also).


	robert