Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0
-
Fix Version/s: 4.0.1
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
ICEsoft Forum Reference:
Description
The PDF in question has several occurences of a font name that is only contains a subtype definition and not the valid font name. When org.icepdf.core.pobjects.fonts.ofont.Font comes accross the emty font name a illegal state exception comes out of the java.awt.Font class which causes the page loading to fail.
The lack of a font name is probably against the PDF spec but either way its pretty easy to fix. When we get into this very rare state of an empty font name we can default to serif font which will keep the rendering going.
The lack of a font name is probably against the PDF spec but either way its pretty easy to fix. When we get into this very rare state of an empty font name we can default to serif font which will keep the rendering going.
Activity
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #20478 | Thu Feb 04 08:36:22 MST 2010 | patrick.corless | |
Files Changed | ||||
MODIFY
/icepdf/trunk/icepdf/core/src/org/icepdf/core/pobjects/fonts/ofont/Font.java
|
Patrick Corless
created issue -
Patrick Corless
made changes -
Field | Original Value | New Value |
---|---|---|
Salesforce Case | [] | |
Fix Version/s | 4.0.1 [ 10228 ] |
Patrick Corless
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Checked in the upadated font substitution logic to always sub a serif font if ther was a problem derifing a java.awt.Font.