skef
skef
@punchcutter Wondering if this PR is still tracking something to be done.
The current `develop` branch of afdko has an unusual structure (given the non-standard way it adds C binaries to the path. We have a branch currently called `addfeatures` that we...
There are at least two causes of this. One is a bad pruning calculation that wasn't using `abs()` as it should have, that's easily fixed. The other is trickier, and...
This should be a simple matter of plumbing now -- deciding on what arguments to use to retrieve the GlyphReport object.
Once we switch to the VF-first/addfeatures workflow, we'll need to build "blank" or "shapeless" CFF2 fonts that we then add shaping to. I want to do this in two development...
I don't see us just _removing_ this part of the spec. Documenting the ordering requirement could be valuable, although there are a lot of things like this in the older...
As you're probably realizing this has a lot of formatting related problems (flake8), some of which are due to edits for line length that you've removed.
I think I would prefer a submission with the _substantive_ changes and then (perhaps) a different submission with the large amount of _stylistic_ changes. Or perhaps just skip the latter?...
@josh-hadley Merging this would presumably require additional `pytype` github checks, so that notations like `# pytype: disable=attribute-error` won't just rot.
One reason we ported `psautohint` to python was the hope that it could be modified by the broader community, in comparison to the C code which was only ever worked...