You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on #207 it isn't clear to me what is considered a potential bug vs something PdfSharp deliberately doesn't support, so apologies in advance if this behavior is expected. Hopefully this can be a quick close-won't fix in that case and the issue can serve as documentation for others who encounter this.
The text was updated successfully, but these errors were encountered:
The file is corrupted and this is not a bug in PDFsharp. In issue 207, the file is also corrupted, but PDFsharp has been updated to correct the wrong information in the PDF and read the file nevertheless.
Without PDF file, we cannot investigate what's going on. Depending on what is wrong with the PDF, there may be a way to modify PDFsharp to read it anyway.
For my understanding, what is the best way to engage on these parsing issues in a helpful way?
I completely understand the perspective that not being able to handle a corrupted file doesn't indicate a library bug, but given the absolute lawlessness of PDFs encountered out in the wild having libraries that are similarly robust to the PDF viewers customers are used to (e.g. in Chrome) is certainly handy.
I'm happy to send over weird files I encounter to help the library improve, but at the same time I don't want to bother the maintainers with yet more instances of errors you've seen before and perhaps decided explicitly not to accommodate.
Reporting an Issue Here
Expected Behavior
The PDF opens without error, or with an exception that indicates that this is something PdfSharp does not support.
The PDF
Actual Behavior
Steps to Reproduce the Behavior
If there's interest in looking into this I can share the file privately via the mechanism described here: https://github.com/empira/PDFsharp.IssueSubmissionTemplate
Based on #207 it isn't clear to me what is considered a potential bug vs something PdfSharp deliberately doesn't support, so apologies in advance if this behavior is expected. Hopefully this can be a quick close-won't fix in that case and the issue can serve as documentation for others who encounter this.
The text was updated successfully, but these errors were encountered: