The FreeType Project

Mentors: Student: Kushal K S V S

<p>For a widely used library like FreeType, a test framework to check font rasterization is a must have. Having a test framework to test the output of the library avoids many possible errors in early-stage. The project is based on enabling the programmers visualize what exactly is changing and helping them decode why is it changing.</p> <h4>Output Glyph --&gt; Test_Framework --&gt; Debugging- -&gt; Quality Code</h4> <p>The working of the Test_Framework</p> <p>1.Generating glyph images (using libpng) for both "base" and the "test"(developer) version of the FreeType library. This is done by linking both version's DLL to the code.</p> <p>2.Comparing the images pixel by pixel and making a sprite sheet for each of the glyph. Each image in the sprite sheet corresponds to an effect after comparison.</p> <p>3.An web interface is generated which lists all the glyphs that are rendered incorrectly in the 'test' version. Selecting a particular image will animate the glyph. (Using the concept of CSS Sprite Sheet Animation) (Various animation effects used as per the needs of the developer.)</p> <p>All the code is written in ANSI C.</p>

Mentors: Student: Ewald Hew

<p>Thanks to Adobe's contribution of their CFF engine, FreeType has excellent rasterization of CFF fonts. However, Type 1 fonts, a similar PostScript font format, has relatively poor rasterization results. This is due to Type 1 being a legacy format, coupled with lack of maintenance for the corresponding module in FreeType. By extending the new CFF module, we can leverage its high quality output for an old format like Type 1.</p>