Details
-
Type:
Bug
-
Status: Reopened
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Any
-
Support Case References:Support Case 14054:- https://icesoft.my.salesforce.com/5007000001iL0hi
Description
A community member has submitted two files, one that is missing some text the other has been corrected by Acrobat and renders correctly in the viewer.
The problem is related to cm that is inside of a text block which is technically illegal. The correct file actually moves the transform out of the text block. The main issue however is that over the years we have had numerous examples where this transform is needed to render the text. In this particular case the transform is causing the problem and should be ignored. I'll need to fire up a full qa run to see what kind of trouble we're looking at.
The problem is related to cm that is inside of a text block which is technically illegal. The correct file actually moves the transform out of the text block. The main issue however is that over the years we have had numerous examples where this transform is needed to render the text. In this particular case the transform is causing the problem and should be ignored. I'll need to fire up a full qa run to see what kind of trouble we're looking at.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Marking as fixed.
Show
Patrick Corless
added a comment - Marking as fixed.
Given the thousands of PDF we have in our QA content set surprisingly we only have two files that have this odd syntax. And of course there is nothing in the spec about it.
The cm in needed for PDF A and it has very simple transform with only a translation. PDF B on the other hand has a very strange transform, huge scale and translations that don't jive with the rest of the file.
For the time being we'll ignore the out of place transform with a simple scale check. Perhaps one day we can check against the pdf's coordinate bounds to see if a transform is a mistake by the encoder or not.
Show
Patrick Corless
added a comment - Given the thousands of PDF we have in our QA content set surprisingly we only have two files that have this odd syntax. And of course there is nothing in the spec about it.
The cm in needed for PDF A and it has very simple transform with only a translation. PDF B on the other hand has a very strange transform, huge scale and translations that don't jive with the rest of the file.
For the time being we'll ignore the out of place transform with a simple scale check. Perhaps one day we can check against the pdf's coordinate bounds to see if a transform is a mistake by the encoder or not.
Client would like to know if this can be applied to the 6.2 branch as their client has a JDK6 limitation. Please comment on this JIra as to complexity and if this is possible (timeline?). Thanks.