tag | ac49b89bc25a5c3e830a1e81206eee35008765af | |
---|---|---|
tagger | Khaled Hosny <khaled@aliftype.com> | Sun Mar 07 06:25:47 2021 |
object | a6533c4f6a7cb777153c78b78295e42f185ccd3d |
8.1.4 - Speedup decompressing compressed Graphite tables. - Improve message about out-of-order MVAR tags.
commit | a6533c4f6a7cb777153c78b78295e42f185ccd3d | [log] [tgz] |
---|---|---|
author | Khaled Hosny <khaled@aliftype.com> | Sun Mar 07 06:25:36 2021 |
committer | Khaled Hosny <khaled@aliftype.com> | Sun Mar 07 06:25:36 2021 |
tree | 9e5b3516944705d2080c2ccf8f10610ee3e53e10 | |
parent | 6e9a697bd9a76475d2d947fb1a371e8f7a6edb32 [diff] |
8.1.4
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.