In a previous post, I discussed a problem with reading PDFs in Windows 7. The partners have released the pdf in question for you examination with the hope that someone can determine the problem. The errors have occurred on three different installations of W7 but none on XP.
The errors are run on gibberish and blank pages. Let me know what you find.
Thanks,
Burt
Yep. I see what you mean (Used Acrobat X and Nitro PDF). It looks like something that was encoded in the PDF file. It's selectable text, for sure.
I don't remember if this was mentioned in the last post but what is the PDF created with? What is the SPECIFIC SOFTWARE used to create it?
Nitro PDF stated the PDF was corrupted and was repaired. I'm thinking there is something going wrong during the creation process.
My recommendation is to stick with software from Adobe (Like Acrobat). I know it costs money and I know people hate Adobe, etc. etc. but after all they DID create the PDF standard and they DO know it best. If not Adobe, something mainstream like CutePDF or NitroPDF.
The problem is we are way downstream. The PDF gets created, perhaps, 5 generations ago. In all cases, it is readable in XP. What stymies us is there must be W7 users in this path somewhere who have complained about the readability issue as well.
The document properties say it was produced by iTextSharp 4.1.6 by 1T3XT.
You know, let me give it a try on my XP virtual machine and report back.
Also I noticed that iText is a PDF library versus a full-blown application meaning whomever is using the iText library may be giving it an improper command that is including the seemingly random and erroneous lines of text.
I'll keep looking into it.
So I kept poking around and I've come to a conclusion as to WHAT is going on.
Every time you see that "line of text", there is an encoding error in the PDF which leads me to believe that what or whomever created the PDF used poorly-built tools to do so. If you'll notice on EVERY page you see that text, there are pages missing from the deposition. The first instance is page 261-264. Notice that 261 is there, 262 is not, part of 263 is not, and 264 is not. Move to the next instance and the result is the same. Adobe Reader X (IN XP) also notified me that there were errors on that page (and all the other pages with this issue) and it may not have been rendered properly.
My suggestion. Whomever created the PDF needs to go back and use more mainstream tools. I've linked a couple below. It also wouldn't even hurt to invest in them or even invest in a copy of Adobe Acrobat. $199 isn't much when it comes to knowing that Adobe invented the PDF. (at least that's how I see it)
CutePDF - Create PDF for free, Free PDF Utilities, Save PDF Forms, Edit PDF easily.
Nitro PDF Software — Create & Edit PDF Files
Both above have free creation tools as well as higher-end professional tools as well (for cost).
I'm not sure how people before you weren't able to notice this anomaly, unless they weren't reading the document. At a glance, it seems ok, but reading it definitely brings it to light.
Let me know what's up!
Thanks!
Jonathan,
Thanks for all that good work. I think part of the problem is as the documents get passed around they are often given to summerizers, which is what my wife and her partner are. By then, the doc has been thru multiple firms with only brief glimpses by the attorneys or their assistants.
Virtual XP is a good idea. We have registered copies. What host do you use? I've used VirtualBox on linux so that's all I'm familiar with and I don't know what others exist.
Again, thanks for your help,
Burt
Virtual PC with Windows XP Mode.
Truthfully, though. There'll be no difference in the output of the PDF if the program used is the same version (I used Adobe Acrobat and Reader X in both XP and 7 and got the exact same results) if you use XP over 7.
Officially, These rogue lines of text were caused by whomever encoded the PDF the first time.
Jonathan,
Fortunately, my wife's partner has an old version of XP with an old version of Reader so at least one of them can read the PDFs. Hopefully, this problem will be realized in the near future and the culprit will be flushed out and made to update to the 21st century.
Here's a big glass of beer to you!
Burt
Quote
