| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |\
| |
| | |
Add family name tests
|
| | |
| |
| |
| |
| |
| | |
Not sure if there's any rule for whether fonts heavier than Bold (e.g.
Black) should be marked bold in the macStyle and subfamily name, so
this adds an option to test either way.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Check removed in ca851298519eb19c3c89cc2b3a6c0770b04257a4.
It may or may not be standard practice, but Roboto has previously set
the bold bit for its Black weight so we'll keep it this way to avoid
regression.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Changes to the TestNames unit tests reflect the issues raised in the
link added to common_tests.py. Also generally account for code changed
in nototools.
|
| |/ |
|
| |\
| |
| | |
Decompose nested components.
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
If components of components aren't also decomposed, we may miss some
contours in the resulting glyphs.
|
| |
|
|
|
|
|
| |
This seems to have been obviously incorrect, looking at the
inconsistency with other Ncommaaccent formulas (commaaccent should
always go below the N). And sure enough, the accent was not being
added to the composite glyph.
|
| |\
| |
| | |
Fix up *num features
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A few things happening here:
- References to *.lnum glyphs changed to *.pnum (reflecting the
renames in the last commit).
- Feature definitions expanded to handle feature combinations,
not-working definitions removed from the resource directory.
- Glyph classes added to make feature definitions clearer.
- VFBs updated via vfb2ufo, based on updates to UFOs.
|
| |/
|
|
| |
These are proportional numbers, not lining numbers.
|
| |\
| |
| | |
Don't use RGlyph.getParent.
|
| |/
|
|
|
|
| |
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.
|
| |\
| |
| | |
Add test to compare glyph areas between weights
|
| | |
| |
| |
| |
| |
| | |
For now, we just check which glyphs are unchanged between the Thin and
Bold masters, and make sure only those glyphs are unchanged between
Thin, Regular, and Bold output (ignoring empty glyphs).
|
| |/ |
|
| |\
| |
| | |
Always deal with floats when mixing font masters.
|
| |/
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| | |
Delivery updates
|
| | | |
|
| | |
| |
| |
| | |
Note that these binaries are also missing mark/mkmk features.
|
| | | |
|
| | | |
|
| | | |
|
| |/| |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
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:").
|
| |\ \
| | |
| | | |
Delivery updates
|
| | | | |
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | | |
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
|
| |\ \ \
| | | |
| | | | |
Contour fix
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Basically a redo of 9292364c1a122498ada2616fdd20683c27c80e15, except more
conservative.
|
| |/ / /
| | |
| | |
| | |
| | | |
This reverts commit 9292364c1a122498ada2616fdd20683c27c80e15. Necessary
because it caused condensed glyphs to italicize incorrectly.
|
| |\ \ \
| | | |
| | | | |
Delivery updates
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Updated glyphs require more kerning subtable breaks to avoid crashing
makeotf. The subtable sizes are still decided somewhat arbitrarily based on
trial-and-error.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |\ \ \
| | | |/
| | |/| |
|
