In this case I would start by opening a font that already works fine in that environment. Examine the font info and apply it back to your font.

Hope this helps!

That is something I did, it does not work. Can it be that the character naming for the Penta/Unix has a restricting? Use of periods in naming, or more than ten positions (e.g. acircumflex has 10 positions)?

Thanks

What kind of fonts are you actually making? OpenType fonts or old-school Unix PostScript Type 1 (.pfa) fonts or something else?

For OpenType fonts it should not matter when you use periods in glyphnames (as long as your OpenType features reference them). But PostScript Type 1 fonts don't support OpenType features *and* need to comply with certain encodings. Some time ago I had to generate Unix pfa fonts in Adobe Standard Encoding for use in Framemaker for instance.

The fonts are old-school Unix Postscript Type 1. The customer told me they need an .pfb font, so I generate in FontLab the FontFormat 'Win Type1' and also an suitcase with .afm included. Maybe the Adobe Standard Encoding can be a clue. Thanks for this!

You might want to check your settings for exporting the fonts as well:

Paul, thanks for all the help. It seems the reason why the font did not work on the Penta system was not in the font itself that I had generate but in the Penta-system. The font is being tested now.