New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fontforge generate creates bad GPOS table in NotoNaskhArabic-Regular.ttf #4675
Comments
Please try again with the latest version and reopen if it's still an issue, those versions are ancient. |
I built the latest fontforge from source:
The issue is still occurring for me. The symptoms appear the same as the original post. |
The GPOS table is being written incorrectly by FontForge in this case.
|
I'm not sure if this is helpful in identifying the font as the culprit, but if I run sfddiff against just the base font it reports an error:
So maybe either the font is bad or fontforge is having issues reading this font, which then makes generating it impossible? |
The GPOS table is definitely valid in the original font. I'm certain this is a FontForge bug. |
Any chance this issue will get attention some time soon? |
Not from me, sorry. |
Environment:
I've tried running this from Ubuntu 16.04 (fontforge 20120731) and Ubuntu 18.04 (fontforge 20170924) with the same results.
What I am doing:
I would like to generate a font based on NotoNaskhArabic-Regular.ttf (here). I am using the following script:
Expectation:
A functionally identical font called "OutputFont.ff" is generated. If I run sfddiff against it, I would expect to see something like:
Issue:
The generated font seems to contain many different errors. I am not a font guy so I don't fully understand the errors that I'm seeing, but they seem to be numerous and severe. If I try sfddiff I get this:
If I try to open up the new font in the GUI application it also spends a long time "Fixing up References" and generates warnings that appear identical to the sfddiff output.
I'm not sure if this is an issue with fontforge or the Noto font. Other Noto fonts I have worked with in fontforge seem to be fine, including other Arabic fonts. I do not deeply understand the inner workings of how fonts work so I'm not sure what else to provide. It seems perfectly likely that the issue could be in the font and not in fontforge, but I'm not sure how to prove that.
The text was updated successfully, but these errors were encountered: