Results 168 comments of Sean Barrett

It's not a decision. > There are a number of reasons to **consider** moving off of github:

stb_truetype will only bake the .notdef glyph if you ask for it. If you want the 26 uppercase characters in a font atlas, that's what you'll get; it would be...

Don't worry about it, the tests are mostly for my purpose, not for your testing. (The details is they are standalone and require a -D on the commandline to determine...

As to the submission: This is the kind of robust complexity that I generally try to avoid in the stb libraries. For example, libjpg supports streaming images, whereas stb_image requires...

My biggest concern is that this leads to stb_image_write creating a file format that stb_image can't read, which I can 100% gaurantee will cause friction in the future.

Given there's no way we're going to have an EXR reader, and the issue I raised about reading what we write, I think maybe the best solution is to separate...

There's no way to progammatically extend stb_image. I imagine people have probably added requests for extensions to allow adding new formats externally, but it really doesn't make sense. You can...

Because this implementation supports both 8- and 16-bit channels by treating them as 1 or 2 bytes and using a multiply by the component count, it will slow down the...

ok, yeah, that works too. i didn't realize it was a loop-constant that compiler MIGHT have fixed, but still worth changing.

Is there any reason you'd think they might *not* be admissable?