tag | b1651550666a59fa92feeb36c348c4cf28f4f715 | |
---|---|---|
tagger | Khaled Hosny <khaled@aliftype.com> | Wed Dec 02 12:45:09 2020 |
object | d6d783c67b4aa604edd12dce0decc18a5c79906b |
Version 8.1.1 * Fix use of uninitialized value that results from upgrading STAT table version. * Fix varous typos. * Add manpage for ots-sanitize.
commit | d6d783c67b4aa604edd12dce0decc18a5c79906b | [log] [tgz] |
---|---|---|
author | Khaled Hosny <khaled@aliftype.com> | Wed Dec 02 12:44:03 2020 |
committer | Khaled Hosny <khaled@aliftype.com> | Wed Dec 02 12:44:03 2020 |
tree | 308fa1ab04026bdf0cfb7414797e209ba3ad9e86 | |
parent | 6c352b031bb68e5d116ca04952d00f3e53f13abc [diff] |
8.1.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.