freetype-devel
[Top][All Lists]
Advanced

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

Re: [ft-devel] GX support now working


From: Dave Arnold
Subject: Re: [ft-devel] GX support now working
Date: Thu, 4 Jun 2015 13:21:27 -0700
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

Note that Type 1 and CFF fonts that follow the "Black Book" guidelines and 
avoid self-intersecting outlines will render correctly with either fill rule. Adobe 
rasterizers typically use even-odd at small sizes and non-zero at larger sizes.

-Dave

On 6/4/2015 12:19 PM, Behdad Esfahbod wrote:
On 15-06-04 12:15 PM, Alexei Podtelezhnikov wrote:
On Wed, Jun 3, 2015 at 4:28 PM, Behdad Esfahbod <address@hidden> wrote:
TrueType fonts have a 'non-zero winding' fill rule, whereas Postscript has
'even-odd'.  That's what causes the artifacts.
FT_OUTLINE_EVEN_ODD_FILL is never set by freeetype. So actually
FreeType always uses non-zero winding rule even for TrueType.
I thought TrueType *is* non-zero.  I also thought Type1 / CFF are even-odd.

More so, the outer outline is always filled on the inside regardless of
the direction (ftgrays.c:1285).
Right.  That's what non-zero means.  Doesn't matter if positive or negative.


FreeType is less sophisticated and resort
to what works the best even for broken fonts.





reply via email to

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