New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

TTX: distinguish between fully-supported and hex tables #13

Open

n8willis opened this issue Nov 20, 2015 · 0 comments

Owner

n8willis commented Nov 20, 2015

The TTX format fully supports the

BASE, CBDT, CBLC, CFF, COLR, CPAL, DSIG, EBDT, EBLC, FFTM, GDEF,
GMAP, GPKG, GPOS, GSUB, JSTF, LTSH, MATH, META, OS/2, SING, SVG,
TSI0, TSI1, TSI2, TSI3, TSI5, TSIB, TSID, TSIJ, TSIP, TSIS, TSIV,
VDMX, VORG, avar, cmap, cvt, feat, fpgm, fvar, gasp, glyf, gvar,
hdmx, head, hhea, hmtx, kern, loca, ltag, maxp, meta, name, post,
prep, sbix, trak, vhea and vmtx

Tables. Other tables are dumped as hexadecimal data.

It might be helpful in the long run for fontfile-ttx-mode to treat these tables differently w.r.t. highlighting and linting.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment