An export to PDF utility was freely available for Visio 2007, and was built in to Visio 2010. However, I have always been disappointed by the lack of support for Visio layers, Shape Data and multiple hyperlinks per shape in the PDF output. Microsoft have always told me that this is because they have limited control over the public PDF format, as opposed to the proprietary Adobe PDF format (These features are also surprisingly missing from the export to XPS tool, even though this format originated from Microsoft). So, the question is, does Adobe Acrobat make better PDF files from Visio than Microsoft’s free tool?
I downloaded the trial version of Adobe Acrobat X Pro after reading the product comparison at http://www.adobe.com/products/acrobatpro/buying-guide.html, because Acrobat X Standard does not have support for Visio.
I used my diagram of Visio 2010 Import & Export Features (see http://blog.bvisual.net/2011/05/24/data-import-export-features-in-visio-2010/ ) for the test because it has multiple layers, Shape Data and multiple hyperlinks.
The page has just three layers (Connector, Container and Data Graphic), and their visibility can be toggled in Visio:
The bVisual logo in the bottom left corner has multiple hyperlinks, whilst all the other rectangles have singe hyperlinks….
The Microsoft Save As PDF utility
Firstly, I made a standard export to PDF using the Microsoft built-in feature, and notice that there are a few options that can be set, but none of them are for layers, Shape Data or hyperlinks:
When I viewed the output in a PDF reader, then I can see that there is support for a single hyperlink on each shape, but there is no support for multiple hyperlinks per shape, nor is there support for layers or Shape Data.
The output happened very quickly and the visual appearance was very good, but only a single hyperlink per shape is presented:
The Adobe Acrobat Create PDF utility
My previous experiences of Adobe Acrobat have been mixed: Whilst I have liked the support for layers and custom properties, I always used to find the way they loaded their add-in into Visio problematical. So, I have not loaded Adobe Acrobat for a few years, but I thought that I should check it out again.
First impressions of their FluentUI ribbon tab were good, but I was surprised to see that Shape Data is still being referred to as Custom Properties, even though Microsoft changed the name in Visio 2007:
The second panel asks if I would like to flatten all the layers into one, or retain them. Obviously, I wanted to retain all layers to see what happens next:
There was a promising message that the page will look just like the original:
The conversion process was quite lengthy as it seemed to switch individual shape visibility off and on again.
However, the promise of visual fidelity was not fulfilled … first thing I noticed that some of my container shapes were completely missing!
Although my page layers appeared to be listed correctly on the left-hand side, only the Background layer toggled the layer visibility off/on – perhaps because the Background is actually a different page – not a real layer at all!
Actually, even the Background was incorrect because it also changed the visibility of containers on the foreground page.
So, perhaps the Shape Data is properly converted to Object Data?
Well, it has encouraging to find the Object Data Tool displayed on the right mouse menu, however it didn’t seem to do anything for me.
However, I did find the Model Tree view, which does appear to have the Shape Data
Unfortunately, the Zoom to Selection option goes to the top left corner of the page for every single shape:
As for multiple hyperlinks per shape? ‘Fraid not – just the single one becomes active:
Conclusion
I started this blog article believing that Adobe Acrobat would provide better output than the Microsoft supplied Export to PDF inside Visio, but I was wrong. If you cannot trust a PDF writer to actually display all of the visual elements that you expect, then it does not matter what other bells and whistles it has to offer.
Adobe developers obviously do not understand the structure of a Visio document. Very disappointing!
BTW, I tried to contact Adobe for comments before publishing this article, but I didn’t get a response …
Appendix
See http://en.wikipedia.org/wiki/Comparison_of_OpenXPS_and_PDF for a Comparison of OpenXPS and PDF.