-
Notifications
You must be signed in to change notification settings - Fork 104
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
With ufo2ft==2.29.0 I can't access ttf.reader on an object returned by compileTTF #3940
Comments
to workaround issue fonttools#3940
That's a feature, not a bug ;) In the ufo2ft postProcessor were previously always compiling the ttfont to an in-memory bytesIO buffer and reloading it off that, but that was only necessary when renaming glyphs so we don't do that any more unconditionally. The TTFont instance you get from ufo2ft is created from scratch not read from disk so you should not expect it to have a reader attribute, that's only for TTFonts read from a file. |
If you require that your test font has a reader, you need to do what we were doing in ufo2ft, that is save it to a temporary BytesIO and open a new TTFont from that, which will then be as if it were read from a file (only that the file is an in memory stream) |
Thanks! I will try that. |
Starting from ufo2ft 2.29.0, the TTFont instance produced by ufo2ft may not have a .reader attribute. Fixes fonttools#3940.
Starting from ufo2ft 2.29.0, the TTFont instance produced by ufo2ft may not have a .reader attribute. Fixes #3940.
The text was updated successfully, but these errors were encountered: