-
-
Notifications
You must be signed in to change notification settings - Fork 704
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
Line breaking simplification breaks PDF RFC generation #973
Comments
Forgot to mention, in case it matters, this is with python3.7. |
The xml provided in the original bug report won't be helpful in tracking down the bug. I'm providing the HTML and 2 css snippets that are handed to WeasyPrint as a result of that XML: https://tools.ietf.org/src/xml2rfc/issue/weasyprint/973/sample.html Best regards, |
@levkowetz -- feeding the html and css to my WeasyPrint v50 renders without problem. Using v49 I see no difference in the PDFs. So what's the actual error? Could you provide WeasyPrint's stack trace? Since you mention f1b1d14 I guess it's a crash with an |
Here's the stack trace from the original bug reporter. I was able to replicate this (using his xml and xml2rfc): Traceback (most recent call last): |
Looks like you are correct. I can also confirm that with the changes from #956 the problem does not happen anymore. |
No worries -- WeasyPrint will survive without bug fixes until 3rd of November. All the best for PyConFr! |
This is a bug I'm forwarding on behalf of a Debian user:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942366
The xml2rfc program uses WeasyPrint to generate PDF versions of IETF RFCs. Up to WeasyPrint version 49, it worked. In version 50, it does not. I bisected the code and it starts failing after the line breaking redesign commit (f1b1d14).
There is an attachment in the Debian bug that shows the exact error. It also gives instructions on replicating the bug which worked for me.
I don't believe this was meant to be an API breaking change, so I think it's reasonably something that should be addressed in WeasyPrint.
Scott K
The text was updated successfully, but these errors were encountered: