Hi everyone,
I’ve been working on a design and have run into a problem which I’ve been unable to remedy. I’m hoping that someone might have some suggestions on how to go about tracking down the source of this problem since I am at a lost. I realise it’s a bit of a longshot, but perhaps someone has encountered a similar problem in the past and this rings some bells.
I’m using FontLab Studio 5.0.4/MacOS 10.5.2
When I generate my font as a Postscript-flavoured OpenType font, I get no error messages, but when attempting to install the font in FontExplorer X, I get a message that the font is corrupt (this message is an OS-level message, not a font-explorer message). Sometimes it will instantly deactivate, other times it will not. In the latter case, the font will show up in the font menu, but when I attempt to use it certain glyphs will be missing (that is they appear blank; they do not show up as the .notdef character). This includes several of the base glyphs (i.e. ones with unicode values) and all alternate glyphs (ones without unicode values which should be appearing when various OT features are active). Nothing appears to be wrong with any of these glyphs in the FontLab file.
If I generate the font as a TrueType-flavoured font, everything works fine.
I have attempted to copy all of the glyphs into a new .vfb file, but get the same results.
If I open generated .otf font in FontLab and regenerate it, then I get a font which does not report errors when installed and which does not exhibit any of the problems outlined above. However, if one embeds this font in a .pdf file, the .pdf file will be replete with .notdef symbols, incorrect glyphs, etc. so obviously something is still wrong.
I realise that debugging someone else’s font based only on the above is probably a tall order, but on the off chance that it suggests some known issue I thought I’d ask.
I don’t want to generate the font as a .ttf file since that would basically require that I redo all of the hinting in the font.
Any suggestions appreciated,
André
