Closed Pomax closed 7 years ago
That article is too long to follow, and I don’t know what to do with the above hex code to get a binary file. Please attach the actual binary file.
Don't read the entire article, it's mostly irrelevant to this bug. The initial comment had all the information needed already.
As for the hex code, you paste it in any hex editor and save it as otf file, or you can even just use echo
to write the sequence to file, but I'll try to attach the actual file for your convenience.
hopefully this worked. github is pretty stupid about which filetypes it accepts as attachment.
TTX, FontForge, Font Creator, Fontlab, etc. all read in this file just fine, and older versions of Firefox and the current version of Chrome load this file as a webfont without any complaint as well, so something in OTS became more aggressive to the point of rejecting fonts that the industry standard in practice says is perfectly fine.
Thanks. I have no problem with the attached file:
$ ./ots-sanitize small.otf
WARNING: maxp: Bad maxZones: 0
File sanitized successfully!
Hm, I wonder whether they did something weird in FF Nightly to break OTS, then. I'm trying this on 58 and the console is full of sanitization errors. I'll do some more investigation here, thanks.
A few years ago I wrote http://processingjs.nihongoresources.com/the_smallest_font/, on making the smallest possible font that is still accepted by all browsers. Since then, OTS has apparently been updated to reject this font, despite the fact that most modifications were made in spec-legal ways. The only truly spec-breaking modification was cropping the POST table, which should have zero effect on a font when used in the browser, so it would be interesting to see why OTS now treats this font as bad.
The font itself can trivially be generated with a hex editor by pasting the following hex code into a new otf file:
(it is a really tiny font =)