🚀 go-pugleaf

In article <1jrgc9INNoo7@life.ai.mit.edu>, bkph@wheat-chex.ai.mit.edu (Berthold K.P. Horn) writes:
 
> In article <1jpel3INN2mn@elroy.jpl.nasa.gov> dundas@chip.Jpl.Nasa.Gov (John Dundas) writes:
 
>    I have the Adobe Lucida Math fonts and their .pl files but have not been
>    able to get all of the math characters to print properly (I am using
>    pltotf and dvips V5.495).  Can anyone offer any pointers?
 
> You need to note that Adobe doesn't believe in the `control character'
> positions, so all of the characters you'd expect to be in in the 0 -- 31
> range appear instead in the 161 -- 195 range.  They also like a space in
> position 32. One way to fix this is to reencode the font.  That is, change
> the assignments in the Encoding vector to correspond to those in Computer
> Modern math fonts.
 
> How to do this is a function of what platform you are on - something you
> don't mention.  On Unix, with PFA files you can edit the file directly,
> since it is plain ASCII.  You need to change the AFM file also if you are on
> NeXT using Display PostScript. 
 
> On the PC you have to convert the compact binary PFB file to PFA form, edit,
> and convert back to PFB (using PFBtoPFA and PFAtoPFB say - or just use
> REENCODE directly).  If you are using the font in MS Windows, you'll have to
> make up a new PFM metric file (using AFMtoPFM say).

If you're using dvips (which by my guess is fairly likely), you
can do  the remapping via VF files. I have some vague
recollection that Karl Berry and someone else from England whose
name I don't remember (terribly sorry) have done the work of
getting the Adobe Lucida fonts working under TeX. I'm sure
they'll post some more on the topic.

Reencode the fonts... hmmph!

-dh

Don Hosek                  
dhosek@ymir.claremont.edu  
Quixote Digital Typography 
714-621-1291