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

3.2.0 autohinting logic still not right? #866

Closed
simoncozens opened this issue Mar 15, 2022 · 4 comments · Fixed by #873
Closed

3.2.0 autohinting logic still not right? #866

simoncozens opened this issue Mar 15, 2022 · 4 comments · Fixed by #873

Comments

@simoncozens
Copy link
Contributor

@marekjez86 reports that in 3.2.0, fontmake is now producing autohinted fonts by default, while 3.1.3 does not. I'm having trouble reproducing, but there it is.

@marekjez86
Copy link
Contributor

marekjez86 commented Mar 15, 2022

My favorite options would be to produce 1. unhinted only (overriding the source) 2. hinted only (also overriding the source) or 3. BOTH :-) [because I need both] ... Note that I have lived so far with 1. (unhinted only) because I use ttfautohint when I need to publish hinted versions

@anthrotype
Copy link
Member

anthrotype commented Apr 6, 2022

I believe this is a feature, not a bug, added with #850

basically if the font has a TTFAutohtint options custom parameter, fontmake will use that with ttfautohint.

All the sources that @marekjez86 linked above contain that custom parameter so they will produce autohinted fonts.

Maybe we need an additional option to skip autohinting no matter the presence of TTFAutohtint options custom parameter in the source.

@anthrotype
Copy link
Member

@marekjez86 I added a --no-autohint option that disables ttfautohint, overriding the custom parameter

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

Successfully merging a pull request may close this issue.

3 participants