Re: [ft-devel] Rendering artifacts

[malc]

On Wed, 8 Sep 2010, Werner LEMBERG wrote:

> > FWIW other fonts are also affected at certain point sizes Liberation
> > Mono (Regulr) diagonals making the 'v' are very thin, Liberation
> > Sans Italic the leg of 'y' is completely invisible,
> 
> I can only repeat: Ignoring the `gasp' table leads to bad results.
> Checking Liberation Sans Italic version 1.06 with ftview: The `gasp'
> table says to use B/W rendering for 9<=ppem<=17, and the leg of `y' is
> *always* visible in this range.  The same for larger ppem values (and
> anti-aliasing).
> 
>
> > I have stumbled upon [1] and it looks as if Times New Roman's 'z'
> > suffers from the same problem and the author gives a clue as to why.
> 
> Again, I've justed tested with ftview, and everything is just fine
> (provided you follow the `gasp' table values).
> 
> > The way i understand it - Windows's rasterizer (with or without
> > ClearType) processes the bytecode (or output of the BCI) differently
> > so that the problem never manifests itself.
> 
> I don't think so.  Can you provide links which gives more details?

Sorry for forgetting to actually provide the text for [1], here goes:
http://translated.by/you/why-linux-fonts-suck/original/

-- 
mailto:address@hidden