| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Test consolidation
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
This ensures that we'll only have four fonts with family name
"Roboto" (regular, bold, italic, and bold italic), which is necessary
for Windows compatibility. Other styles have their weight appended to
the family name.
Also ensures that the macStyle bold bit is set for weight Black, to be
consistent with older Roboto binaries.
|
| |
|
|
|
|
|
|
| |
See added comment for motivation.
Probably the *.frac and *superior glyphs should be merged. More info:
https://github.com/google/roboto/issues/22
https://github.com/google/roboto/issues/108
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
| |
If components of components aren't also decomposed, we may miss some
contours in the resulting glyphs.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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).
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | | | |
|
