Basic OT errors ...

Eric_West's picture

Hello,

I'm trying to build some basic OT code just for the 'fi' 'fl' combo's to start with. I'm following the user manual. The attached pic is giving me errors, I tried diff combinations with ' l i by li' 'li by l i ' 'l_i by li' etc. But when I compile it errors out saying

' aborting because of errors...

Any ideas.

Thanks

k.l.'s picture

Hello. Glyphs are identified by their glyphname in feature code. If your ligature is called f_l (bottom of your image), this is the name to be put after the "by", so: "sub f l by f_l;"

But I am surprised about aborting because of errors. Normally FL would just say: glyphs don't exist, shall I create them ... Do you have other features already defined in the leftside column but without content yet?

Karsten

Eric_West's picture

Thanks Karsten.
Here's my OT panel. That's the only thing I've got (attempted) in OT.

.'s picture

Eric, you should probably use the "standard" names of "fi" and "fl" for those two glyphs: they have Unicode indices and places in the Mac Roman codepage.

I wonder why the compile isn't working for you. That's the simplest feature in the universe!

If you're still having problems, you can email the file to me and I'll troubleshoot it for you. (I'd hate for your avatar to come true.)

twardoch's picture

Actually, for these ligatures, both the "fi", "fl" and the "f_i", "f_l" names are equally permissible.

A.

k.l.'s picture

Strange, everything looks right! Maybe Chester finds something in the font.

.00's picture

""

I'd check the name, and the settings in your Generate OpenType preferences.

twardoch's picture

Of course, needless to mention that in such situations I recommend contacting Fontlab Ltd. at http://www.fontlab.com/problem/

Regards,
Adam Twardoch
Fontlab Ltd.

.'s picture

Adam, if there is nothing wrong with the way the OT is written, I'll let you guys know. c

.'s picture

Update: I renamed the Unicode-supported ligatures, as well as some of the "spare parts" glyphs in the VFB. I cleared the Unicode, and then generated Unicode with PUA for the non-Unicode glyphs. I rewrote the liga feature to reflect these changes, and the feature compiled successfully.

Case closed!

Eric_West's picture

Thanks all!

Eric_West's picture

Chester,

Or anyone else, now why all the sudden i hang and freeze when trying to generate OT? All I did was go back and clean it up with font audit.

THX

Nick Shinn's picture

There is also a BCP situation I've encountered which prevented OT font generation, when two BCPs are at the same position (indicated by an "open" point image).

Eric_West's picture

Thanks Nick, I went back through and cleaned it up some more.Seemed to do the trick.

Eric_West's picture

And again,

Any reason my apostrophe would be showing up in Ill CS and not InDesign CS ?

Thanks

Syndicate content Syndicate content