W3C home > Mailing lists > Public > www-font@w3.org > January to March 1996

Font Hinting

From: <glen@met.bitstream.com>
Date: Wed, 07 Feb 96 00:15:57 est
Message-Id: <9601078236.AA823681025@met.bitstream.com>
To: admin@verso.com, david@dsiegel.com, www-font@w3.org, james@met.bitstream.com, johnc@met.bitstream.com, johns@met.bitstream.com, ray@met.bitstream.com, glen@met.bitstream.com
     David and Hussein,  I'm running out of gas so this will be my last 
     entry this evening. I will try to complete the remaining topics 
     tomarrow. Glen Rippel
     Yes, hinting is very difficult, and implemented differently depending 
     on the format. Most fonts require a good set of hints below 60 pixels. 
     Hints maintain the uniform stroke thickness, uniform character 
     heights, and baseline references, side bearings, ect..... and allow 
     for hours of stress free reading.
     Allowing designers to choose any font format combination for authoring 
     and maintaining the original font fidelity is almost an impossible 
     goal and this is achieved by using TrueDoc. TrueDoc has a unique 
     automatic hinting process which is applied to the character shapes 
     during the authoring process. The results of the TrueDoc character 
     recording process are excellent and can only be improved upon by font 
     designers hand tuning for discrete point sizes.
     In addition to TrueDoc's excellent auto-hinting process, our OEMs and 
     ISVs also can make use of TrueDoc's anti-alias modules that deliver 
     grey scale bitmaps during the rendering process.
     Bitmaps can be delivered which are 32K pixels high. Rendering speed of 
     bitmaps for screens are in the range of 400 to 500 characters per 
     second on a 486/66. Once generated and cached, the performance is 
     limited mostly by the blit operations.
Received on Wednesday, 7 February 1996 01:55:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:37 UTC