Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.1
-
Fix Version/s: 4.2.2
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
Assignee Priority:P2
Description
The PDF in question is actually malformed, I've never seen one that has such a simple but none the less a malformed file. The offending content reads:
q1 0 0 1 0 792 cm
but should read
q 1 0 0 1 0 792 cm
The error is really simple to see but not some simple to fix. I'll have to think a little more about how to fix the error without slowing down our parser too much.
q1 0 0 1 0 792 cm
but should read
q 1 0 0 1 0 792 cm
The error is really simple to see but not some simple to fix. I'll have to think a little more about how to fix the error without slowing down our parser too much.
Activity
Patrick Corless
created issue -
Patrick Corless
made changes -
Field | Original Value | New Value |
---|---|---|
Salesforce Case | [] | |
Fix Version/s | 4.2 [ 10243 ] |
Arran Mccullough
made changes -
Salesforce Case | [5007000000E489a] |
Patrick Corless
made changes -
Assignee Priority | P2 |
Patrick Corless
made changes -
Fix Version/s | 4.2 [ 10243 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #24894 | Fri Jun 24 11:05:39 MDT 2011 | patrick.corless | |
Files Changed | ||||
MODIFY
/icepdf/trunk/icepdf/core/src/org/icepdf/core/util/Parser.java
|
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #24895 | Fri Jun 24 11:17:33 MDT 2011 | patrick.corless | |
Files Changed | ||||
MODIFY
/icepdf/trunk/icepdf/core/src/org/icepdf/core/util/Parser.java
|
Patrick Corless
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Fix Version/s | 4.2.2 [ 10265 ] | |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
I did quite a bit of research into a new Lexer for ICEpdf when writing the Type4 function lexer. I think new Lexer for the content parser would be fairly low risk, fix the issue in question and significantly speed up content parsing. As time permits I'll see if one can be created on a branch of 4.2 with the intention of a 5.0 release upon completion.