[ 
https://issues.apache.org/jira/browse/PDFBOX-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15026281#comment-15026281
 ] 

Tilman Hausherr edited comment on PDFBOX-3130 at 11/25/15 6:18 AM:
-------------------------------------------------------------------

That is a different problem. This seems to be similar to the file 
PDFBOX-3062-H6NIYQXHLPGD3GI6SNIYINRAZBCDHUCB.pdf. See attached image that shows 
the "bounds" of your file. The red bounds are used for text extraction, i.e. to 
decide whats to be on one line.


was (Author: tilman):
That is a different problem. This seems to be similar to the file 
PDFBOX-3062-H6NIYQXHLPGD3GI6SNIYINRAZBCDHUCB.pdf. See attached image.

> Recent regression in PDFTextStripper, text getting garbled
> ----------------------------------------------------------
>
>                 Key: PDFBOX-3130
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-3130
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Text extraction
>    Affects Versions: 2.0.0
>            Reporter: Fred Andrews
>            Assignee: Tilman Hausherr
>             Fix For: 2.0.0
>
>         Attachments: garbled text 2-marked-1.png, garbled text 2.pdf, garbled 
> text.pdf
>
>
> Text extraction using PrintTextLocations is getting garbled characters in the 
> attached snippet. 
> For this file it is getting one string of "2O(Er4env vqeheurosriAurseirueeass 
> ss/Ct:7:rh adaliaargynse csr eadc+cit6e l1ipc te+2en 6d9c1)9e 91 2933"
> This test case is about as small as I could make it and still show the 
> problem; when I reduced the file to just one line of text, then the text came 
> though correctly.
> This problem shows up in RC2 and the latest development build.  I believe it 
> was OK in the development build from Nov 4



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to