| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
| |
The copyright message now found in the source files is correct.
|
|
|
|
|
| |
Due to changes in
https://github.com/jamesgk/ufo2ft/commit/6c46f7050bfdd346c33c1312f07830c48fcc07f2
|
|
|
|
|
|
| |
This was changed to test hinted fonts in
a4ef18e29638cd1a0c814adb762177a342898eeb, but I think we want to go
back to unhinted fonts by default. It can always be changed locally.
|
| |
|
|
|
|
|
| |
There's no reason not to have these, and they're quite helpful for
catching little issues.
|
|
|
|
|
|
| |
There's no documented reason why we were doing this before, so let's
output these fonts for now and see if they work on other platforms.
Android can come next.
|
|
|
|
|
|
| |
Due to changes in
https://github.com/jamesgk/nototools/commit/7c07e2b2485b29638d9141b809d7eadd547f1b01
https://github.com/jamesgk/nototools/commit/995fe3c706d1e9fb76d5506e36a6ef06f2ea2dfe
|
|
|
|
|
| |
This is hopefully the last time we have to do this. In response to
https://github.com/googlei18n/cu2qu/commit/56f36a1b2ab673c25ac81756d5c251909a7d41e2
|
|
|
|
|
| |
cu2qu is a new library without a currently well-defined API, so these
calls have changed and will probably change again.
|
|
|
|
|
| |
The UFOs store contours in ccw order, and the TrueType spec seems to
say they should be cw. The old binaries are cw.
|
|
|
|
|
|
| |
This is a small change which passes the threshold at which dots will
have eight points instead of four, which makes a noticeable difference
in shape.
|
| |
|
| |
|
| |
|
|
|
|
| |
It's not much, but maybe a start....
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is (hopefully) a temporary hack until a more robust solution to
the issue is found.
Basically the problem is that RoboFab pens do float-to-float
comparisons to decide whether to remove duplicate points from
contours, and breaks with BooleanOperations output (which can include
point coordinates with very small fractional components). The
italicizing code assumes certain behavior from RoboFab pens and can't
handle duplicate points being kept.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
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.
|