signable pdf

Post by **magick** » 2006-11-09T14:01:51-07:00

ImageMagick conforms to the PDF specification, meaning any/all conforming rips/renderers/viewers should be able to process PDF's generated by ImageMagick. If you discover a PDF generated by ImageMagick that you suspect does not conform to the specification, post a URL to your PDF here and describe the problem.

Post by **magick** » 2006-11-09T22:27:12-07:00

What type of signature with what version of Acrobat? Are they also adding a digitized signature or watermark to the signature appearance?

Post by **magick** » 2006-11-10T09:47:44-07:00

We have a contact with a company that exclusively works with PDF. They had no problem with the image with Acrobat 5-8. Unless you can prove the image does not follow the PDF standard, there is not much we can do to help.

Post by **magick** » 2006-11-10T14:32:29-07:00

What is malformed about the objects? If we know the problem we can add a patch to the next release of ImageMagick.

Post by **magick** » 2006-11-10T15:38:44-07:00

Object 17 is a length object. If I change it to

17 0 obj
<<
54490
>>
endobj

I get an error

Error (591): Dictionary key must be a name object
Error (527): Bad 'Length' attribute in stream
Error: Weird page contents
Error (591): Dictionary key must be a name object
Error (527): Bad 'Length' attribute in stream
Error: Weird page contents

How should this length object look?

Post by **magick** » 2006-11-10T16:06:39-07:00

Object 17 is just an example of an ImageMagick PDF length object. If I change the length objects to include << >> it produces an error.

Post by **magick** » 2006-11-17T22:14:50-07:00

Object 17 was corrupt but it seems specific to your image or perhaps the version of ImageMagick you are using. Recent versions of ImageMagick do not create corrupt objects.

Post by **magick** » 2006-11-28T13:48:35-07:00

We added a patch to ImageMagick 6.3.0-8 Beta to fix the corrupt object problem. It will be available sometime tommorrow.