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

Font Hinting #30

Closed
tocsoft opened this issue Jun 4, 2017 · 5 comments
Closed

Font Hinting #30

tocsoft opened this issue Jun 4, 2017 · 5 comments

Comments

@tocsoft
Copy link
Member

tocsoft commented Jun 4, 2017

Provide a mechanism for processing the font hints.

@JimBobSquarePants
Copy link
Member

Some further information.

We should be able to port an implementation from https://github.com/LayoutFarm/Typography (MIT)

They use the following HintTechnique enum to describe hinting.

Interpreting the hinting instructions appears to be handled by TrueTypeInterpreter

The underlying implementation of which is a port from SharpFont

@JimBobSquarePants
Copy link
Member

Initial support for this has been implemented in #210 We still need to implement hinting adjustments for specific fonts a la FreeType and do optimizations.

@JimBobSquarePants
Copy link
Member

JimBobSquarePants commented Mar 28, 2022

@tocsoft Do you think we should close this now? I don't think Freetype don't actually use those adjustments anymore. They're for the old version.

@tocsoft
Copy link
Member Author

tocsoft commented Mar 28, 2022

Yeah we probably should close this one as we have hinting now... I think anything else now should new issues/bugs rather than initial implementation.

The only thing we might still need to consider is if we should enable it by default or not. That decision probably requires a whole suite of samples being generated with a large variety of settings and fonts and comparing outputs. If at a significantly high percentage mark we decide we don't produce worse results and on average we generally produce better with it on rather than off then we should turn it on by default.. in one of the 2 modes anyway.

@JimBobSquarePants
Copy link
Member

If at a significantly high percentage mark we decide we don't produce worse results and on average we generally produce better with it on rather than off then we should turn it on by default.. in one of the 2 modes anyway.

Yeah. Good idea. I've been happy with the improvements I've seen following my recent changes but you never know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants