[
https://issues.apache.org/jira/browse/PDFBOX-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925458#comment-15925458
]
Roman commented on PDFBOX-3715:
-------------------------------
Thanks!
Yep, I've already calling setSuppressDuplicateOverlappingText(false), and this
helps. However, my doubt is this is rude solution, since many characters has
appeared in other PDFs, which were suppressed before. If you do not see an easy
way to add some backward compatibility mode (so it will suppress other
duplicates, but not in this PDF, as it was before) it would be interesting.
Otherwise, feel free to close this.
> Text Stripper regression in 2.0
> -------------------------------
>
> Key: PDFBOX-3715
> URL: https://issues.apache.org/jira/browse/PDFBOX-3715
> Project: PDFBox
> Issue Type: Bug
> Reporter: Roman
> Attachments: WindowsPhone7.pdf_page1_qdf.pdf
>
>
> When migrated from 1.8 to 2.0, we realized that some spaces are disappeared.
> Please see attached PDF. Disappeared spaces are shown as blue boxes in it.
> Those spaces WERE present in 1.8 version.
> Our App overrides *PDFTextStripper* class, implements *writePage()* method,
> and uses *charactersByArticle* property, which is actually a list of all
> *TextPosition* objects existing for every character from document.
> Some trailing spaces are disappeared from it. In the same time, those spaces
> are present in PDF via explicit declaration. For example, these piece of
> attached PDF contains the space right after "contents" word:
> {code}
> [( the content)-7(s )-2(of t)...]TJ
> {code}
> PS
> I found that this bug occurs only when *sortExtractedTextByPosition* mode
> is set to *false*. The spaces removed from inside the text by
> *suppressDuplicateOverlappingText* feature, because there are another spaces
> with almost same coordinates in the begin of document. When sorting, those
> spaces are moved inside text, in place of removed ones. The remaining
> question is how did this work in 1.8 and if PdfBox can be enhanced by adding
> some "backward compatibility" mode so we can avoid of such regressions?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
