tag | c90446bdaf2527e08a2dfd583b77be7cb0df088e | |
---|---|---|
tagger | Khaled Hosny <khaled@aliftype.com> | Sun Dec 20 14:07:53 2020 |
object | 5afd9e2b8abdd03ffeddb22e6094b4fb546cb39d |
Version 8.1.2 * Sanitize maxPoints, maxComponentPoints, and maxComponentDepth from the maxp table. * Increase limits for decompressed tables and files from 30MB for both, to 150MB and 300MB, respectively. * Improve warning and error messages in hhea/vhea tables.
commit | 5afd9e2b8abdd03ffeddb22e6094b4fb546cb39d | [log] [tgz] |
---|---|---|
author | Khaled Hosny <khaled@aliftype.com> | Sun Dec 20 14:07:38 2020 |
committer | Khaled Hosny <khaled@aliftype.com> | Sun Dec 20 14:07:38 2020 |
tree | 45f7402c74c0a3f5fc643daa78bd600ecab2d724 | |
parent | 318e75ad918bbc527021e9ebb81818ff00e9e9f0 [diff] |
8.1.2
The OpenType Sanitizer (OTS) parses and serializes OpenType files (OTF, TTF) and WOFF and WOFF2 font files, validating them and sanitizing them as it goes.
The C library is integrated into Chromium and Firefox, and also simple command line tools to check files offline in a Terminal.
The CSS font-face property is great for web typography. Having to use images in order to get the correct typeface is a great sadness; one should be able to use vectors.
However, on many platforms the system-level TrueType font renderers have never been part of the attack surface before, and putting them on the front line is a scary proposition... Especially on platforms like Windows, where it's a closed-source blob running with high privilege.
Instructions below are for building standalone OTS utilities, if you want to use OTS as a library then the recommended way is to copy the source code and integrate it into your existing build system. Our build system does not build a shared library intentionally.
Build OTS:
$ meson build $ ninja -C build
Run the tests (if you wish):
$ ninja -C build test
See docs
Thanks to Alex Russell for the original idea.