> the FreeType API defines several FT_LOAD_TARGET_XXX constants that > determine which hinting algorithm to use when loading outlines > from a font file: > > FT_LOAD_TARGET_NORMAL => hint for normal anti-aliased rendering > FT_LOAD_TARGET_LIGHT => same as above, but hint less ! > FT_LOAD_TARGET_MONO => hint for monochrome rendering > FT_LOAD_TARGET_LCD => hint for horizontal LCD rendering > FT_LOAD_TARGET_LCD_V => hint for vertical LCD rendering > > Notice that: > > - you should only use *one* of these values in your load flags; > you cannot OR them, because they're not simple bit flags ! > > - this means you cannot combine them, i.e. there is no "light > lcd" mode. Light hinting is intended for normal anti-aliased > rendering only. > > However, FreeType makes a distinction between the hinting > algorithm being used, and the pixel mode of the target > bitmaps. For example, it is possible to use the "light" hinting > algorithm and have the results rendered in horizontal LCD pixel > mode, with something like: > > FT_Load_Glyph( face, glyph_index, load_flags | FT_LOAD_TARGET_LIGHT ); > FT_Render_Glyph( face->glyph, FT_RENDER_MODE_LCD );
I've added this to the documentation of the FT_LOAD_XXX enumerations. Werner _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel