Re: Progress update on adjustments database branch.

[Brad Neimann]

Hi all,

On this issue, I’ve noticed a particularly egregious example in the past few days: around 20 ppem, with autohinting enabled, ⟨ñ⟩ in Noto Sans Regular consistently renders with a horizontal bar, so as to be indistinguishable from ⟨n̄⟩. As Werner mentioned some time ago, this particular character may not be a huge problem in practise, but it would be nice to get this fixed nonetheles. I note especially that --- at least on my machine --- popular sites like Wikipedia and Reddit render in precisely this font at that size.

(This issue actually has an interesting story behind it... after getting fed up with scaling issues in Emacs with my HiDPI laptop screen, I decided to try out Wayland. Indeed, Wayland fixed all my rendering issues, allowing my lower-resolution external monitors to be rendered at their correct resolution rather than being downscaled 2×. But that also meant the hinter finally needed to do some actual work, meaning this issue suddenly became obvious. I suspect this issue also indicates that, for some reason, my computer has been autohinting everything... it is a testament to the quality of Freetype that I never noticed this before!)

Regards,
Brad

On 29/6/23 12:14, Craig White wrote:

Thanks for the feedback on the algorithm!

I'm trying to use ftview to get some more sample images, but I can't find the image produced by the "print png" feature.  Where is it saved?

In the benchmark file, is a higher number better or worse?  In either case, the performance hasn't changed much.

On Tue, Jun 20, 2023 at 10:38 AM Ahmet Göksu <ahmet@goksu.in> wrote:

Hi, I think this benchmark page in attachment is what you wanted to.

Made baseline in my branch, fetched and merged with craigs branch, made benchmark.

Best,

Goksu

goksu.in

On 20 Jun 2023 07:18 +0300, Werner LEMBERG <wl@gnu.org>, wrote:

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

Yes, please try that.

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

Exactly.


Werner