ThomasHoevel
ThomasHoevel
Changing the properties of a `PdfTextField` does not change the representation of this field in the PDF file. This is by design. It is up to your code to change...
People who used PDFsharp 1.5 should try the GDI build of PDFsharp 6.1 to get the same functionality. That much can be said without trying your code.
As far as I can tell, the image that causes this issue is corrupted: There is one file header that indicates that there is only one component (meaning grayscale image)...
PDFsharp does not (yet) support LTR languages, Japanese, Chinese, Korean, ... Issue here is that the font does not contain 0xE0100 and PDFsharp did not handle this correctly. Beginning with...
I think that supporting `AddImage(Stream stream)` is a bad idea. I think that supporting `AddImage(byte[] bytes)` could be a good idea.
Other folks simply attach the ZIP files to their issue posts on GitHub.
I downloaded the file. Nothing obviously wrong with the PDF. It probably takes a few hours with the debugger to understand why the two pages are missing.
The PDF specification reads: > Together, the combination of an object number and a generation number shall uniquely identify an indirect object. The file with the issue has several duplicated...
@packdat I'll have a look when you provide a PR. I thought the parser was using the newest objects as tables where read from rear to front, starting with the...
The fix by packdat should be included in version 6.1.0 coming later this year or next year. Thanks for the feedback. Issue still exists with version 6.0.0.