I hear “This isn’t working” from frustrated customers on a fairly regular basis. Most of the time it’s because a particular PDF file isn’t behaving the way that they expect it to. So, with the recent release of the “Compatibility Advisory Regarding Adobe Reader plug-in and Acrobat plug-in with Safari 5.1“, I thought I’d address a few broader compatibility issues that may arise when working with PDF files.
But first… Yes – I’m biased – I work for Adobe. So I’ll try to stick to just the facts in this article and let everyone come to their own conclusions. I’m also not going to cover the obvious compatibility issues that are inherent with PDF Portfolios, Multimedia and other Flash dependent objects in PDF files, but will, instead, limit my discussion to the core of PDF that is in use my most people out there and not the cutting edge stuff that I talk about in my developer blog.
There are three scenarios that are the root cause of most issues around use of PDF files and I’ll address each separately but they can… and do… occur in combination with each other.