-
Notifications
You must be signed in to change notification settings - Fork 23
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
Feature request: Add support for Bitmap strikes #16
Comments
There is a tool to do this: I'm going to convert Fairfax, but it had a segmentation fault. Donno why. |
Thank you for letting me know @diaowinner |
Also, version 2 can export to otb (OpenType Bitmap), which is much better supported than ttf with bitmap strikes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for this lovely piece of software!
As you may well be aware, rendering of pixel-based vector fonts on Windows is a mess because of ClearType:
However there is a workaround possible by including bitmap strikes (documented here: https://int10h.org/blog/2016/01/windows-cleartype-truetype-fonts-embedded-bitmaps).
Currently the author of the blogpost/fonts in question proposes a workflow including closed source software "Fony" in addition to bitsnpicas, but it would be ideal if this could all be handled by one piece of software!
Thanks for considering.
The text was updated successfully, but these errors were encountered: