Bug 162575 - RFE: xpdf 2 does not understand PDF version 1.5
RFE: xpdf 2 does not understand PDF version 1.5
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: xpdf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-07-06 09:49 EDT by Andrew Gormanly
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHEL4
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-05-24 08:52:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Gormanly 2005-07-06 09:49:46 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.7.8-

Description of problem:
When opening some PDF files with xpdf 2.02, newer ones cause the error message:

Error: PDF version 1.5 -- xpdf supports version 1.4 (continuing anyway)

to be displayed.  It seems that this version of xpdf does not properly understand PDF version 1.5, only 1.4 and lower.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. View a PDF 1.5 document

Actual Results:  Error message, sometimes bits of document not displayed.

Expected Results:  RHEL3 should include a PDF viewer capable of rendering these documents.

Additional info:

The version of acroread in RHEL3 has the same limitation; xpdf 3.0 does not have this issue, neither does Adobe Reader 7.0

The example URI above is the one that gave me the error message today, but there have been many others recently, and some were missing chunks (mostly images).
Comment 1 Ngo Than 2006-05-24 08:52:00 EDT
yes, updating to new xpdf 3.0 should resolve this problem. RHEL4 already 
includes the new xdpf-3.

Note You need to log in before you can comment on or make changes to this bug.