Re: [Freetype] Comments on quality

[David Turner]

Hi Michael,

Michael Jansson a écrit :
> 
> Hi,
> 
> I doubt that the use of the gasp table is covered by any patents.
> Considering that the table is nothing but a bunch of integers. I can't see
> how anyone can make such a patent. If you can use 'OS/2' than you can use
> 'gasp'. I do think it is up to the app using a TT rasterizer to us the table
> though, i.e. this is not something that should be used automatically by FT.
> 

Please have a look at US Patent 5,684,510 and tell me that it doesn't cover
the use of the GASP table. I would be extremely surprised if it wouldn't..

As I read it, the patent prevents using data contained in the font. I could
imagine that the table could come from an external database though.. (which
means "libXft" doesn't infringe on the patent)..


> There is a need for ensuring that fonts are rendered b/w at small sizes even
> on WindowsXP where you have Cleartype, and you do get b/w text in some cases
> even there. CJK fonts is a perfect example, where you have b/w embedded
> bitmaps. There are also classes of Latin fonts that needs to be b/w at small
> sizes (e.g. outline fonts, very light fonts, etc). You can re-hint some of
> these fonts. However, this is a very costly and time consuming job, and it
> may not be possible in all cases.
> 
> Fonts smoothing is nice, but it's not the solution to all hinting problems
> (it gets pretty close though).
>
Of course not :o) I'm also pretty certain that using high-quality embedded
bitmaps for common "small" pixel sizes and relying on automatically generated
hints (be they from your font editor or from the FreeType auto-hinter) is
_much_ more cost-effective than having to deal with all the TrueType hinting
voodoo !!

And they also make for smaller font files too (except in the CJK ones, maybe)


Cheers,

- David