by Phil Lee, VP Sales
There are literally hundreds ofexporters and converters out there. Of course, there’s the downloadable type, such as the Free . But there are also free online software versions, written by many different developers for the main reason of avoiding paying for the high cost of Adobe Acrobat to create PDF files.
And therein lies the problem.
Anyone with a penchant for open source software knows that one of the drawbacks can be the “Wild West” of compatibility. Which matters when the document you create or convert isn’t compatible with someone else’s version of the same software, or won’t render onscreen.
Also, all of these bits and pieces of software offer different features. For example, one user may want to export the links in. Another may need to archive the whole document with graphics. Yet another whole department may be tasked with archiving PDF documents in PDF/A for long term readability and searchability.
Can these situations result in incompatibility issues? Of course. Can they even create situations where the end user is faced with a document that won’t even convert to a PDF? Absolutely.
While all these scenarios are not entirely unavoidable, they do stem from a common problem: standardization.
We recently discussed the benefits of standardizing on a singleacross the enterprise. Not the least of which are your ability to rely on a unified set of underlying standards for how the solution you use works, what types of features it offers, who supports it and who you can rely upon if you need said support.
If you’re relying on a dizzying array of PDF viewers, editors, exporters and converters, perhaps it’s time your organization considers standardizing on a single solution that can handle all users’ needs across any platform you can throw at it.