-
Notifications
You must be signed in to change notification settings - Fork 153
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
Problem parsing a certain pdf #15
Comments
Also incase it helps, just found a slightly older version of the same file which DOES work. I can't spot any difference, only 9 bytes difference between the two! |
Hi Stefan, Thank you very much for opening this issue and helping make the combine_pdf gem even better. I had a quick look at the issue and it seems that the PDF file you showed me uses the wrong version identifier. The PDF file states PDF version 1.3 but uses features introduced only in PDF version 1.5 ... ... for performance reasons, the parser didn't check if Object Streams existed in this PDF file (following the rule that in version 1.3 they shouldn't exist) and didn't attempt to extract the data from them. I updated the parser so that it will always search for Object Streams and this resolved the issue on my system. Please install version 0.1.18. It should solve the issue for you. Again, thanks you for opening this issue. |
Yep, works like a charm now. Thanks for the amazingly quick fix! |
Hi guys, See this issue again on v0.2.31 when trying to combine a pdf generated by CombinePDF.
Do I have to update something on system? Thank you. |
Hi @andela-echigbo , Thanks for posting. I'm assuming the error you're posting shows I'm not sure, but in my head this is expected behavior. Please let me know if you're experiencing this as an error or a warning... Let me explain why I suspect you're referencing an expected behavior when importing CombinePDF data. PDFs have, sometimes, In CombinePDF, the NULL object is object These NULL objects are (often, but depending on the PDF specification version) marked by a reference to a non-existing object (which, according to the specification, faults to The final value caused by this "broken" reference is HOWEVER, this is not always the case. Different PDF authoring systems designate different objects for the NULL object (or they use the |
Yes, you're right @boazsegev, it's a warning and things still works anyways. I'm sorry I didn't state that. |
Hi, I'm getting an error when trying to load the pdf data for a certain pdf:
https://docs.google.com/file/d/0B4AGXAJrQz1RNE5OZHFTdWIycHc/edit?pli=1
Using ruby 2.1.5. It's working for every PDF I've tried except this one.. also, looking through issues it's potentially related to #6
The text was updated successfully, but these errors were encountered: