The message 'Neither pfa nor pfb found' is of little use given: C:\>set GS GS=gswin32 GSC=gswin32c GS_FONTPATH=C:\WINNT\FONTS C:\>pf2afm LINAFB Neither pfa nor pfb found C:\>pf2afm LINAFB__ Neither pfa nor pfb found C:\>pf2afm LinaresFigurine-Bold Neither pfa nor pfb found C:\>dir C:\WINNT\FONTS\LINAFB*.* Volume in drive C has no label. Volume Serial Number is A4BF-3E4A Directory of C:\WINNT\FONTS 09/10/1994 02:20p 29,040 LINAFB__.PFB 09/10/1994 02:20p 695 LINAFB__.PFM 06/17/2003 08:20p 38,440 LINAFB__.TTF 3 File(s) 68,175 bytes 0 Dir(s) 49,477,562,368 bytes free This is either an error in the program or the documentation or both...
The search is case-sensitive. So neither pfa nor pfb were found. This is indeed an annoyance to Windows users but for the time being you have to rename your files to the lower case.
Created attachment 3968 [details] patch Make pf2afm utility friendlier to Windows users: check for .pfa or .pfb extensions case-insensitively and accept backslash as a path separator.
The path is committed as a rev. 8674. pf2afm didn't change for about 3 years. The patch should be easy to apply to the released versions.