-
Notifications
You must be signed in to change notification settings - Fork 188
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
Silent woff2_decompress failure? #151
Comments
Hm, maybe this is a clue: if I try to use the uncompressed font in a web page, Chrome complains:
If I try to use the woff2 file, Chrome echoes ots:
For completeness sake: ots does not complain about the uncomressed ttf outside of Chrome. |
I believe Chrome configures a smaller size limit for OTS than the default that you presumably get if you build it standalone; see khaledhosny/ots#244. |
Is this identical to https://bugs.chromium.org/p/chromium/issues/detail?id=1348101 ? |
(I have no access to that issue, so I wouldn't know) |
it reads like this:
|
It's definitely related. My main issue here is probably two things:
|
this: Lines 19 to 20 in 4721483
|
I'm having a very large font (that I cannot share publicly), that successfully compresses with woff2_compress:
If I decompress it with fonttools, the result is fine (identical except for the head table, the mod date differs probably).
But
woff2_decompress
doesn't produce any output, and no error message is shown. The exit code is 1, though.opentype-sanitizer is complaining about this file, too:
Perhaps it is the same issue, as it appears that ots uses
google/woff2
.If anyone would be willing to have a look, I'd gladly share the file privately. It's from the GS CJK project, in case you're familiar with that.
The text was updated successfully, but these errors were encountered: