Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!lll-winken!sun-barr!ames!dftsrv!mimsy!chris
From: chris@mimsy.umd.edu (Chris Torek)
Newsgroups: comp.text
Subject: Re: mftobdf, having problems
Message-ID: <21288@mimsy.umd.edu>
Date: 14 Dec 89 23:06:31 GMT
References: <863@mti.mti.com> <4225@amelia.nas.nasa.gov>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 31

In article <4225@amelia.nas.nasa.gov> lonhyn@sun252..nas.nasa.gov
(Lonhyn T. Jasinskyj) writes:			(two dots??)
>I'm having problems with mftobdf complaining about a missing font ...

You have old, undocumented software (not surprising since texx2 comes
with old, undocumented software).

>My problem is probably a lack of understanding of box, blank, and invisible
>fonts.  As far as I undertand they are pseudo-fonts without bitmaps
>and information only from tfm files that are used for mapping out
>space on a page.  What are the differences among them?

box: produces little boxes like those in Chapter 11 of {\it The \TeX book}
(see Exercise 11.5).  blank: produces blank space.  invis: produces blank
space.  Blank and invis are thus `the same'; the difference is that box
and blank fonts produce complaints (warnings, not errors), while invis
is silent.

MC-TeX (the name changed since there are at least three different
`C-TeX' systems out there, all different) calls these `box', `blank',
and `tfm' (the name `invis' is still recognised but is scheduled to
vanish someday).

>font	blank	*	1	/usr/local/lib/tex/tfm/%s.tfm
>font	pk	*	3	/usr/local/lib/tex/pk_bw/%m/%f.pk

These *must* appear in the other order, since the file is searched in
order, and the first match is always taken.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@cs.umd.edu	Path:	uunet!mimsy!chris