-
-
Notifications
You must be signed in to change notification settings - Fork 686
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
Better error message for the non-support of WOFF fonts #1259
Comments
Hello! Thank you for reporting this issue.
Right, it’s even already supported in the
It’s a bit more complicated than that: this warning is displayed when loading all the different fonts if one But the message of the exception is displayed when you launch WeasyPrint with the A clean way to do this would be to store the exceptions in a list and display them after the warning message (as warning messages) when they all fail. Now that WOFF(2) fonts are supported, I’m not sure that it’s really useful to have this feature. Letting developers know that there’s a |
OK, thanks for all this information. The I'll try the @liZe Just to know, when is it planned to use this branch as the new |
Hi @vpoulailleau! Please have a look at #1232 (comment) :) |
Hi @grewn0uille! Thanks for the good news and for WeasyPrint/pydf! |
Thanks for WeasyPrint, I love it!
I lost 1 hour trying to use my
@font-face
and trying several options (local files, remote files, absolute and relative paths…). I finally discovered that WOFF and WOFF2 fonts are not supported (18010a1) and this is totally OK, I know you're working on removal of cairo and better support.In the meantime, I think that the following error message:
may be replaced with
I saw an exception here: https://github.com/Kozea/WeasyPrint/blob/master/weasyprint/fonts.py#L357
Maybe it's possible to catch it somewhere and provide a clearer message?
What do you think? (You may answer that I'll just have to wait for the support of WOFF and WOFF2 fonts 😉)
The text was updated successfully, but these errors were encountered: