Replies: 3 comments 2 replies
-
There shouldn't be anything about stb_truetype (or OpenGL) that would cause this. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your response, Sean. One thing I've noticed, which may or may not be relevant, is a slight difference in how the first bytes of the font data are printed out, depending on the method of loading:
I understand that this might simply be a formatting difference in the printout, but I wanted to mention it in case it provides any clues. The actual binary data appears to be the same in both cases. Do you think this could have any impact on how stb_truetype processes the font data? |
Beta Was this translation helpful? Give feedback.
-
I will continue to investigate other aspects of my implementation and settings that may affect the rendering of undisplayed text. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I'm working on a project where I use the stb_truetype library for rendering text in an OpenGL environment. I've encountered a problem related to different methods of loading font data. Here's a detailed description of the situation:
xxd -i 9x18.ttf > font_data.c
.fontData
array, which contains the data of "9x18.ttf" font, in my project..ttf
file, the text renders correctly.fontData array
with "9x18.ttf" data, the text does not display in the window.stbtt_InitFont
andstbtt_BakeFontBitmap
functions for font initialization and baking.Text rendering is done using
stbtt_GetBakedQuad
and standard OpenGL calls.stbtt_InitFont
returns success in both loading methods.I would appreciate any suggestions or insights that might help me solve this problem.
Beta Was this translation helpful? Give feedback.
All reactions