Client's Hinting Problem

Design
1

A client is having a problem regarding hinting in PC Windows, in a Dell Monitor, Windows 11Pro, Edge, etc…

Current hinting workflow:

  • Draw shapes with correct nodes and handles
  • Use standard paths direction
  • Add Family Aligment Zones in Family
  • Add TTF Zones and Stems in each Master
  • Add TTFAutohint Options in each Export (
    • x-height snaping exceptions: 10,13,15
    • Fallbackstem with (accordin to each stem)
    • hinting limit 50, maximum range 48
    • Grayscale: Quantized, GDI: Strong, DW: Quantized
  • Export individuals as .ttf (autohint)
  • Use FontSpector or Fontbakery to solve any issue
  • Use latest ttfauthint in terminal with standard settings in each .ttf (does this override all the previous settings I made in glyphs? should I use one or the other?)
  • Use woff2_compresion in terminal

The typeface looks perfect in 7 screens that I’ve tested in windows, one old as 2006. But I couldn’t replicate the error. One important thing is that the vertical metrics of each weight are different due to optical compensation, but the problem isn’t when the font is used mixed… so I guess that this shouldn’t affect rendering.

Here is a few of the client’s problem:

As you can see here, the “H” is lower and the top of the “A” stands out a lot in several sizes

image (26)
image (26)579×316 15.2 KB

Here all the letters jump a lot (what?!?!)

image (27)
image (27)351×193 5.23 KB

Here as well. the letters jump a lot (what?!?!)

img1
img1617×214 23.4 KB

——————————————————————————————————————————

And, here is what I see in a Dell screen from 2006 (for example):

imgxxx
imgxxx650×805 147 KB

Any idea what could the problem be or how to fix it?

I’m doing Rainer’s hinting course next month (fortunately).

Thanks a bunch,
Fer

2
  • Raise hinting limit to something higher like 70.
  • Double check your overshoots. Make them as consistent as possible.
  • consider double checking your path directions
  • use --reference (with family alignment zones script)

Are you sure this is the TTF and not the CFF that the client installed??

The internal ttfautohint should suffice.

You can send me the files if you like and I’ll have a look.

1 Like
3

All the zone settings in Glyphs (family and TTFZones) are not used by ttfAutohint.
Could you send me the .glyphs and the .ttf file?

1 Like
4

Will send them, thanks a lot to both!

5

As fare as I can see, the fonts look very good on windows 11. Is there chance to see that html page?

6

One thing I just realized that could contribute is the screen scaling. It didn’t cause problems for me, but it might be worth checking:

Bildschirmfoto 2026-05-01 um 18.59.19
Bildschirmfoto 2026-05-01 um 18.59.191268×1384 19.2 KB

7

Hey Goerge, I’ve sent the website privately.
I’ll let them know to check screen scaling.

Thanks!!!

8

I think I achieved a good result with the TTF reference (TT equivalent of family alignment zones). Screen scaling cannot cause the differences between overshoots.

9

My thinking wars that ttfAutohint is very size dependent, it might behave strangely in certain in between sizes.