-
-
Notifications
You must be signed in to change notification settings - Fork 605
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
Proposal: Eliminate otf builds #267
Comments
So, I have been using the OTF hack and did not notice. And the Arch community seems to prefer TTF over OTF since the TTF package is in extra ( https://www.archlinux.org/packages/extra/any/ttf-hack/ ) while the OTF is just in AUR. So I don't mind dropping / deprecating the OTF Arch package. |
what happens to users who installed with a deprecated package on Arch? Possible to forward in some way to another package? |
We can add a warning message output during install that points them to the ttf package |
Thanks @coderbyheart |
Will eliminate otf builds as of v3.0 release |
Added a note to otf-hack to switch to ttf-hack. |
@coderbyheart thank you! appreciate your help! |
We are considering the elimination of the otf builds as of the v3.0 release of the Hack fonts. If this matters to you, here's your chance to weigh in before we make the decision.
In my view, otf offers the potential benefit of somewhat smaller binary file sizes. I cannot come up with any other significant benefits of this build type for our fonts.
The downside of the otf builds are that the hint sets in the v2.x releases (automated in all v2.x releases in the FontLab Studio editor) are not ideal and there is not an impetus to work on them given the relative lack of benefit vs ttf files. With the move to a fully scripted build approach with OS tools, we would need to identify a new way to autohint the otf builds and then attempt to optimize those hints for platforms that use them. For platforms where the instruction sets/hints are important at smaller text sizes (Linux and Windows) the manual instructions on our ttf files are much more optimal, and with planned work in the v3.x releases will improve further, than those in the otf builds and this will make a difference at the sizes used for source code.
The text was updated successfully, but these errors were encountered: