Re: [ft-devel] Enquiry about GSoC project
> I am eager to take part in GSoC 2018 in the project that aims to > covert the documenataion of FreeType to from HTML to Markdown. > Could anyone please guide me as to where I should be starting? I > have coded in Python for about 3 years now and am comfortable in it. Somnath, please look up the mailing list archive; suggestions for using MarkDown (and even some conversions) have already be made. http://lists.nongnu.org/archive/html/freetype-devel/ Note that it is *your* job to prepare a proposal of what to do. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Contribution to freetype
> My name is Parth Wazurkar. I am a sophomore student at Indian > Institute Of Information Technology Nagpur, India studying Computer > Science and Engineering. I am interested in working for > freetype. How should I start contributing? Please help. Parth, please look at FreeType's GSoC page https://www.freetype.org/gsoc.html Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Contributing to the organization -GSOC
Hello Gayan! > I'm Gayan Kavirathne, a final year computer science & Engineering > undergraduate at University of Moratuwa - Sri Lanka. I have been > working on project which converts freeType,openType and RegularType > fonts to unicode. It currently supports only for south east asian > fonts only. So your organization made an interest on me. Looking > forward to contribute. Excellent! > Split the existing fuzz target into many Above project looks > interesting and I would like to get know the mentors to get started > with. This e-mail list is the right forum to discuss GSoC ideas; all potential mentors are reading it. However, you should first get a bit acquainted with FreeType fuzzing – please follow the links and try to compile FreeType's fuzzer binary (see `src/tools/ftfuzzer'). Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Contribution to freetype
Sir, My name is Parth Wazurkar. I am a sophomore student at Indian Institute Of Information Technology Nagpur, India studying Computer Science and Engineering. I am interested in working for freetype. How should I start contributing? Please help. ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] LLP64 model outside Win64
On 13/02/18 07:17, Werner LEMBERG wrote: >>> Maybe we can announce in the forthcoming release that we are >>> switching to C99 later on. >> > >> I have no objection to have some conditional parts for C99-specific >> feature, but I feel negative with the total migration to C99. "For >> LLP64 platform except of Win64, C99 compiler is needed" would be >> enough, if Pierre's guessing is correct. > > Hmm. Even the dinosaur called `emacs' moved to C99 a few years > ago :-) While being conservative, it doesn't make sense in case > everyone already moved on – I've looked into Wikipedia's C99 page, and > it seems that there aren't any major compilers that don't support it > (at least the very decent set of changes we would need or use). The concern is installed bases of systems like AIX, HP-UX, OpenVMS that haven't been updated in some time, and using the default C compiler. With Ghostscript, we regularly get reports from such users (not to mention Windows 95/98/ME, NT 4.0, OS/2, etc, etc - !). It is odd that they insist on using obsolete hardware and operating systems, but want the latest releases of other software! Using C99 types, with sane fallbacks makes sense, but using the more invasive parts of C99 (like mixing declarations and code) could be problematic. >> The usage of FT_UINT_TO_POINTER() macro is only used to store the >> 32-bit integer (GID) into the storage of FT_List object directly. I >> feel it's overkill to close C89 support just to keep this method in >> LLP64 on the platforms which we have not known their names yet. > > I still vote for the possibility to change FT_UINT_TO_POINTER in a > configuration file, for example with some code in `ftstdlib.h'. I guess that would come under the heading of "sane fallback" mentioned above. Chris ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
