freetype-devel
[Top][All Lists]
Advanced

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

Re: [ft-devel] Experimental: v38 interpreter with minimal backwards comp


From: Nikolaus Waxweiler
Subject: Re: [ft-devel] Experimental: v38 interpreter with minimal backwards compatibility mode and linear advance widths
Date: Mon, 18 Jan 2016 20:23:53 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0

This is funny. I think I found a way to make bytecode rendering similar to the autohinter in smoothness, it even helps making old fonts look less ugly. in Ins_MIRP, I added:

    if ( exc->backwards_compatibility && exc->GS.freeVector.x == 0x0 )
    {
      control_value_cutin = control_value_cutin / 2;
      minimum_distance = minimum_distance / 2;
    }

In Ins_MDRP, I added:

    if ( exc->backwards_compatibility && exc->GS.freeVector.x == 0x0 )
    {
      minimum_distance = minimum_distance / 2;
    }

(I know both values are actually FT_F26Dot6 but this works for my proof-of-concept)

I'm browsing around the net and on https://typekit.com/fonts and am quite pleased with what I see :D

I attached the new full patch again. It sure looks like I have to have a harder look at this and find out if I should change more minimum distances and CVT cutin values.

Uh, should I push a branch to GitHub?

Attachment: minimal_v38_interpreter_v2.patch
Description: Text Data


reply via email to

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