Re: [ft-devel] longjmp issue 1

2014-12-08 Thread suzuki toshiya
Dear Werner, I'm quite sorry for my latency with this issue. I guess this error might be caused by a removal of FT_INVALID_(). otvalid has a super validator class, OTV_Validator, which includes FT_Validator as a member (otvalidator-root is typed as FT_Validator). To use FT_INVALID() samely in

[ft-devel] FTLicense Clarifications

2014-12-08 Thread Jonathan Reyes
Hi FreeType Developers, Good day! I am writing to you guys to clarify some matters related to giving credits to your team. We plan to use the FreeType License(FTL.txt) Let me start by stating the conditions in which your software will be used. 1. Only FreeType libraries will be

Re: [ft-devel] longjmp issue 1

2014-12-08 Thread Werner LEMBERG
Thus, the easiest solution would be keeping both of FT_INVALID_() and FT_INVALID() in ftvalid.h, and, updating FT_INVALID_() in otvcommn.h to new syntax. OK. I attached a sample patch. I could reproduce SEGV by Roboto-Thin.ttf, and the binary with the sample patch does not crash. Works

Re: [ft-devel] FTLicense Clarifications

2014-12-08 Thread Werner LEMBERG
1. Only FreeType libraries will be redistributed, sources will not be included. OK, but ... 2. Our customers, which are developers, will have to link against those FreeType libraries. ... normally you need FreeType header files also. Does your API hide FreeType completely? 3. The

Re: [ft-devel] FTLicense Clarifications

2014-12-08 Thread Jonathan Reyes
Hi Mr. Lemberg, Thank you for getting back to me so quickly. Sorry I didn't explicitly mentioned that header files are also included, but yes, libraries and headers will be distributed. Including `FTL.txt' doesn't make sense for such cases – they are delivering *final* products that are not