>> I wonder what's the best solution to get FreeType's error strings from
>> its error numbers? E.g. "cannot open resource" from `FT_THROW(
>> Cannot_Open_Resource )'. Since I cannot locate anything in the docs
>
> This must be an oversight on your side, since FreeType comes with a
complete
>
Hi all,
I propose to default to straight RGBA color space in FreeType. This is
especially important before the next FreeType release 2.10 with
CPAL/COLR support. I will quote from PNG documentation for the
overarching reason:
"PNG also uses only unassociated alpha, wherein the actual gray or
> I wonder what's the best solution to get FreeType's error strings
> from its error numbers? E.g. "cannot open resource" from
> `FT_THROW( Cannot_Open_Resource )'. Since I cannot locate anything
> in the docs
This must be an oversight on your side, since FreeType comes with a
complete
>
> > After some debugging, I found out that, I was using binary search on
> > the encodings array in the `char_index' function, although it wasn't
> > sorted (so foolish of me :( ). Now, fixed! Thanks.
>
> In the commit message, you write
>
> Use `linear search' instead of `binary search' in
I wonder what's the best solution to get FreeType's error strings from its
error numbers? E.g. "cannot open resource" from `FT_THROW(
Cannot_Open_Resource )'. Since I cannot locate anything in the docs I
wonder if
https://stackoverflow.com/questions/31161284/how-can-i-get-the-corresponding
