No, only parameter that given to ftbench.o is -c 50 for now. but i will do by 
“-r 1” parameter.

so i need to pass additional parameters from command line first. then, print it 
to benchmark page as well as commit id and date.

Best,
Goksu
goksu.in
On 19 Jun 2023 11:50 PM +0300, Werner LEMBERG <w...@gnu.org>, wrote:
>
> > your repo is updated 2 weeks ago. we can use ftbench to compare
> > differences. yet, benchmark is in attachments.
>
> Thanks, but I'm not sure that it actually tests what Craig is
> developing: AFAICS, the fonts you are benchmarking contain TrueType
> bytecode, which by default is not handled by the auto-hinter. To test
> the auto-hinting mode, you have to set the `-r 1` option of `ftbench`
> to actually test 'light' hinting, i.e., enforcing auto-hinting even if
> the fonts contain TrueType bytecode. Did you do that?
>
> So I have another request besides displaying the git commit IDs:
> Please display the arguments passed to `ftbench` on the HTML page so
> that it we exactly know what `ftbench` is actually testing.
>
>
> Werner

Reply via email to