On importing font in font creator 14, it may breaks the kerning tables.
For reference files has been attached.
[FIXED] Destructing font in new font creator
-
- Posts: 33
- Joined: Wed Apr 07, 2021 6:50 am
[FIXED] Destructing font in new font creator
- Attachments
-
- Nastaliq Lahore.ttf
- (178.46 KiB) Downloaded 214 times
-
- Nastaliq Lahore (Project_FontCreator14).fcp
- (209.19 KiB) Downloaded 213 times
-
- Nastaleeq Lahore.jpg (2.03 MiB) Viewed 2026 times
-
- Moderator
- Posts: 11160
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: Destructing font in new font creator
The font contains several Chained Contexts Substitution lookups (ChainingContext40-ChainingContext47) that replace a space for another glyph. Then single adjustment is applied to that glyph. See the two screenshots below.
For some unknown reason those lookups are not applied by other shaping engines. It would be great to know why they ignore them. Within the original font all lookups are extensions, which is awkward and needless. Maybe there is a limit (50!) on the number of such extension lookups? You could try to post an issue at harfbuzz or post at typedrawers...
For some unknown reason those lookups are not applied by other shaping engines. It would be great to know why they ignore them. Within the original font all lookups are extensions, which is awkward and needless. Maybe there is a limit (50!) on the number of such extension lookups? You could try to post an issue at harfbuzz or post at typedrawers...
-
- Moderator
- Posts: 11160
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: Destructing font in new font creator
I have exported the font with all lookups as extensions, and it also fails, so it is most likely not related to the extensions.
-
- Moderator
- Posts: 11160
- Joined: Fri Oct 04, 2002 12:41 am
- Location: Bilthoven, The Netherlands
- Contact:
Re: Destructing font in new font creator
After some more digging I located the cause of the problem. The font contains chained contexts substitution lookups with empty classes. We ignored the empty classes, but we should actually skip such lookup rules. The problem is solved with the update we just released!
Thank you for reporting these rare but nasty issues, as it makes our software more robust.
Thank you for reporting these rare but nasty issues, as it makes our software more robust.