>> Its CFF so no
>
> That's just plain lazy :)
>
> surely there's some crossover with ttf?
Not really, since TrueType doesn't have the concept of `hints' at all.
ttfautohint emulates Type 1 hints to a certain extent, but those hints
are created by algorithm (i.e. by FreeType's auto-hinter), whi
On 1 May 2013, at 11:18, Dave Crossland wrote:
> On 1 May 2013 20:16, vernon adams wrote:
>> That's look like good stuff.
>>
>> Will this new code also be integrated into ttfautohint library? :)
>
> Its CFF so no
That's just plain lazy :)
surely there's some crossover with ttf?
__
> Will this new code also be integrated into ttfautohint library? :)
Not directly, since ttfautohint can't handle CFFs. However, maybe the
algorithm influences the auto-hinter also which in turn could
influence ttfautohint.
Werner
___
Freetype-d
On 1 May 2013 20:16, vernon adams wrote:
> That's look like good stuff.
>
> Will this new code also be integrated into ttfautohint library? :)
Its CFF so no
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/list
That's look like good stuff.
Will this new code also be integrated into ttfautohint library? :)
-v
On 1 May 2013, at 11:11, Werner LEMBERG wrote:
> Folks,
>
>
> Adobe, in collaboration with Google, has contributed a new CFF parsing
> and hinting engine. The last few months it was my job t
Folks,
Adobe, in collaboration with Google, has contributed a new CFF parsing
and hinting engine. The last few months it was my job to fully
integrate the code into FreeType, and I'm very pleased with the
results. Here are links to the relevant blogs:
http://adobe.ly/12mJWGv
http://google
