Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[otfautohint] will not hint if zones are too close #1770

Open
frankrolf opened this issue Dec 19, 2024 · 0 comments
Open

[otfautohint] will not hint if zones are too close #1770

frankrolf opened this issue Dec 19, 2024 · 0 comments

Comments

@frankrolf
Copy link
Member

frankrolf commented Dec 19, 2024

I got a report

afdko.otfautohint.fdTools.FontInfoParseError: In FDDict FDArray[0]. The top of zone AscenderHeight at 698 is within the min 
separation limit (3 units) of zone FigHeight with the bottom at 700.

Reading the T1 Specification (page 37, chapter 5), I confirm that otfautohint is correct:
image

This is confusing since psautohint (and autohint before that) did not enforce this (I learned that alignment zones need to have a minimum distance of 1 unit + BlueFuzz). Especially in UFOs which have previously been edited with psautohint, we now produce a fragmentation of hinted (untouched) and unhinted (touched and their dependent components) glyphs - which only surfaces once we run makeotf (lots of “unhinted” output, but without an explanation as to why).

  • What tests need to be conducted to understand if the zone distance 3 really is crucial to rasterization?
  • Might there have been an update to the spec where this distance was decreased? (might well be that autohint got it wrong in the first place)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant