Incorporate italic sources into build
arrowtype opened this issue · comments
In #42, I tested generating Italics, and determined that I need to make some visual corrections.
With 84ee1c3 I have started doing these corrections with the basic A–Z, a–z, and 0–9 of ExtraBold and Light.
Next, I need to:
- make visual corrections to irregular sources
- make a full designspace to incorporate the italic sources
- incorporate into sources
- incorporate into instances
- make static version of designspace
- build, and fix build script to handle italics
- if moving forward with italics, decompose these glyphs in all sources and adjust drawings for italics
- the prep build script needs to generate bouncy italics, with diagonal bounces along the italic angle
- generate necessary sources
- fix xShift for yShift
Incompatibilities to fix, Jun 9:
ERROR:cu2qu.ufo:Glyphs named 'arrowNE' have different number of segments
ERROR:cu2qu.ufo:Glyphs named 'arrowNW' have different number of segments
ERROR:cu2qu.ufo:Glyphs named 'arrowSW' have different number of segments
ERROR:cu2qu.ufo:Glyphs named 'arrowSE' have different number of segments
ERROR:cu2qu.ufo:Glyphs named 'invertedbrevecmb' have different number of segments
ERROR:cu2qu.ufo:Glyphs named 'bracketangleright' have different number of segments
ERROR:cu2qu.ufo:Glyphs named 'dotbelowcmb' have different number of segments
ERROR:cu2qu.ufo:Glyphs named 'caroncomb' have different number of segments
Solution: add these as glyphs to decompose in prep-build.py. Very likely, they were getting decomposed in select sources only, by the ufo2ft filter that decomposes scaled/flipped components.
Okay! It's a subtle but important difference: the bouncy italics now have their yShift compensated for with an xShift.
In the below video, the old font is the bottom row, and the new font is the top row. The old font moves only vertically, causing problems in the bouncy versions of glyphs, while the new font moves along the italic slant, allowing for better spacing.