0.5.1 issues
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| News Cycle |
New
|
Undecided
|
Unassigned | ||
Bug Description
DSIG tables were not included.
FFTM tables should not be included, but were.
GlyphOrder changed (doesn't really matter)
The usWeightClass in the OS/2 table of the Regular is 500 but should be 400
The version numbers of both styles should be kept in sync
The vertical metrics should be 2574/-538/0 or the high and low glyphs will be clipped in some environments:
$ fontbakery-
Parameter NewsCycle-Bold.ttf NewsCycle-
ymax 2574 2510
hhea.ascent 2510 2510
OS/2.sTypoAscender 2510 2510
OS/2.usWinAscent 2510 2510
ymin -676 -794
hhea.descent -538 -538
OS/2.sTypoDescender -538 -538
OS/2.usWinDescent 538 538
hhea.lineGap 0 0
OS/2.sTypoLineGap 0 0
hhea total 3048 3048
typo total 3048 3048
win total 3048 3048
UPM:Heights 2048:3250 2048:3304
UPM:Heights % 158 % 161 %
High Glyphs
NewsCycle-Bold.ttf: Aringacute
Low Glyphs
NewsCycle-Bold.ttf: kcommaaccent Kcommaaccent aringbelow Aringbelow ncommaaccent t_comma Ncommaaccent Rcommaaccent lcommaaccent Scommaaccent Lcommaaccent T_comma scommaaccent rcommaaccent Gcommaaccent
NewsCycle-
Fixed example attached.
| Dave Crossland (davelab6) wrote | #1 |
| Nathan Willis (n8) wrote | #2 |
Could I request that we not combine multiple issues into one bug report? Particularly when they're not related. I don't mind automatically generated reports (which I'm assuming is where this info originated). But lumping them together makes it extremely difficult to track progress and makes comment threads difficult if not impossible to follow.