Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!beta!unm-la!unmvax!turing.unm.edu!mike
From: mike@turing.unm.edu.unm.edu (Michael I. Bushnell)
Newsgroups: comp.windows.x
Subject: Re: Re: X PostScript previewer (again) - (nf)
Message-ID: <642@unmvax.unm.edu>
Date: Fri, 25-Sep-87 05:35:43 EDT
Article-I.D.: unmvax.642
Posted: Fri Sep 25 05:35:43 1987
Date-Received: Sun, 27-Sep-87 02:27:22 EDT
References: <8709211613.AA10595@renoir.Berkeley.EDU>
Sender: news@unmvax.unm.edu
Reply-To: mike@turing.unm.edu.UUCP (Michael I. Bushnell)
Distribution: world
Organization: University of New Mexico, Albuquerque
Lines: 30

In article <8709211613.AA10595@renoir.Berkeley.EDU> john@RENOIR.BERKELEY.EDU (John Coker) writes:

>    It may be possible to get the shapes from METAFONT, but this will almost
>certainly require a partial rewrite of the METAFONT program itself since the
>character shapes are described on high-level objects like strokes.
>
>					John

Actually it isn't that hard.  METAFONT produces 2 kinds of files when given
foo.mf as input.

1) a tfm -- the font metric table for TeX.  You can convert this to the 
	      proper form for whatever formatter you use (troff, TeX, etc.)

2) A gf -- the pixel map.

The entire job of metafont is converting strokes into pixel maps.  The maps
are in a Generic Font format which is designed to be easily convertable
to whatever form the printing software desires.





					Michael I. Bushnell
					a/k/a Bach II
					mike@turing.UNM.EDU
---
You can't hurt me!!  I have an ASSUMABLE MORTGAGE!!
				-- Zippy the Pinhead