More FontLab voodoo...
I shall pass over in silence my continuing gripe that FontLab is stuck expecting a 2,048 em unit when I open a glyph window, as well as the fact that, more often than not, the Preview Panel refuses to display the names of OpenType features, much less offer a preview of same.
Now, I have encountered a different problem. I just made a font based on an old MacKellar, Smiths and Jordan banner typeface which includes the banner image as a component element of all alphabetic character, along with component diacritics on the accented characters. When I generated font files, the TrueType version was flawless; the CFF version, on the other hand, dropped both the banner and the diacritics on over a dozen accented characters.
I managed to solve the problem by decomposing ALL of the characters and regenerating the CFF version. What is odd, though, is that the new file is exactly the same size as the defective file it replaced. WTF?
13.Mar.2010 4.58pm
Composite characters are not allowed in CFF fonts. "CFF" stands for "Compact Font Format" because it uses compression algorithms to collapse redundant data. Composites do essentially the same thing. So is probably why the font is no bigger after conversion. (This is my understanding, anyway.)
BTW, for OT features to show up in the Preview panel, you need to compile them first.
13.Mar.2010 7.48pm
Well, composite characters are "sort of" allowed in CFF. It's a deprecated feature, which should be avoided. By default, FontLab Studio decomposes all glyphs in OpenType PS fonts, there's a preference setting for that. Perhaps you accidentally disabled it.
13.Mar.2010 8.11pm
Maybe "sort of" but I've run into problems when I've left them in.
14.Mar.2010 10.19am
BTW, for OT features to show up in the Preview panel, you need to compile them first.
Standard Operating Procedure: it still remains a matter of "sometimes it works, sometimes it don't." Mostly, it don't...
14.Mar.2010 10.44am
Hm. I've never run into that particular bug. Maybe a FontLab on Windows thing?