There used to be a command line tool call ttf2pt1 I think, based on freetype, for converting truetype to type 1 .
I assume fontforge and many other tools car do the conversion via a GUI too. It was quite routine in the early days of TeX/LaTeX which used to support type 1 only, and still prefer it now, I think.
I already answered on the Glyphs forum. There is a .pfb file in the Temp folder from the OT export. Just rename the file to whatever you like. And you need to produce an .afm file. but that should be easy.
If you need to generate Mac PostScript fonts with suitcases then FontLab or Fontographer are probably (still) the best choice. Also for Windows pfb fonts I would only use a font editor where I can define all the settings myself (encoding, unique ID, etc). Too much that can go wrong...
On the Mac side, you need one outline font file per font, plus a matching font suitcase with at least one bitmap font in it. One suitcase can support multiple outline fonts, however.
Comments
I assume fontforge and many other tools car do the conversion via a GUI too. It was quite routine in the early days of TeX/LaTeX which used to support type 1 only, and still prefer it now, I think.
There is a .pfb file in the Temp folder from the OT export. Just rename the file to whatever you like. And you need to produce an .afm file. but that should be easy.
If you need to generate Mac PostScript fonts with suitcases then FontLab or Fontographer are probably (still) the best choice. Also for Windows pfb fonts I would only use a font editor where I can define all the settings myself (encoding, unique ID, etc). Too much that can go wrong...
You can create a .pfm from a .afm and an .inf. In this case you can use the afm2pfm tool to make the PFM: http://www.proximasoftware.com/downloads/
On the Mac side, you need one outline font file per font, plus a matching font suitcase with at least one bitmap font in it. One suitcase can support multiple outline fonts, however.
Wow. That brings back memories.