freetype-devel
[Top][All Lists]
Advanced

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

Fw: [Devel] Re: The guts of yudit-2.xx


From: Werner LEMBERG
Subject: Fw: [Devel] Re: The guts of yudit-2.xx
Date: Thu, 01 Feb 2001 08:52:46 +0100 (CET)

Can someone please verify this claim?

Currently, I don't have enough time to do it by myself.


    Werner

--- Begin Message --- Subject: Re: [Devel] Re: The guts of yudit-2.xx Date: Wed, 31 Jan 2001 17:03:11 -0800 User-agent: Mutt/1.2.5i
On Thu, Feb 01, 2001 at 01:08:50AM +0100, Werner LEMBERG wrote:
> > ... I think this happens due to the bug in load_truetype_glyph() but
> > I will have to look into that tomorrow.
> 
> `The' bug?  Which one?  Do you have a patch?

If I am not mistaken load_truetype_glyf() does not do all the calculations
prescribed by the manual. 

Check out: http://fonts.apple.com/TTRefMan/RM06/Chap6glyf.html

Specifically:

The transformation entries determine the values of an affine transformation 
applied to 
the component prior to its being incorporated into the parent glyph. Given the 
component 
matrix [a b c d e f], the transformation applied to the component is:

                 a             c
    x' = m * (( --- ) * x + ( --- ) * y + e )
                 m             m

                 b             d
    y' = n * (( --- ) * x + ( --- ) * y + f )
                 n             n

where m = max (abs(a), abs(b))
n = max(abs(c), abs(d))
and if (abs(abs(a) - abs(c)) <= 33/65536 then m = 2 * m
if (abs(abs(c) - abs(d)) <= 33/65536) then n = 2 * n

But unfortunately this does not seem to be the cause of the Aring problem,
at least after I modified the Freetype code to calculate m and n 
properly Aring still did not look right. Anyway I am still looking into
the problem and I will keep you posted.

Regards,
AG

-- 
(650) 786-9047 / (650) 786-9553 fax

--- End Message ---

reply via email to

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