Sean Barrett

I'm not sure why it's relevant, but you brought it up, so: I didn't go on a Twitter rant bashing people "just working on OSS". I reiterated to my friends...

>engineers like @nothings please don't tag me into this thread, i unsubscribed from it for a reason, tagging me sends me a notification that i don't want. i don't know...

See the line above: https://github.com/nothings/stb/blob/master/stb_truetype.h#L1584 The font doesn't contain a supported unicode-to-glyph mapping table. There are multiple types, and stb_truetype handles all the major types, but apparently this file has...

>Format 14: Unicode Variation Sequences > >Subtable format 14 specifies the Unicode Variation Sequences (UVSes) supported by the font. A Variation Sequence, according to the Unicode Standard, comprises a base...

I have two, separate, unrelated answers to this. First, based on your analysis, we are thinking this is format=14. And yes, it appears that that mapping requires unicode codepoint pairs...

Second, if I run with the font you provided, or I download the same font from another source, when I run it, it works correctly in stb_truetype and reports `format...

From the documentation: ``` COMPILING & LINKING In one C/C++ file that #includes this file, do this: #define STB_IMAGE_RESIZE_IMPLEMENTATION before the #include. That will create the implementation in that file....

What do you mean it assumes platform native is little-endian?

But the conversion code is not big-endian to little-endian, it's big-endian to platform native. Big-endian to little-endian would just swap the bytes, which is not what this code does.

Do you understand what the code you added is doing, or did you just copy-paste it without understanding it?