[
https://issues.apache.org/jira/browse/PDFBOX-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993402#comment-13993402
]
Pat Hickey commented on PDFBOX-1895:
------------------------------------
I finally found the missing object.
It is the encryption object.
I have pasted its content below.
The /U token is only 16 bytes long...
doesn't the spec say it should be 32?
270 0 obj
<<
/CF <<
/StdCF <<
/AuthEvent /DocOpen
/CFM /V2
/Length 16
>>
>>
/EncryptMetadata false
/Filter /Standard
/Length 128
/O <1C05A048615171E5D46A21726E33D63AB2FFD258E5D9745CC19FAFD8CBC8B086>
/P -3900
/R 4
/StmF /StdCF
/StrF /StdCF
/U <568E89D6FDE15C453FCD04E69160C5BD>
/V 4
>>
endobj
> Modifying a damaged PDF damages it further
> ------------------------------------------
>
> Key: PDFBOX-1895
> URL: https://issues.apache.org/jira/browse/PDFBOX-1895
> Project: PDFBox
> Issue Type: Bug
> Components: Writing
> Affects Versions: 1.8.3, 1.8.4
> Reporter: Pat Hickey
>
> When re-writing a document with font descriptions, Adobe Reader is unable to
> display the fonts in the document. Reader can display the fonts in the
> original document. The difference is that in the original document, the font
> descriptions are in lower object numbers than the font references; in the
> output document, the font descriptions are in higher object numbers than the
> font references. Is there a quick way to re-order them?
> Update: the PDF file in question is actually corrupt, but somehow modifying
> it with PDFBox causes it to no longer be readable with Adobe Reader.
--
This message was sent by Atlassian JIRA
(v6.2#6252)