googlefonts / googlefonts/gftools

Are we exporting OTF-CFF from sources converted to TTF?

Open
#770 3 comments 0 reactions 0 assignees View on GitHub
bug builder enhancement
Dominant language
Python
Stars
283
Forks
73
Avg merge
21h 25m
Merged PRs (30d)
8

Description

For the Intel Mono project we noticed gftools builder was turning the sources to TTF masters before exporting OTF-CFF binaries, instead of exporting directly from the sources that have postscript contours —ending up in otf-cff files with `gasp` and `prep` tables. This seems to be a Builder issue since exporting directly with Fontmake is okay.

Also reported by designers but that may be a Fontmake issue (not builder):
- StemSnapH parameter is missing from CFF
- in the CFF table, it looks like any slashes have gone missing, which garbles the URL in the copyright notice. Not sure how relevant this is, the name table is OK
- PANOSE information is missing from OS/2 table

ref: https://github.com/RosaWagner/intel-one-mono/tree/googlefonts

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.