[
https://issues.apache.org/jira/browse/PDFBOX-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17129375#comment-17129375
]
Michael Klink commented on PDFBOX-4865:
---------------------------------------
{quote}Actually /Producer have two space{quote}
The number of spaces is irrelevant, there may be 20, there may be none, it
doesn't matter. As written the value of the key {{/Producer}} is {{/Creator}}
(which is invalid, according to the spec it must be a text string) and the next
key is
{{<359D509429DF857A0FCBEE3A0FB238910C6864154C8174774FD8682344EE88EF372C9045BCAFD973DAFA07CD>}}
(which also is invalid, keys must be names, not strings).
{quote}It can be opened normally。if /Creator value don't start with '<',Can be
parsed normally{quote}
Different parsers react to broken data in different ways. It does not matter
whether there is some parser that does not stop when parsing these broken data.
In particular PDF viewers are very lax in this regard.
> Parse PDF Failed
> ----------------
>
> Key: PDFBOX-4865
> URL: https://issues.apache.org/jira/browse/PDFBOX-4865
> Project: PDFBox
> Issue Type: Bug
> Components: Parsing
> Affects Versions: 2.0.19
> Reporter: daihy
> Priority: Major
> Attachments: 特殊字符.pdf
>
>
> if file have special text like this
> {code:java}
> << /Title 18 0 R /Producer /Creator
> <359D509429DF857A0FCBEE3A0FB238910C6864154C8174774FD8682344EE88EF372C9045BCAFD973DAFA07CD>
> /CreationDate 21 0 R /ModDate
> {code}
> Invalid dictionary, found: '<' but expected: '/' at offset 13909
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
