-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Support for OTF fonts #3030
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
Comments
Duplicate of #2276. I agree, this would be a really nice feature. I won't have the time to implement such complex features myself. I will definitively merge a pull request from the community, though. |
Thanks for the response! Separately, though, there is the issue of some TTFs rendering in the same "curse chars" way. I have many, and even at least one official MS font (ahronbd.ttf), that are coming up wrong. Is this something to look into? Perhaps they are OTF in disguise? They do all work in normal desktop use. |
AFAIK, some features of TTF are not supported, so this might very well be the reason. |
This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant. |
I see that this has come up here and there, but OTF support would be a hugely welcome addition. Most of the fonts I use, for design and such, are in OTF format. I've tried converting OTF fonts to TTF using FontLab 7 (to both OpenType TTF and to Variable TTF formats) to no avail. I've also tried numerous online services. They all produce the same
!"##$%&$'#(
for "Hello World" at https://sphilee.github.io/jsPDF-CustomFonts-support/. They DO seem to have the font weight, though.Some TTFs do work, but many of the selections I've been making do not. So perhaps there's something in the TTF spec that isn't being handled? Or designers are exporting non-compliant fonts?
So this is a request for OTF support, and perhaps full TTF support to boot. Let me know if a sample OTF and/or TTF font that doesn't work would be helpful.
The text was updated successfully, but these errors were encountered: