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
Reencode() silently mis-encodes type1 fonts with Unused/detached glyphs #3080
Comments
|
I tried |
This was referenced Jun 7, 2017
|
The problem was first noted on the CJK mailing list. |
This was referenced Jun 9, 2017
|
It would be nice if |
This was referenced Jun 9, 2017
|
The fixed up freetype-py script is up at |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Important
Mark with [x] to select. Leave as [ ] to unselect.
When reporting a bug/issue:
Based on source from git with hash: b8e5ff8, fedora linux, x86_64
For example, for subfont 44, this is what ttf2tfm gives:
This is what fontforge does (it is really glyph id rather than uniXXXX) - whenever fontforge seems to be randomly uses /uni44*, it encodes the wrong glyph. The glyph ids should be uni1AD1, etc. So half of subfont 44 is wrong, in my case.
When you open an issue for a change/improvement/feature request:
The text was updated successfully, but these errors were encountered: