tag | 2890649d8212838b98802868b6ccddfa855d14e2 | |
---|---|---|
tagger | Khaled Hosny <khaled@aliftype.com> | Sun Jan 02 21:59:18 2022 |
object | 2369c7c00de9e729c79d13e41e2c3601ed2f6c69 |
Version 8.2.1 - Fix a couple of uncaught out of bounds exceptions in CFF2 code.
commit | 2369c7c00de9e729c79d13e41e2c3601ed2f6c69 | [log] [tgz] |
---|---|---|
author | Khaled Hosny <khaled@aliftype.com> | Sun Jan 02 21:57:43 2022 |
committer | Khaled Hosny <khaled@aliftype.com> | Sun Jan 02 21:57:43 2022 |
tree | 16bb9bcbfeb56c5f1ef93d1b92f51e65da492765 | |
parent | 635fa6b97af975620510755de8322a395ad3e4cf [diff] |
8.2.1
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.