Hi Michal, On 25 Nov 2010 at 16:27, Michal Hocko wrote: > > > > > > Are you sure? It shouldn't be same because we are encoding strings in a > > > different way. How did you compare those documents? > > > > > I'm sorry, I wasn't clear. The *input* (linearized) PDF was the same one I > > sent you before. I didn't try to compare the delinearized PDFs. > > OK, just to make sure that I have understood you. Have you tried to > delinearze with the latest CVS snapshot and open the resulting document?
As noted before, I tried with the GNU tarball that I downloaded from the CVS. You said before that this was the same as the current snapshot. If that's correct, then the answer is yes, the error occurs with the latest CVS snapshot. > If this is the case then I do not know what can make acrobat consider > that the document is not correct (my version 9.2.10 doesn't complain). > It might be also bug in those applications. > It might be, but they are two different applications written by different companies. Also, note that the error message from Acrobat reader 7 only appears very briefly (maybe for half a second) before the PDF displays. I don't have a copy of Acrobat reader 9, but Acrobat reader 10 displays the PDF so quickly after loading it that it would be hard/impossible to see a similar error message (and perhaps they don't issue one because the error is repairable). Note that PDF-Xchange itself silently corrects the error when loading, and only complains when you want to do an incremental save. Further, if you are running on a "modern" cpu (rather than a 2.6GHz Pentium 4 like me), you probably wouldn't be able to see the message even from Acrobat reader 7 because it would disappear so quickly. My belief is that there probably is an error in the delinearized document, associated with the incremental save information. > > I have checked documents you have sent me in the separate (off-list) > email but it is really hard to judge anything from that as the document > is completely reorganized so I would have to match object-by-object > which I do not have time for. > I tried this: I sent the original & the delinearized PDF to the Solid Documents PDF/A validator. I know they are not supposed to be PDF/A-compliant, but I thought I would check if there were any error msgs issued for the delinearized that weren't issued for the original, in case they might give you a clue. Here's what I got for differences in error msgs: . "Metadata dictionary used stream filter" . "Incorrect delimiter used for indirect object" (many of these) As I said, these are probably worthless, but just in case ... I have also emailed the authors of PDF-Xchanage to see if they can help me determine what the problem is. I will let you know via the list what (if any) information I get from them. Roger ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Pdfedit-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pdfedit-support
