| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| | |
Fontcrunch update
|
| | |
| |
| |
| |
| | |
I feel like we may as well have these flags, since it compiles fine
with them.
|
| |/
|
|
|
|
| |
These are changes from https://github.com/googlefonts/fontcrunch. Not
included is the removal of the main function in quadopt.cc, which we
obviously need.
|
| |\
| |
| | |
Italics stuff
|
| | |
| |
| |
| | |
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.
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
These dates seem to be incorrectly exported by vfb2ufo. The new dates
are taken from the currently available webfont binaries.
|
| |\
| |
| | |
[README.md] modify instructions for installing booleanOperations
|
| |/
|
|
|
|
|
| |
The current master/HEAD no longer requires to run two different setup.py
scripts and manually copy the *.so module.
https://github.com/typemytype/booleanOperations/pull/6
|
| |\
| |
| | |
Use common tests from nototools
|
| | | |
|
| |\|
| |
| | |
Further generalize common_tests.py
|
| | | |
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Test consolidation
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Provide a hotfix for webfont names
|
| |/
|
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| | |
Temporarily disable superscript digit test for web
|
| |/
|
|
|
|
|
|
| |
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
|
| |\
| |
| | |
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
|
