summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Fix up *num features.James Godfrey-Kittle2015-09-04
| | | | | | | | | | 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.
* Rename *.lnum files to .pnum.James Godfrey-Kittle2015-09-04
| | | | These are proportional numbers, not lining numbers.
* Merge pull request #105 from jamesgk/shape-fixJames Godfrey-Kittle2015-09-02
|\ | | | | Don't use RGlyph.getParent.
| * Don't use RGlyph.getParent.James Godfrey-Kittle2015-09-02
|/ | | | | | 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.
* Merge pull request #103 from jamesgk/add-testsJames Godfrey-Kittle2015-09-01
|\ | | | | Add test to compare glyph areas between weights
| * Add test to compare glyph sizes between fonts.James Godfrey-Kittle2015-08-31
| | | | | | | | | | | | 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).
| * Allow source and output UFOs to be tested.James Godfrey-Kittle2015-08-31
|/
* Merge pull request #100 from jamesgk/shape-fixJames Godfrey-Kittle2015-08-31
|\ | | | | Always deal with floats when mixing font masters.
| * Always deal with floats when mixing font masters.James Godfrey-Kittle2015-08-21
|/ | | | | | | | | 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.
* Merge pull request #97 from google/delivery-updatesdougfelt2015-08-20
|\ | | | | Delivery updates
| * Hinted TTF updates 15/08/20.James Godfrey-Kittle2015-08-20
| |
| * Unhinted output updates 15/08/20.James Godfrey-Kittle2015-08-20
| | | | | | | | Note that these binaries are also missing mark/mkmk features.
| * Update missing anchors based on source updates.James Godfrey-Kittle2015-08-20
| |
| * Resource updates 15/08/20.James Godfrey-Kittle2015-08-20
| |
| * Source updates 15/08/20.James Godfrey-Kittle2015-08-20
| |
| * Merge branch 'delivery-script-updates' into delivery-updatesJames Godfrey-Kittle2015-08-20
|/|
| * Script updates 15/08/20.James Godfrey-Kittle2015-08-20
| |
* | Add top anchors to composite .smcp, .NAV glyphs.James Godfrey-Kittle2015-08-12
| | | | | | | | | | | | | | 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
* | Hinted TTF updates 15/06/25.James Godfrey-Kittle2015-08-06
| |
* | Explicitly check anchor objects against None.James Godfrey-Kittle2015-07-17
| | | | | | | | | | | | | | | | | | 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:").
* | Merge pull request #65 from google/delivery-updatesJames Godfrey-Kittle2015-06-29
|\ \ | | | | | | Delivery updates
| * | Update missing anchors based on source updates.James Godfrey-Kittle2015-06-26
| | |
| * | Resource updates 15/06/25.James Godfrey-Kittle2015-06-26
| | |
| * | Source updates 15/06/25.James Godfrey-Kittle2015-06-26
|/ /
* | Merge pull request #51 from google/name-table-fixJames Godfrey-Kittle2015-06-22
|\ \ | | | | | | Correct metadata related to font names and weights.
| * | Explicitly set weight class in OS/2 table.James Godfrey-Kittle2015-06-22
| | | | | | | | | | | | Without this, ufo2fdk sets both Light and Regular to 400 by default.
| * | Correctly set PostScript font name in UFOs.James Godfrey-Kittle2015-06-22
| | | | | | | | | | | | | | | This propagates to name ID 6 in the name table, and font name info in the CFF table.
| * | Correct family and style data in name table.James Godfrey-Kittle2015-06-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge pull request #63 from google/contour-fixBehdad Esfahbod2015-06-20
|\ \ \ | | | | | | | | Contour fix
| * | | Don't round interpolated component scaling values.James Godfrey-Kittle2015-06-19
| | | | | | | | | | | | | | | | | | | | Basically a redo of 9292364c1a122498ada2616fdd20683c27c80e15, except more conservative.
| * | | Revert "Don't convert mixed glyph values to ints."James Godfrey-Kittle2015-06-19
|/ / / | | | | | | | | | | | | This reverts commit 9292364c1a122498ada2616fdd20683c27c80e15. Necessary because it caused condensed glyphs to italicize incorrectly.
* | | Merge pull request #61 from google/delivery-updatesJames Godfrey-Kittle2015-06-19
|\ \ \ | | | | | | | | Delivery updates
| * | | Insert kerning subtables more aggressively.James Godfrey-Kittle2015-06-17
| | | | | | | | | | | | | | | | | | | | | | | | Updated glyphs require more kerning subtable breaks to avoid crashing makeotf. The subtable sizes are still decided somewhat arbitrarily based on trial-and-error.
| * | | Revise updated scripts to run without FontLab.James Godfrey-Kittle2015-06-17
| | | |
| * | | Update missing anchors based on source updates.James Godfrey-Kittle2015-06-17
| | | |
| * | | Resource updates from Paratype 15/06/16.James Godfrey-Kittle2015-06-17
| | | |
| * | | Source updates from Paratype 15/06/16.James Godfrey-Kittle2015-06-17
| | | |
| * | | Merge branch 'delivery-script-updates' into delivery-updatesJames Godfrey-Kittle2015-06-17
| |\ \ \ | | | |/ | | |/|
| | * | Script updates from Paratype 15/06/16.James Godfrey-Kittle2015-06-17
| | | |
* | | | Merge pull request #54 from moyogo/readme-nototoolsBehdad Esfahbod2015-06-12
|\ \ \ \ | |/ / / |/| | | Nototools moved to https://github.com/googlei18n/nototools
| * | | Nototools moved to https://github.com/googlei18n/nototoolsDenis Jacquerye2015-06-12
|/ / /
* | | Merge pull request #52 from google/mix-glyph-fixJames Godfrey-Kittle2015-06-11
|\ \ \ | |_|/ |/| | Don't convert mixed glyph values to ints.
| * | Don't convert mixed glyph values to ints.James Godfrey-Kittle2015-06-11
|/ / | | | | | | | | | | 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....
* | List eog with post-production dependencies.jamesgk2015-05-31
| | | | | | | | Part of #41
* | Add link to Google Fonts page to README.mdRoozbeh Pournader2015-05-28
| |
* | Remove old Windows build file.Roozbeh Pournader2015-05-27
| |
* | [minor] Move "Setup" in README.md one level down.Roozbeh Pournader2015-05-22
| |
* | Add general project description to README.md.Roozbeh Pournader2015-05-22
| |
* | Bump up build number to 01289 to take a cut for Android.Roozbeh Pournader2015-05-21
| |
* | Remove various hot fixes from touchup_for_android.py.Roozbeh Pournader2015-05-21
| | | | | | | | These are now fixed in the fonts themselves.