Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.3, 6.3.1
-
Fix Version/s: 6.3.2
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
Support Case References:Support CAse 14374:- https://icesoft.my.salesforce.com/5000g00001wGfsT?srPos=0&srKp=500
Description
The file in question is quite interesting in that the results of the text extraction change given the order the pages are extracted. Further investigation is needed.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Added code to ensure we undue the previous xobject space from the text objects before applying the new space. This insures the glyphs will be in the correct location when the sorting takes place.
Marking as fixed.
Show
Patrick Corless
added a comment - Added code to ensure we undue the previous xobject space from the text objects before applying the new space. This insures the glyphs will be in the correct location when the sorting takes place.
Marking as fixed.
Pages 16 and 17 share content via an xobject that represents the small table "DESIGN FAILURE REATE (FIT)". When page 17 is loaded on it's own the content is correctly converted to the page's page space and the page text extraction algorithm correctly sort the page content.
When 16 and 17 are loaded in sequence the table is first loaded for page 16 and the text sprites are updated to that coordinate space. When 17 is loaded we have code that should update the table's xobject text sprites but that doesn't appear to be happening or is happening incorrectly. The code wasn't written with this corner case in mind, we'd need to first back out any transform and apply the new one.