I'm confused. I've just generated a signature with Acrobat 7 and I have in the 
/DR key:

/Encoding<</PDFDocEncoding 57 0 R>>

In the implementation note the PDF reference says:


Acrobat viewers may insert additional entries in the DR resource dictionary,

such as Encoding, as a convenience for keeping track of objects being

used to construct form fields. Such objects are not actually resources and

are not referenced from the appearance stream.



So, what's valid after all?



Paulo



________________________________
From: Leonard Rosenthol [EMAIL PROTECTED]
Sent: Thursday, November 06, 2008 5:24 PM
To: Post all your questions about iText here
Subject: Re: [iText-questions] Unrecognized PDF content: The document contains 
PDF content or custom content not supported by the current version of Adobe 
Reader.

You are correct - it _IS_ the /Encoding/WinANSIEncoding value inside that DR 
dictionary.  That isn't a valid value there - hence the error being thrown.   I 
suspect that's a bug in iText - easy to fix.

Leonard

On Nov 6, 2008, at 3:43 AM, Shadow Man wrote:

Hello again,

The code for signing is mostly from the iTextSharp examples Paulo provided, and 
most of the low level manipulation is done to insert the pkcs7 signature into 
the signature dictionary. If you want i could provide some code if it would 
help you find whats causing it. Just let me know.

Also I didnt mean that the error was caused by the Encoding type, but by the 
font description object inside the resource dictionary, however it does seem 
strange like you said, so it probably isnt the cause.

Btw im monitoring this thread so if you need any more details just ask. I'll be 
glad to help.

J.

On Thu, Nov 6, 2008 at 12:17 PM, Leonard Rosenthol <[EMAIL 
PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
Doubtful that you are on the right track - nothing wrong with using WinANSI 
encoding for font data...  It is more likely either a bug in iText itself or 
something you did in some low level code that you wrote.

Let me take another look at the file for more details...

Leonard

On Nov 6, 2008, at 2:49 AM, Shadow Man wrote:

Hello Leonard,

First of all, thanks for your response. After reading your mail I checked the 
syntax with Adobe Professional 8 and the same error came up, except for the 
part where the error trigger is mentioned (since no trigger was shown).

For what I've seen it seems like a resource dictionary has some invalid key 
value, but i cant say my knowledge about the pdf format is enough as to make me 
feel confortable on the subject... so, please correct me if im wrong, but my 
guess is that what may be causing the problem is the font description (which 
says its using Adobe Standard Latin characters set...) (the only font 
description property set to true for what i could see in the objecst explorer, 
and your image dump).

Would you say im in the right track, any ideas on how could i solve this? Maybe 
change the default font used for the process?

Thanks in advance,

J.

PS: The certificate's cn field has characters like 'a' with backward accent 
etc... this, of course, can't be changed.

On Wed, Nov 5, 2008 at 9:27 PM, Leonard Rosenthol <[EMAIL 
PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
You are running into the updated PDF syntax validator in Acrobat/Reader 9.

Enclosed is a detailed dumpfrom Preflight 9...

Leonard




On Nov 5, 2008, at 4:43 AM, Shadow Man wrote:

Hello,

I recently used itextsharp to build an application that signs pdf documents 
using timestamps on the signature.

The problem i have is that using Acrobat 8, the signatures are validated 
correctly, however i recently discovered that with Acrobat Reader v9 (probably 
with Professional too, i havent tried it) signatures applied show as non 
verifiable cus of errors during validation. The error i get with Adobe 9 is:

4000: Unrecognized PDF content: The document contains PDF content or custom 
content not supported by the current version of Adobe Reader.

Im attaching sample pdf files to see if anyone has an idea of what could be 
causing the problem. Im interested in knowing if this is a flaw on the library 
itself, or its due to something im doing wrong. If so, how could i correct this 
problem.

Thanks beforehand,

J.

PS: About the sample files: they are both sigend with the same test 
certificate, time stamps are different thou.
<unsigned.pdf><signed.itextsharp.pdf><signed.acrobat.8.pdf>-------------


Aviso Legal:
Esta mensagem é destinada exclusivamente ao destinatário. Pode conter 
informação confidencial ou legalmente protegida. A incorrecta transmissão desta 
mensagem não significa a perca de confidencialidade. Se esta mensagem for 
recebida por engano, por favor envie-a de volta para o remetente e apague-a do 
seu sistema de imediato. É proibido a qualquer pessoa que não o destinatário de 
usar, revelar ou distribuir qualquer parte desta mensagem. 

Disclaimer:
This message is destined exclusively to the intended receiver. It may contain 
confidential or legally protected information. The incorrect transmission of 
this message does not mean the loss of its confidentiality. If this message is 
received by mistake, please send it back to the sender and delete it from your 
system immediately. It is forbidden to any person who is not the intended 
receiver to use, distribute or copy any part of this message.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions

Buy the iText book: http://www.1t3xt.com/docs/book.php

Reply via email to