commit | ddc3d0a8c46a015f9cc8769f405f843d93d15fda | [log] [tgz] |
---|---|---|
author | Khaled Hosny <khaled@aliftype.com> | Tue Jan 12 17:00:14 2021 |
committer | Khaled Hosny <khaled@aliftype.com> | Tue Jan 12 17:00:14 2021 |
tree | 4c02dd096f3b0b679b9abbf8aef083b34cdcbd4f | |
parent | 3ada7470a9840c176c13a80ae1c35d22e5cd1d4d [diff] |
8.1.3
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.