Article View: comp.text
Article #6561mftobdf, having problems
From: lonhyn Lonhyn T. Jasinskyj
Date: Thu, 14 Dec 1989 20:55
Date: Thu, 14 Dec 1989 20:55
52 lines
2785 bytes
2785 bytes
I'm having problems with mftobdf complaining about a missing font when
I try to convert a font from pk to bdf format in preparation for later
conversion to snf format (which is then used for my texx2 previewer).
What confuses me is that two routines in one of Torek's libraries
(namely box_read and blank_read in tfmfont.c) call do_read() with
the third argument ("complain") set to 1 explicitly. This causes
do_read to print "Warning, no font for fontname" and things seem to
abort from there.
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?
The following is my fontdesc file:
#
# Sample C-TeX font configuration file.
#
# N.B.: choose only one of `box' or `blank' TFM fonts.
# TYPE SPEC SLOP PATH
#
font blank * 1 /usr/local/lib/tex/tfm/%s.tfm
#font box * 1 /usr/local/lib/tex/tfm/%s.tfm
# TYPE SPEC SLOP PATH
font pk * 3 /usr/local/lib/tex/pk_bw/%m/%f.pk
It seems to be read correctly. In font.c of Torek's library code (which
mftobdf.c calls) there is a whole section of ADDFONT() macros. These
link in the various font reading and operation routines. (This is in
fontinit() which mftobdf calls). This is how I eventually get to the
fatal call to do_read().
In case you are wondering, the files for a particular font (both tfm
and pk) do exist in the place mentioned. It does not seem that I am
having problems with the pk part at this time. I have been through
the instructions for installing fonts that come with TeXx2 a number
of times. Obviously, I am doing something wrong. If only someone
could point to the problem staring me in the face...
Any help would be appreciated.
Lonnie
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Email to: lonhyn@sun252.nas.nasa.gov Human at: 415-694-3989
Disclaimer: All views and opinions expressed here belong
entirely to the organization mentioned above. They
have sole rights to my every waking thought.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Technical Details
Message-ID:
<4225@amelia.nas.nasa.gov>Path:
arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!amelia!sun252!lonhynReferences:
<863@mti.mti.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!amelia!sun252!lonhyn From: lonhyn@sun252..nas.nasa.gov (Lonhyn T. Jasinskyj) Newsgroups: comp.text Subject: mftobdf, having problems Message-ID: <4225@amelia.nas.nasa.gov> Date: 14 Dec 89 20:55:28 GMT References: <863@mti.mti.com> Sender: news@amelia.nas.nasa.gov Reply-To: lonhyn@sun252.nas.nasa.gov (Lonhyn T. Jasinskyj) Organization: NASA Ames Research Lines: 52