freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ft-devel] Re: FT_MAX_CURVE_DEVIATION vs ONE_PIXEL cont'd


From: Алексей Подтележников
Subject: [ft-devel] Re: FT_MAX_CURVE_DEVIATION vs ONE_PIXEL cont'd
Date: Wed, 20 Oct 2010 08:19:52 -0400

Werner, Graham,

Please do not let this slip through the cracks. If you do not want to
harmonize conic and cubic splines completely, you have two choices:

1) DOWNSCALE(ONE_PIXEL) in the conic splines
2) move UPSCALE coordinates to the top of the conic function

The former is ugly in my opinion. The latter at least harmonizes how
the conic and cubic splines work from the start.

Also, you may consider moving back to ONE_PIXEL / 4 in the conics,
as Graham originally intended, but may need some rendering quality
control.

As it stands right now the truetypes are dog-ugly.

Alexei

2010/10/17 Алексей Подтележников <address@hidden>:
> On Sun, Oct 17, 2010 at 4:53 AM, Werner LEMBERG <address@hidden> wrote:
>>> It turns out that since 2.4.3 the cubic deviations have been
>>> estimated *after* UPSCALE, whereas conic ones have been evaluated
>>> *before* UPSCALE.  This was probably the original sin that led to
>>> the misuse of FT_MAX_CURVE_DEVIATION that we've just fixed in
>>> "cubic".  Let's fix the original sin now.
>>
>> I won't comment the patch itself since I'm not too acquainted with
>> those intricate geometric details.  However, please resend your patch
>> as an attachment; your mailing program inserts replaces ordinary
>> spaces with non-breaking space characters at arbitrary places...
>
> Ok. I'm resending the non-intrusive patch as an attachment. The intrusive
> harmonization of the conic and cubic splines is to follow in a separate 
> thread.
>
> Alexei
>



-- 
Alexei A. Podtelezhnikov, PhD



reply via email to

[Prev in Thread] Current Thread [Next in Thread]