If you are ok with revealing what went wrong it would be useful to
know more details. I'm curious and it would be useful to have in the
mailing list archive.

Chris


On Thu, Sep 8, 2011 at 1:02 PM, Louis Desjardins
<[email protected]> wrote:
> That's a great troubleshooting tip - thank-you. Using this causes the
> function to succeed in Android - so I am embarrassed to say that the problem
> is on my end afterall :s
> I will take it from here, thanks for all the help!
>
>> Date: Thu, 8 Sep 2011 06:42:34 +0200
>> To: [email protected]
>> CC: [email protected]; [email protected]
>> Subject: Re: [ft-devel] FT_New_Memory_Face crashes
>> From: [email protected]
>>
>>
>> > The main difference between the standalone and Android app is the
>> > way that the input TTF file is read in, however I verified that my
>> > TTF file is read in correctly in Android, by writing out the buffer
>> > that I read in to a new file, and then comparing the original with
>> > this - they are identical.
>>
>> What about putting the font into a static buffer, this is, converting
>> the font into something like this:
>>
>> const char* font = { 0x01, 0x05, 0x03, ... }
>>
>> This could eliminate one possible source of error.
>>
>>
>> Werner
>

_______________________________________________
Freetype-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Reply via email to