Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.0.5
-
Fix Version/s: 6.0
-
Component/s: Core/Parsing, Imaging
-
Labels:None
-
Environment:All
-
Salesforce Case Reference:
Description
With the customer provided PDF file, the images in the PDF are rendered at a 45 degree angle on the page.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Salesforce Case Reference | 5007000000ZvVSYAA3 |
| Fix Version/s | 5.1 [ 10675 ] |
| Fix Version/s | 5.2 [ 10970 ] | |
| Fix Version/s | 5.1 [ 10675 ] |
| Component/s | Imaging [ 10970 ] |
It turns out the water mark cm transformation is what was exposing the rotation issue and bug in our form handling. PDF renders correctly now.
Show
Patrick Corless
added a comment - It turns out the water mark cm transformation is what was exposing the rotation issue and bug in our form handling. PDF renders correctly now.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Marking as closed
Show
Patrick Corless
added a comment - Marking as closed
| Status | Resolved [ 5 ] | Closed [ 6 ] |
This is a very interesting one off PDF that shows an implementation issue with how we handle the saving of a graphic state before we process a form and after. The issue is that when we set the save/restore we are doing the same function as a regular q/Q. I think this is incorrect, what we really want is to save the graphics state in it's entirety and restore it after the forms is processed, very similar to what we do when working with the Java2D Graphics object.
The assumption seems to hold water and the PDF now renders correctly.