On Fri, 18 Aug 2023 11:02:49 + (UTC), Werner LEMBERG wrote:
> To summarize: Benchmark comparisons only work if there is a sound
> mathematical foundation to reduce the noise.
I am probably not qualified, but I am following the discussion for some
time. And I think there is a problem with the
Hİ,
I have edited the code aligning with the Hin-Tak’s suggestion. Here is the two
results pages, also pushed on gitlab.
Best,
Goksu
goksu.in
On 18 Aug 2023 14:02 +0300, Werner LEMBERG , wrote:
> > > What happens if you use, say, `-c 10', just running the
> > > `Get_Char_Index` test? Are the
Hi,
Yesterday's opentype font meeting touched upon hinting and ttfautohint briefly.
I see the infinality patch is already gone (next release, 2.13.2 I guess - bits
of it was removed in 2.13.1 already). Question is, does its removal impact the
functionality of ttfautohint? Are we getting into a
>> What happens if you use, say, `-c 10', just running the
>> `Get_Char_Index` test? Are the percental timing differences then
>> still that large?
> Actually Get_Char_Index, on the three pages I have sent in the
> prev. mail, is higher than 6% only 4 times out of 15 total. (which is
> seem on
Hi,
The approach we initially took was, in fact, based on the principle of the
interquartile range (IQR) – a method that excludes outliers by determining the
range between the first and third quartiles. However, I understand from your
feedback that directly focusing on the median and quantiles
On Friday, 18 August 2023 at 00:21:41 BST, Ahmet Göksu
wrote:
> about outliers, i splitted every tests into chuncks that is sized 100. Made
> IQR calculations and calculated average time on valid chunks. you can find
> the result in the attachment also pushed to gitlab.
> also,
> Yesterday's opentype font meeting touched upon hinting and
> ttfautohint briefly. I see the infinality patch is already gone
> (next release, 2.13.2 I guess - bits of it was removed in 2.13.1
> already). Question is, does its removal impact the functionality of
> ttfautohint?
No.
> Are we
>> It's not clear what you are actually asking. ttfautohint is an
>> incarnation of FreeType's auto-hinter, translated into TrueType
>> bytecode, more or less. This is not related to interpreting
>> bytecode.
>
> But does it contain hidden assumptions about how bytecodes are
> interpreted (by
On Friday, 18 August 2023 at 22:27:26 BST, Werner LEMBERG wrote:
> > Are we getting into a situation where ttfautohint is hinting for the
> > (limited) "good enough" light hinting model of recent freetype?
> It's not clear what you are actually asking. ttfautohint is an
> incarnation of
