> hard to test without those tfm files (i don't want to clobber my system 
> by generating them; also, i never use the p* variants)

I created the vf and tfm files with the attached script. Maybe you can 
setup a local directory? Creating these fonts simply needs the following 
calls (the files are generated in the current directory!):

fonts.sh <path-to-afm-dir> adobe helvetic ec
fonts.sh <path-to-afm-dir> adobe times ec
fonts.sh <path-to-afm-dir> adobe courier ec
fonts.sh <path-to-afm-dir> adobe helvetic texnansi texnansi
fonts.sh <path-to-afm-dir> adobe times texnansi texnansi
fonts.sh <path-to-afm-dir> adobe courier texnansi texnansi

The first three calls generate virtual fonts that are base on raw fonts 
with default encoding and the last three calls generate virtual fonts 
that are based on texnansi reencoded raw fonts.

(After studying texfont I think that generating fonts based on the 
default encoding of raw fonts is not possible with texfont.)

I think the generate vf and tfm files are correct because they can be 
used without problems as long as no family switching occurs.

Is there a specific reason why the p* variants should not be used? I 
hoped that they are very similar to what is present in the different 
Acrobat Reader versions.


> 
> looking at your map file:
> 
> there are no pfb files mentioned ... why?

I want to use the built in fonts because the size of the PDF documents 
must be as small as possible.

--Stefan