Opentype Fontlab Standard ligatures problem

kingofcapearcona's picture

Hi together,

I have a problem. I build a typeface and generate it as Opentype (Postscript) on MacOSX with fontlab 4.6.
the problem is, that the standard ligatures (fi, fl) doesnt apear in InDesignCS. I checked everything, export options, UNICODE, indesign, etc. i have no problem with other fonts generated with fontlab, they (the standard ligatures) all work. but not in that font.
the strange thing is, if i make a new font and copy all letters from the problem font to the new font and generate it again as opentype i got the same problem, that the fi and fl ligatures are not used by indesign (or textedit) under osx. so, my theory is that there is something in the font itself that surpress the use of ligatures in such programs.

has anyone an idea where the problem could be?

again, I do not changed the unicode or added new ligatures into fontlab. i just used the 2 standard ligatures in fontlab (fi, fl).


chronicle's picture

You'll have to script the changes yourself, using the OpenType panel in FontLab.

Theunis de Jong's picture

Better late than never?

I'm pretty positive ID uses 'fi' and 'fl' named characters automatically as ligatures, OpenType font or not. Well, perhaps it did not in ID 2.0 (or what was it, back 'den?)

Roger S. Nelsson's picture

I'm sure InDesign (and Quark) use the fi and fl ligatures automatically if they are included in POSTSCRIPT TYPE 1 fonts.
But in OpenType fonts I guess you HAVE TO define the liga feature and include the ligatures there.
FontLab does this automatically when importing Postscript Type 1 fonts as default - which may be the reason some of your fonts have this feature, but a font you've made all by yourself from scratch doesn't have it.
Copying the glyphs from one font to another does not copy the OpenType features, so that explains why this doesn't work...
So make sure you make the liga feature before you export your OpenType font.

Roger S. Nelsson's picture

Just discovered how old the initial post was... D'oh!
Oh, well... :*)

Syndicate content Syndicate content