PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com _____________________________________________________________
example a customer has created a 8.5 x 11 4 pages she wants it to be printed on 11 x 17 then folded. There is an imposition tool on the Xerox colour copier that we use to convert from 8.5 x 11 to 11 x 17 it is there at the colour copier that I get the error message. >>> [EMAIL PROTECTED] 8/14/2003 4:32:11 PM >>> PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com _____________________________________________________________ Ah. I had it backwards. But now you're talking about impossition issues. I'm afraid I don't understand what the situation is. Could you please explain your situation in more detail? --Mark Storer Software Engineer Cardiff Software #include <disclaimer> typdef std::disclaimer<Cardiff> Discard; > -----Original Message----- > From: Adrian Colefield [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 14, 2003 1:18 PM > To: [EMAIL PROTECTED] > Subject: RE: [PDFdev] getting This PostScript file was created from an > encrypted PDF Redistilling an encrypte > > > > PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com > _____________________________________________________________ > > customers use Word, Pagemaker Publisher etc to create a PDF > they then send it to me and I print it > to my Xerox digital colour copier. It is at the imposition > tool on copier that I get this messaage. > File is 8.5 x 11 and wants it 11 x 17 folded. > > >>> [EMAIL PROTECTED] 8/14/2003 4:00:14 PM >>> > > PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com > _____________________________________________________________ > > It's not clear what you're asking... but let me see if I > understand you: > > You have a PDF that is printed and then redistilled. That > redistilled PDF > is not secured, and you want to know how to keep the security. > > You can't. Once they've got postscript of your PDF, you've lost. > > But there are a couple things you can do. > > 1) Prevent printing. Allowing printing is a gaping hole in > true security. > This is a simple matter of a security flag in the standard > security handler. > > 2) Store important data such that it is not printable. > Annotations have > flags governing their appearance in the printed version. At > that point, you > may as well not allow printing at all. > > > There may be some strange PS-in-the-PDF trickery you could do to tell > distiller to recreate the PDF with a given password, but that > is trivial to > defeat (alter the PS before distilling). PDF allows you to > store arbitrary > PS that is not executed by the viewer, just passed on for > printing. You can > build some PDF structures in PS. I don't know if you can control > distiller's output settings in this way, but it's worth looking into. > > Note that it may not be possible to make this technique "recursive"... > converting the redistilled PDF to PS and to PDF again would > defeat this > tactice (without some PS wizardry) > > --Mark Storer > Software Engineer > Cardiff Software > #include <disclaimer> > typdef std::disclaimer<Cardiff> Discard; > > > To change your subscription: > http://www.pdfzone.com/discussions/lists-pdfdev.html > > > To change your subscription: > http://www.pdfzone.com/discussions/lists-pdfdev.html > To change your subscription: http://www.pdfzone.com/discussions/lists-pdfdev.html To change your subscription: http://www.pdfzone.com/discussions/lists-pdfdev.html
