the bug has been opened on https://bugs.launchpad.net/bugs/321720
"Evince cannot read the pdf format created with Adobe 8.1.3
This results in the file displaying the below message. Presumably, this is the message that Adobe Reader 8.1.3 and higher will save into the pdf files for readers that are only familiar with older pdf formats. This kind of monopolizing is typical of closed source programs.
To view the full contents of this document, you need a later version of the PDF viewer. You can upgrade
to the latest version of Adobe Reader from www.adobe.com/products/acrobat/readstep2.html
For further support, go to www.adobe.com/support/products/acrreader.html
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."
(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. ***
*** This bug has been marked as a duplicate of bug 14265 ***