OS X: Segfault adding ligature
Ambarish Sridharanarayanan <[email protected]>
| Newsgroups | gmane.comp.fonts.fontforge.devel |
|---|---|
| Message-ID | <ef022076d25143cf8ccbcd8f61762f8f@BY2PR02MB186.namprd02.prod.outlook.com> |
I’m running fontforge 20131122, libfontforge 20131122-ML on OS X Mavericks. I’m trying to add a ligature to an Indic font for the Grantha script. The target of any ligature I add (through Glyph Info) ends up being a .notdef in the table, If I then go to Font Info, Lookups, go into the sub-table, Edit Data and try to fix the Ligature Glyph Name, FontForge crashes when I hit ‘OK’, with a Segmentation Fault, with the following output: MakeTemporaryFile() fd:28 template:/var/folders/_j/jr2f9sf110l_ylyy7mchm95h0000gp/T//fontforge-stemp-H83T9W Failed to read a file. Bytes read:0 file size:0 /Applications/FontForge.app/Contents/MacOS/FontForge: line 64: 699 Segmentation fault: 11 $WRAPPER $bundle_bin/fontforge -new "$@" Here are repro steps: * Download file from the link below (you may need a modern browser + JS) http://sdrv.ms/1fwqunc * Go to Element → Font Info * Go to Lookups * Open the <1, 0> Required Ligatures table * Select the only sub-table and click Edit Data * Notice the 2 ligatures are both .notdef * Try to fix up the Ligature glyph-names by editing the first notdef, typing in ‘uniE00C’ * Click OK * CRASH! Thanks for any help! Ambarish ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Fontforge-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fontforge-devel