[
https://issues.apache.org/jira/browse/PDFBOX-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201624#comment-17201624
]
Tilman Hausherr commented on PDFBOX-4964:
-----------------------------------------
It's worse - the problem is in PDFStreamParser, or rather in
BaseParser.parseDirObject(). An invalid token is quietly skipped, although
there is another error message that comes later.
What we could do is to add another log message, which would give an additional
hint on the problem. Something like
bad string skipped: 'Tw'
with offset etc
> PDFDebugger Text View for Streams hides errors
> ----------------------------------------------
>
> Key: PDFBOX-4964
> URL: https://issues.apache.org/jira/browse/PDFBOX-4964
> Project: PDFBox
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 3.0.0 PDFBox
> Environment: Win10
> Reporter: Michael Klink
> Priority: Major
> Labels: debugger
> Attachments: 2-30-SL-manual-DE.pdf,
> 2-30-SL-manual-DE.pdf-6-2-Hex.png, 2-30-SL-manual-DE.pdf-6-2-Txt.png
>
>
> In the context of [this stack overflow
> question|https://stackoverflow.com/q/64013884/1729265] I used the PDF
> Debugger to inspect the second page content stream of page 6 of the document
> provided as example,
> [2-30-SL-manual-DE.pdf|http://www.autosfera.lt/images/Manuals/Nussbaum/2-30-SL-manual-DE.pdf],
> also attached to this issue.
> The problem that question was about is caused by an invalid literal (neither
> string nor number) in some *TJ* instruction array argument. This literal
> indeed was visible in the hex view of the PDF debugger:
> !2-30-SL-manual-DE.pdf-6-2-Hex.png!
> (See the "Tw" literals in the *TJ* arrays.)
> But in the text view it was hidden:
> !2-30-SL-manual-DE.pdf-6-2-Txt.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
