[
https://issues.apache.org/jira/browse/PDFBOX-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045590#comment-14045590
]
Tilman Hausherr edited comment on PDFBOX-2158 at 6/27/14 6:25 AM:
------------------------------------------------------------------
The problem of that file wasn't just that the decode had the wrong size, there
were null objects in it. These null objects did a NPE in toFloat(), the part
that you quote wasn't even reached :-( . My solution is to hope that there are
two entries at least, and that the first two entries are numbers and to get
them.
was (Author: tilman):
The problem of that file wasn't just that the decode had the wrong size, there
were null objects in it. These null objects did a NPE in toFloat(), the part
that you quote wasn't even reached :-( . My solution is to hope that there are
two entries at least, and that the first two entries are floats and to get them.
> ExtractText missing most of text in this PDF file, due to font bounding box
> with minus infinity
> -----------------------------------------------------------------------------------------------
>
> Key: PDFBOX-2158
> URL: https://issues.apache.org/jira/browse/PDFBOX-2158
> Project: PDFBox
> Issue Type: Bug
> Components: Text extraction
> Affects Versions: 1.8.5
> Environment: Windows x64
> Reporter: Joel Hirsh
> Attachments: negative.text.box.pdf
>
>
> Attached PDF file is missing most of the text when processed by the
> ExtractText example program
> I traced it down to PDFontDescriptorDictionary.getFontBoundingBox() getting a
> rectange for COSName.FONT_BBOX that contained a ymin value of minus
> infinity. That method then creates a PDRectangle which calculates a bounding
> box with a ymin value of -65,329, and results in an enormous text size, and
> things go downhill from there. The text cannot be matched up, and most of it
> ends up being discarded.
> I was able to hack a fix by doing a check in the constructor
> PDRectangle.PDRectangle( COSArray array ) for big negative numbers and
> setting them to 0. With that change, all the text came through as expected.
> However, I don't have enough familiarity with the code to understand what a
> real fix ought to look like.
> The PDF file looks to be fine by other programs such as Acrobat and NitroPDF
--
This message was sent by Atlassian JIRA
(v6.2#6252)
