Re: [ft] Bytecode enabled rendering

[Anton Danilov]

Thanks for the answer, Werner!

I see your point. But what really makes this situation strange and 
unnatural is that Windows makes "undocumented and unpredictable" things 
which produce well-documented and predictable results, am I not right?

It's clear that these fonts were designed by Monotype to look exactly as 
they look under Windows.

You're speaking about the patch for "these two symbols". I have got 
problems with several symbols on Tahoma 8 pt, some other symbols on 
Tahoma 10 pt, Times New Roman 14 pt.

Maybe, there is some way to fix these symbols on my own if you do not 
plan to create this patch soon?

Anton

Werner LEMBERG wrote:
> > I am experiencing problems with aliasing-disabled rendering, and if
> > you look at Kaya's screenshot (my system, and any other will
> > probably do, shows just the same behaviour)
> >
> > http://kayalabs.com/images/tahoma.png
> >
> > you will see the difference in rendering Tahoma's 8 and v -- in
> > freetype's version you have just one more pixel and it's really
> > disturbing and annoying.
>
>
> This has been discussed at great length on the freetype-devel list,
> IIRC.  The `correct' rendering result of Tahoma on Windows is tightly
> bound to anomalies in the Windows rendering engine which internally
> rounds certain values differently, namely in an undocumented and
> unpredictable way.  With other words, Windows is `wrong'.  The correct
> solution is to fix the bytecode instructions for those two characters
> -- this breaks the digital signature, but FreeType ignores it anyway.
> A longer time ago I announced to provide a patch, but unfortunately I
> haven't found enough time yet to do that.
>
>
>     Werner

Anton.Danilov.vcf
Description: Vcard