Summary: | PDF v1.7 asks to upgrade Adobe Reader | ||
---|---|---|---|
Product: | poppler | Reporter: | Sebastien Bacher <seb128> |
Component: | general | Assignee: | poppler-bugs <poppler-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | carlosgc, eugen.dedu, martin, murrayc |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Sebastien Bacher
2009-03-05 06:05:01 UTC
(In reply to comment #0) > This is a problem on all pdf readers, except newer adobe products. I have > checked google's pdf reader, evince and foxit, which all seem to not work. > However adobe pdf reader 9 reads this file." Because it uses (more or less proprietary) technology from Adobe; the content of the PDF is what is displayed by evince etc. What AR shows is something quite different... The file at http://eugen.dedu.free.fr/a.pdf shows: snoopy:~$ file a.pdf a.pdf: PDF document, version 1.7 Upon opening with evince 2.28.2 (using libpoppler 0.12.2 cairo), a dialog box appears "Password required... The document is locked and requires a password before it can be opened." pdfcrack says it is not encrypted: snoopy:~$ pdfcrack a.pdf Error: Encryption not detected (is the document password protected?) So I suppose the problem is that the file is pdf v1.7. Is there a method to see these files on gnu/linux...? (In reply to comment #2) > So I suppose the problem is that the file is pdf v1.7. No. The "problem" is that this file uses an AcroForm (see section 12.7.2 of the ISO PDF Standard). And it uses Adobe LiveCycle. > Is there a method to see these files on gnu/linux...? Not yet. Your patch is very welcome. Please, do not hijack bugs unless you are sure the root cause of the bug is the same. *** Bug 28153 has been marked as a duplicate of this bug. *** Basically the PDF uses JavaScript to change which contents to render and that's why we get the plain "dumb" text |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.