RE: [Devel] Type 1 rendering and Euler numbers

[Turner, David]

> That's right. The only thing you could do for the moment is modify the
> Type 1 driver to automatically render a glyph bitmap when the 
> load flags contain the FT_LOAD_RENDER bit, and then use a different 
> algorithm.
> 
> However, this would mean that later conversions of outlines, 
> e.g. with FT_Glyph_To_Bitmap, would generate different results. I let 
> you imagine what kind of support nightmare this could be.
> 
> Making FreeType capable of using distinct rasterizers based 
> on the original font format would mean quite a number of changes to the 
> library. Note that this is uninteresting, but it's a lot of work.
> 

Please allow me to correct myself. It is possible to ask for an alternative
rendering behaviour by defining new FT_OUTLINE_FLAGS bit-flags, and these
will be passed nicely from the font driver to the rasterizers.

So, it's possible to define something like FT_OUTLINE_TYPE1_DROPOUTS,
and have the code in ftraster.c behave differently wether this bit is
set of not.

In other words, it's possible without tearing the library apart, though
you still need to write the new renderer. And of course, you must set the
bitflag in the glyph loader.

Hope this helps,

- David Turner
- The FreeType Project  (www.freetype.org)


> 
> > 3. Would it help to turn on auto-hinting for Type 1 fonts? 
> > (Of course I'll try this myself, but any other experiences 
> are welcome).
> > 
> Maybe yes. The Type 1 hinter now lags severely behind the 
> automatic hinter
> for certain fonts. For others, its results are still better 
> (especially
> for monochrome rendering).
> 
> 
> Regards,
> 
> - David Turner
> - The FreeType Project  (www.freetype.org)
> 
> > Best wishes,
> > 
> > Graham Asher
> > 
> 
> _______________________________________________
> Devel mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/devel
>