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

Timo Boehme commented on PDFBOX-1822:
-------------------------------------

For mixing up xref tables/streams see 
http://stackoverflow.com/questions/14962151/mixing-xref-tables-and-xref-streams 
and http://forums.adobe.com/thread/1034273
Normally you have to stay with one kind of XREF, however hybrid documents are 
possible in order for old parsers to parse the document via xref table - so 
while we have both kinds all content must be accessible by xref table in this 
case (no changing within xref chain).

[~lehmi]: if I understand your patch correctly it is now up to the parser to 
set isXrefStream in COSDocument? This will be set by NonSeqParser. However if 
one uses the sequential one this property won't be set at all. So do we need to 
change PDFParser as well or should the boolean in COSDocument be an object with 
NULL for not set in which case the old behavior 
COSName.XREF.equals(trailer.getItem(COSName.TYPE)) is used?


> Signature byte range is Invalid
> -------------------------------
>
>                 Key: PDFBOX-1822
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1822
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Parsing, PDModel, PDModel.AcroForm, Signing
>    Affects Versions: 1.8.3, 1.8.4, 2.0.0
>            Reporter: vakhtang koroghlishvili
>            Assignee: Andreas Lehmkühler
>             Fix For: 1.8.4, 2.0.0
>
>         Attachments: araxis-merge - compare two document.jpg, 
> damaged-sig.jpg, unsigned-signed.pdf, unsigned.pdf, unsigned_signed_fix.pdf
>
>
> On person send me a unsigned PDF document. He wanted to sign it. When I try 
> to sign it (using pad box), I have some problem.
> After signing adobe reader tells me "The signature byre range is invalid".  
> I will attach original and signed document.
> I think, it is PDF box parser error. another signature libraries sign 
> document very well. I'm searching the problem at the moment, in order to fix 
> it.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to