Closed diegozea closed 1 year ago
The file is corrupt. The PDF file must start with %PDF and end with %%EOF. While some readers take a lenient stand on it, one cannot say that is the right approach. Anyway I fixed the file and uploading here for reference. fixed.pdf
Thank you so much for the quick answer. I am having this error with the 75% of my files. Would it be possible to have some keyword argument for allowing parsing this kind of files? Something like permisive=true
, but being false
by default?
These files are not according to the PDF spec. So technically, the behavior of a parser on corrupt files cannot be guaranteed and should not be fixed in a hurry. While I will keep in mind to update the parser to handle some bad files, I cannot make it a guranteed feature in the product. For now you can remove the bad MIME corruptions in the file manually and work with them.
Can be done easily with a binary preserving text editor like vi or emacs on Unix or Linux.
Thank you very much! There is no hurry at all :D
Hi! I found the
Unexpected character
error while parsing many of my PDFs. Here is one example of a PDF giving me that error: https://drive.google.com/file/d/1YXdN7TfwK87_5ekbUElYRFOkVLifKj1F/view?usp=sharingMy system is:
I really appreciate any help you can provide.
Best regards,