mpost problems

[Larry Smith]

Dear Ladies and Gentlemen,

I am writting to discover what I am doing wrong with my
texmf installation. I am a user on the Yale Math Department
unix system. I use my own versions (i.e., formats) oTeX and
friends. To do so on a unix box I have installed a texmf tree
as suggested in your documantation, and all the usual TeX tools
seem to function properly except the mpost friends needed to make
an mpx file. The problem is the isnsitance of the sequence
of program calls
mpto -tex junk > trash
mytex \&mymem trash
dvitompx trash.dvi junk.mpx
The result is that for the fonts declared in the .mp source
and the TeX format to be
pncr
become in the .mpx file
pncr8r
The same source compiled on a windows free dos box uses the
correct file name of pncr, and leads to no troubles. On the unix
box, as you can imagine, the dvips program stumbles over all the
unknown fonts and produces chaos.

I am supposing that either some font names have been compiled into the
distribution of MetaPost, or that MetaPost is reading the psfonts.map
file from somewheres else other than my own texmf tree, or doing so, but
in the wrong order.

Any ideas?

If indeed there is support out there in tug land I can send you some
sample source: for the moment my workaround is to lie to dvips and tell
it that pncr8r is the same as pncr in the psfonts.map file. This may
produce chaos down the line since some of the font names I used other
than pncr also get the same 8r attached to them, and they are definitely
NOT 8r encoded.

Sincerely,

Larry Smith