[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: fontinst 1.801 -- still worse

At 08:30 PM 6/8/99 -0400, Fernando Q. Gouvea wrote:
>**** On Tue, 8 Jun 1999 22:03:04 +0100 (BST), "Sebastian Rahtz" <sebastian.rahtz@computing-services.oxford.ac.uk> said:
>  > Apparently so far only the people who developed the fontinst
>  > stuff were using it seriously, and they already know all the
>  > details, which are _not_ explained in the documentation ;-)
>SR> evidence to the contrary is Alan Hoenig, who does not really class as a
>SR> fontinst developer, but who certainly understands it
>SR> but i concede there may be some truth in your remark...
>Well, I use fontinst, and I wouldn't dream of getting involved in
>development... It *is* unfortunate that so many of the details are omitted
>from the documentation, but I've managed to use fontinst to set up several
>of my Type 1 font families for use with TeX.

I guess I don't know what the big deal is about fontinst.  All I do is 
(i) install the Type 1 font using ATM (Adobe Type Manager), (ii) Select
"Fonts > WriteTFM..." then pick the new font, (iii) make a note of the
file name used for the TFM.   Then refer to the TFM using \font in
plain TeX, or via a simple *.fd file in LaTeX 2e.  I make the *.fd file
simply by taking some existing file for another font family and
editing it to change the names...

Regards, Berthold.

Berthold K.P. Horn	mailto:bkph@ai.mit.edu  http://www.ai.mit.edu/people/bkph/bkph.html