Re: [ft-devel] Two patches for FT

[Werner LEMBERG]

> version: 2.1.9 and current (dating back to the end of december)
> font: Tahoma 8px
> settings: native bytecode interpreter enabled, antialiasing disabled

Don't complain about that!  The tahoma font (version 2.60) has this
gasp table:

  <gasp>
    <gaspRange rangeMaxPPEM="8" rangeGaspBehavior="2"/>
    <gaspRange rangeMaxPPEM="16" rangeGaspBehavior="1"/>
    <gaspRange rangeMaxPPEM="65535" rangeGaspBehavior="3"/>
  </gasp>

Flag value 1 means `with bytecode', value 2 means `anti-aliased', and
value 3 means `with bytecode and anti-aliased'.

Thus, for sizes <= 8ppem, the table says ``don't use the bytecode
interpreter, just do anti-aliasing''.  Consequently, using tahoma with
disabled antialiasing at 8ppem gives bad results.  Starting with
9ppem, the results with the current CVS version of FreeType are just
fine.


    Werner