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
Zapfino typface (font) not correctly rendered #50
Comments
WeasyPrint uses Pango to render text. Based on the images, some font feature seems not to be enabled but I don’t know what it is. Are you sure this is even the same font? Try something like this:
Do you get an image? What does it look like? In any case, I’m afraid WeasyPrint can not do much about it and this is all in Pango. |
Thanks for the quick reply.
produces an image that looks like the second image in my bug report above. Should I open a bug for Pango instead? |
I don’t know about a bug, but I’d write on the Pango mailing list. |
Thanks again. Will contact Pango folks one way or another :) |
https://bugzilla.gnome.org/show_bug.cgi?id=738505 might be relevant, but I don’t know if it’s in a Pango release yet. We’d want some conditional code to only use it when available. |
On OS X 10.6.8, Firefox, TextEdit and others render the word "Zapfino" in the typeface Zapfino as in the first attached image. However, WeasyPrint renders it as in the second attached image.
My understanding is that in this particular case, Firefox, TextEdit, etc, are honouring Zapf's intentions, and that WeasyPrint is not.
The text was updated successfully, but these errors were encountered: