Re: [ft-devel] [GSoC] CID font support, and others

[Ewald Hew]

> I suggest that you add tracing messages.  For example, the attached
> excerpt from a log file shows what the auto-hinter emits for glyph
> index 2 of the font `c059013l.pfb' (URW Century Schoolbook L Roman
> version 1.06).  I called
>
>   FT2_DEBUG=any:7 ftview 20 c059013l.pfb &> c059013l.log
>
> then pressing key `f' to enforce full auto-hinting.
>
> As you can see, it is quite detailed.
> Table of points:
> Table of horizontal segments:
> Table of vertical segments:
> Table of horizontal edges (1px=48.13u, 10u=0.21px):
> Table of vertical edges (1px=50.00u, 10u=0.20px):

These would be really useful, I guess I'll start by adding something
of this sort to the Adobe hinter too. I somehow hadn't seen these
tables before, despite running with "any:7" most of the time.

> A starting point might be running ftbench with a profiler.  I
> sometimes use valgrind for that:
>
>   valgrind --tool=callgrind ...
>
> The resulting data can then be visualized with `kcachegrind'.  There
> are certainly other profiling tools that you might find helpful.

Thanks for the advice!

Ewald