Open netdelight opened 6 years ago
Thanks for the kind words! Unfortunately, there is no Bold of Bellefair. (Nor italic, for that matter.) You will have to match it with another typeface.
Cheers,
Nick Shinn President
Shinntype 42 John Street Orangeville, ON L9W 2P3 Canada
On Mar 14, 2018, at 10:07 AM, netdelight notifications@github.com wrote:
Hello, the font is beautiful but unfortunately, it render not so well when it's used for bold text in web browser (Chrome, Firefox and Edge). Have a look here : https://codepen.io/anon/pen/yKOype https://codepen.io/anon/pen/yKOype — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/shinntype/bellefair/issues/9, or mute the thread https://github.com/notifications/unsubscribe-auth/AOMFrnaVL0ntmCgHxwmvd5IByQU-7oMcks5teSQ2gaJpZM4SqflI.
Since this was brought up at https://issues.skia.org/issues/300502150 I figured I'd comment on this upstream issue. The reason for the incorrect fake-bold is that the (OpenType glyf
based) export of Bellefair currently hosted on Google Fonts contains self-intersecting contours. See some investigation comments on the Skia issue. The .glyphs source file doesn't appear to contain contour self-intersections. The contour self intersections appear to be introduced by some exporter or post processing. This may or may not have something to do with some of the contours in the .glyphs file having the opposite contour direction (ccw) than OpenType expects and what ended up in the exported font file (cw).
In addition to causing the fake-bold and other stroking issues, this means that there is a small amount of "lint" in the Google Fonts version of Bellefair. They aren't very big, but if one draws the h
glyph very large (not fake-bolded, just regular) there are small filled areas below the baseline at the corners of the feet. This is true for a number of glyphs that share this common foot design.
Also, this only appears to affect the glyf
based export (the .ttf
version). The CFF
based export (the .otf
version) appears to be fine.
Faux sux. I have asked the power that is at Google if he would like to family-size Bellefair, but that is not a priority.
Kind Regards,
Nick Shinn RCA, RGD Emeritus President
Shinntype 42 John Street Orangeville, ON L9W 2P3 Canada
On Oct 10, 2023, at 12:07 PM, bungeman @.***> wrote:
Since this was brought up at https://issues.skia.org/issues/300502150 https://issues.skia.org/issues/300502150 I figured I'd comment on this upstream issue. The reason for the incorrect fake-bold is that the (OpenType glyf based) export of Bellefair currently hosted on Google Fonts contains self-intersecting contours. See some investigation comments on the Skia issue. The .glyphs source file doesn't appear to contain contour self-intersections. The contour self intersections appear to be introduced by some exporter or post processing. This may or may not have something to do with some of the contours in the .glyphs file having the opposite contour direction (ccw) than OpenType expects and what ended up in the exported font file (cw).
In addition to causing the fake-bold and other stroking issues, this means that there is a small amount of "lint" in the Google Fonts version of Bellefair. They aren't very big, but if one draws the h glyph very large (not fake-bolded, just regular) there are small filled areas below the baseline at the corners of the feet. This is true for a number of glyphs that share this common foot design.
— Reply to this email directly, view it on GitHub https://github.com/shinntype/bellefair/issues/9#issuecomment-1755762642, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADRQLLQENMYVXSWQHOUUBCDX6VXC7AVCNFSM4EVJ7FEKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZVGU3TMMRWGQZA. You are receiving this because you commented.
Hello, the font is beautiful but unfortunately, it render not so well when it's used for bold text in web browser (Chrome, Firefox and Edge). Have a look here : https://codepen.io/anon/pen/yKOype