>> Ewald, have you already done some benchmarks?
>
> I finally got the freetype2-demos to work with callgrind, but many
> of the calls have no debug label. In fact, it seems like the demos
> are linking to my system-provided libfreetype instead of the git
> devel one, hence no debug
Thanks Dave for the helpful explanation!
>> I suppose you could disable the use of the initial hintmap for Type 1
>> charstrings only.
>
> If I understand correctly, this is what Ewald started with, and he got
> bad results...
No, it was always enabled, but built wrongly as we don't have all the
Hello Dave,
thanks for your detailed response.
> The initial hintmap feature is relatively new in Adobe's CFF
> rasterizers. It does not exist in CoolType (the rasterizer used in
> Acrobat). CoolType uses an interpreter that handles either Type 1
> or CFF in one pass. But because it does
> Humm. I don't see them in git.
Oops! Now pushed.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
Finally got round to build the binary - just get FontVal-2.1.0-py-bin-net4.zip
from
https://sourceforge.net/projects/hp-pxl-jetready/files/Microsoft%20Font%20Validator/
I recovered the test results I did almost a month ago from my old computer,
on all fedora 26 shipped fonts - will upload at
On Mon, Aug 14, 2017 at 11:52 PM, Werner LEMBERG wrote:
> > Check the branch now:
> > https://github.com/behdad/freetype/commit/40112725e9041a5e3f2878e71bdd08
> 249beaa743
> >
> > I think this is good enough to go in. What do you think?
>
> Committed, thanks, with some additional
> Check the branch now:
> https://github.com/behdad/freetype/commit/40112725e9041a5e3f2878e71bdd08249beaa743
>
> I think this is good enough to go in. What do you think?
Committed, thanks, with some additional checks and minor code changes.
Please check.
Werner