Broken Geometry for ij(?) in some boundary cases
Closed this issue · 5 comments
Logo121 commented
Since #1882 I've been building with the boundary metric cases allowed in private build sample (along with the regular cases):
- Weight of 100 and 900
- Width of 434 and 664
- Slant of 0, 9.4 and 15
A few version ago I start getting these messages when building:
Detected broken geometry when processing .ligature-part.J@compatLigature1/0.8370763848151533/0/200.22867124778466
Detected broken geometry when processing .ligature-part.J.serifedSymmetric@compatLigature1/0.8370763848151533/0/200.22867124778466
Detected broken geometry when processing .ligature-part.J.serifedBothSides@compatLigature1/0.8370763848151533/0/200.22867124778466
Detected broken geometry when processing .ligature-part.J.serifless@compatLigature1/0.8370763848151533/0/200.22867124778466
Which I think happens with Heavy (900), Extra Condensed (434) and max Slant (15). It could be the other cases though.
be5invis commented
Well currently broken geometries won't crash the build, instead it will leave a blank glyph.
Maybe you can try find it from some J-related ligatures (IJ or DJ)
Logo121 commented
Well my guess is correct, IJ in Heavy Ultra Condensed and max Slant:
jmcwilliams403 commented
I keep meaning to open an issue that IJ/ij should be no closer together than the vertical lines of U/u
be5invis commented
Hook lf J being too tight...