| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
Closes: #922457
|
| |
|
| |
|
| |
|
|\
| |
| |
| | |
Update to upstream version '0~20170802'
with Debian dir 034d09721149c2057bd9c72853b45fa489d99ed6
|
| | |
|
| |
| |
| |
| |
| | |
Accidentally used NMU version from debdiff from Markus. Updated for
reupload.
|
| | |
|
| |
| |
| |
| | |
Dependency on devscripts dropped and licensecheck is added.
|
| |
| |
| |
| |
| | |
Don't remember why I added conflicts in first place but it is not
required.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Both me and Christian Perrier tried sponsoring the same version, my upload
was several hours earlier so it prevailed but I couldn't push to the VCS,
resulting in Christian thinking no upload was done.
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| |
| |
| |
| | |
Upstream version 0~20160106
# gpg: Signature made Sunday 17 January 2016 10:24:04 AM IST using RSA key ID 87700B7E
# gpg: Good signature from "Vasudev Kamath <kamathvasudev@gmail.com>" [ultimate]
# gpg: aka "Vasudev Kamath (Debian Maint) <kamathvasudev@gmail.com>" [ultimate]
# gpg: aka "Vasudev Kamath <vasudev@copyninja.info>" [ultimate]
|
| |\ |
|
| | |\
| | | |
| | | | |
Update post-production and testing
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
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
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | | |
If we wait until the UFO glyph is drawn to a FontTools glyph, the
contours (one of which is a reflected component) will have opposite
directions. When decomposed in the build scripts, the glyph's contours
both have the correct direction.
|
| | |\
| | | |
| | | | |
TTF generation
|
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |\ \
| | | |/
| | |/| |
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.
|
| | | | |
|