| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
Apparently this method returns a different font than we expect in
decomposeGlyph, probably due to the glyph copying we do when mixing
masters. The easiest thing to do is just not trust or use the method.
|
| |
|
|
|
|
|
|
|
| |
Without this change, some of the master data contains int values
which are not interpolated correctly due to numpy array behavior.
For example adding float values to a numpy array of ints will
always result in an array of ints, so a scale value which should be
a float between 0 and 1 might instead be rounded.
|
| |
|
|
|
| |
Basically a redo of 9292364c1a122498ada2616fdd20683c27c80e15, except more
conservative.
|
| |
|
|
|
| |
This reverts commit 9292364c1a122498ada2616fdd20683c27c80e15. Necessary
because it caused condensed glyphs to italicize incorrectly.
|
| |
|
|
|
|
| |
Doing this conversion visibly changes the appearance of some composite glyphs,
since e.g. a component scale of 1.6 would be rounded to 2. What doesn't make
sense is why this was working with FontLab....
|
| |
|
|
| |
This caused some glyph mixes to fail.
|
| |
|
|
| |
This affects the creation of condensed masters, without it they had no kerning info.
|
| |
|
|
| |
These issues are solved with the updated anchor resources.
|
| | |
|
| | |
|
| |
|
|
| |
This is a temporary workaround until VFB to UFO conversion is fixed.
|
| |
|
|
| |
This matches the behavior of the old toolchain. The result should only contain kern rules for pairs present in both masters.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
