Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.2.1
-
Fix Version/s: 4.2.2
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
ICEsoft Forum Reference:
-
Workaround Exists:Yes
-
Workaround Description:Use page.getViewText() instead of page.getText() which insures page is fully parse before text is extracted.
Description
A forum user has identified a bug with missing text when calling page.getText(). This method is used in the RI for the TextExtractionTask, it turns out that the "optimized" text extraction call is not initializing PDF XForm object and thus missing quite a bit of content during the extraction.
The Content parser method parseTextBlocks() needs to be updated to insure the xform objects are correctly initalizied and parsed.
The Content parser method parseTextBlocks() needs to be updated to insure the xform objects are correctly initalizied and parsed.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Updated the content parsers parseTextBlocks method to include xobject processing. This feels like deja vu as I'm sure I've fixed this in the past. Regardless text extraction is working correctly with the optimization that not all page objects are parsed, such as images and other non related text content.