Bug 106791

Summary: Several fields are not displayed at all in a PDF form
Product: poppler Reporter: Germán Poo-Caamaño <gpoo+bfdo>
Component: generalAssignee: poppler-bugs <poppler-bugs>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: PDF test case
Screenshot of Evince and Foxit side-by-side

Description Germán Poo-Caamaño 2018-06-03 02:43:18 UTC 
Created attachment 139980 [details]
PDF test case

As reported in https://gitlab.gnome.org/GNOME/evince/issues/395

"Attached is a PDF evince cannot display correctly and a screenshot of evince and Foxit Reader displaying the same file. The difference is easy to spot."
Comment 1 Germán Poo-Caamaño 2018-06-03 02:47:41 UTC 
Created attachment 139981 [details]
Screenshot of Evince and Foxit side-by-side

Screenshot that shows the differences between Evince and Foxit to render the document.

Even though the versions displayed in the screenshot are old, the issue stays the same. It is reproducible with pdftocairo and pdftoppm.

For both, the output in the console is:

Syntax Error: End of file inside array
Syntax Error: Leftover args in content stream


The PDF itself seems to be broken, too.  At least, Acroread complains:

"An error exists on this page. Acrobat may not display the page correctly.
 Please contact the person who created the PDF document to correct the
 problem."

Nevertheless, Acroread renders the same as Foxit, and some form fields are editable.
Comment 2 GitLab Migration User 2018-08-21 10:41:09 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/323.

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.