I see three problems right now:
Word documents embedded within a SWX document print with a border around them. This is new with the switch from Bluebeam. You can get rid of this by right-clicking each Word doc and choosing "Sharpen Zoom State", which is fine, except that we have hundreds if not thousands of documents to do this on. One more workaround to remember...
I want to scale all pdfs to 8-1/2 x 11, but Save As pdf automatically prints at 1:1. Printing them full size screws up the header size and lineweights when we use Acrobat to print on 8-1/2 x 11 paper later. The header turns out tiny (useless) and the lineweights appear too thin. When I use a printer driver I just choose 8-1/2 x 11 paper size and the pdf turns out exactly the same as hard copies on letter size paper out of a printer.
Text in embedded Word documents is not crisp. This also is new with the Adobe Save As function. Printing using a pdf printer driver produces crisp text.
These issues wouldn't be that big of a deal if we were just using pdfs for archiving purposes, but we're moving toward the pdfs being the official document rather than the hard copy printout. We use a macro that silently prints to pdf and then prints a hard copy of the pdf using Acrobat. So we know the pdf file matches the paper print, since we're actually printing the pdf. (We got burned in the past when printing to paper, checking the paper print, and then printing to pdf
-- from time to time the pdf was different than the paper print. We no longer trust SWX to produce the same print twice in a row.)
Frankly, I would just as soon not experience SWX's learning curve of implementing Bluebeam and then switching to Adobe and then switching to ?? in the future. I could have saved hours of headaches and actually have what I want if SWX hadn't broken the silent print to pdf with a printer driver when Save As pdf was implemented.