| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
I'm not sure why we weren't doing this before, or why there is even a
check to prevent adding top or bottom anchors to glyphs without
unicode values. But this change seems appropriate, particularly since
it fixes #69
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is necessary because of some implementation details in RoboFab;
RAnchor objects always evaluate to False in a boolean context.
Fixes a bug in which "top" anchors were not being added to composite
glyphs, since they are added only when the "parenttop" anchor is
present (which was checked for with a statement like "if anchor:").
|
|\ \
| | |
| | | |
Correct metadata related to font names and weights.
|
| | |
| | |
| | |
| | | |
Without this, ufo2fdk sets both Light and Regular to 400 by default.
|
| | |
| | |
| | |
| | |
| | | |
This propagates to name ID 6 in the name table, and font name info in the
CFF table.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This uncomments some code which distinguishes between Regular/Bold and other
weights when setting the UFOs' styleMapFamilyName attribute, which is used by
the FDK to set the output OTFs' family names (this association is documented
here: http://unifiedfontobject.org/versions/ufo2/fontinfo.html). It's not clear
why this code was commented out in the first place.
Part of #37
|
| | |
| | |
| | |
| | |
| | | |
Basically a redo of 9292364c1a122498ada2616fdd20683c27c80e15, except more
conservative.
|
| | |
| | |
| | |
| | |
| | | |
This reverts commit 9292364c1a122498ada2616fdd20683c27c80e15. Necessary
because it caused condensed glyphs to italicize incorrectly.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Updated glyphs require more kerning subtable breaks to avoid crashing
makeotf. The subtable sizes are still decided somewhat arbitrarily based on
trial-and-error.
|
| | | |
|
|\ \ \
| | |/
| |/| |
|
| | | |
|
| |/
|/|
| |
| |
| |
| | |
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....
|
| |
| |
| |
| | |
These are now fixed in the fonts themselves.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The change is temporary, while we confirm the quality of our new
build toolchain. The target should go away once we switch completely
to the new toolchain.
This also removes the code that removed tab and unassigned characters
from the Android target, since the tab now has the same width as
space and the unassigned characters are no longer in the fonts.
|
| |
| |
| |
| | |
This caused some glyph mixes to fail.
|
| |
| |
| |
| | |
This affects the creation of condensed masters, without it they had no kerning info.
|
| |
| |
| |
| | |
This was causing problems with Thin Italic font generation.
|
|\ \
| | |
| | | |
Fix bug causing inaccurate anchor coordinates.
|
| | |
| | |
| | |
| | | |
This has now been fixed upstream.
|
| | |
| | |
| | |
| | | |
Ideally we could call RGlyph.move(offset, anchors=False), but we have to bring back "shiftGlyphMembers" from the original toolchain because RGlyph.move does not work as documented.
|
| | | |
|
| | |
| | |
| | |
| | | |
These issues are solved with the updated anchor resources.
|
| | |
| | |
| | |
| | | |
This is necessary for correctly adding anchors in the immediately following code.
|
| | |
| | |
| | |
| | | |
I introduced this bug in aa285dc861fb8a5b5083e1de3bb00ea1ef658cb1 while adapting updated scripts from Paratype.
|
|\ \ \
| |/ /
|/| | |
Remove feaTools adaptions which are now upstream.
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| | |
The new tests check that every glyph fits in the [yMin, yMax] range.
Also switch run_general_tests.py to test the hinted fonts instead of
the unhinted fonts.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Fix for dropped anchors
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
With anchors fixed, we shouldn't need this check. Rollback of 55519e636b119dcdd91319364c572d3550050a43.
|
| | |
| | |
| | |
| | | |
This is a temporary workaround until VFB to UFO conversion is fixed.
|
| | |
| | |
| | |
| | | |
This should avoid segmentation faults from makeotf even as we add more kerning rules. Necessary for the upcoming missing-anchor fix.
|
|\ \ \
| | | |
| | | |
| | | | |
Add tests and requirements for the 'smcp' feature.
|
| | | | |
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | | |
Add tests for s-t and longs-t discretionary ligatures.
|
| | | | |
|
| | | | |
|