You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I happened to have a handful of OTF fonts installed. I seem to get the same behavior with all of them: in the Glyph Buffer sample, the call to font.getTextMetrics() results in an empty bounding box and returns an error originating from within the BL_PROPAGATE( blFontGetGlyphBounds() ) in blFontGetTextMetrics(). It does seem to render the font though. Attaching one of the fonts. font.zip
The text was updated successfully, but these errors were encountered:
kobalicek
changed the title
blFontGetTextMetrics() fails with some OTF fonts on Windows 10
blFontGetTextMetrics() & blFontGetGlyphBounds() fails with OTF/CFF fonts
Jun 11, 2019
Unfortunately I can confirm this. The reason this fails is that OTF fonts have no bounds stored in the font, the outlines have to be inspected in order to get bounds. I will definitely try to finish this.
Thanks, this should work! I'm having trouble building from git for some reason (probably I'm doing something stupid; beta7 and beta 8 zips worked just fine). I just wanted to verify that more complete OTF font support is on the roadmap. It sounds like it is, and that's great! For my purposes, I don't think I need much beyond what's in the sample code other than right-to-left text working; guessing that's probably part of 'Advanced Text Layout' on the roadmap.
I happened to have a handful of OTF fonts installed. I seem to get the same behavior with all of them: in the Glyph Buffer sample, the call to font.getTextMetrics() results in an empty bounding box and returns an error originating from within the BL_PROPAGATE( blFontGetGlyphBounds() ) in blFontGetTextMetrics(). It does seem to render the font though. Attaching one of the fonts.
font.zip
The text was updated successfully, but these errors were encountered: