Re: [ft] Bytecode enabled rendering

[Werner LEMBERG]

> 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?

You might look up the old emails.  I've posted some images from a
debugging session with fontforge which shows the problem clearly.  The
result FreeType produces has been confirmed with Rogier's TT engine
(which is completely independent of FreeType) and is the `right' one.

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

Right, and Monotype has never used a different rasterizer to verify
that the result is portable -- and Apple uses the same engine (for
monochrome rasterization).

> 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.

Please send a list of differences for future reference.

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

Unfortunately, it's non-trivial bytecode hackery.  Maybe you succeed
-- if you do please send the results to the list.


    Werner