> This has nothing to do with FrameMaker in general or Save as PDF in particular. [1]https://helpx.adobe.com/acrobat/kb/change-in-support-for-acrobat-and -reader-plug-ins-in-modern-web-.html
Actually, I fear it does have to do with FrameMaker's "Save as PDF" functionality. We have repeatedly been warned by the experts who know about these things, that it would be foolish to attempt to put Adobe Acrobat Pro DC and Adobe Reader on the same machine -- due to sloppy programming by these two product teams, they will access and overwrite each other's parameter files. Therefore I need to pose the question, is that warning still correct, or by now has it become old scoop? The problem is that although the Chrome browser may pick up and use the Adobe Reader as an extension to read Adobe PDF files, it definitely does not pick up and use Acrobat Pro DC. Since we are warned not to put Adobe Reader on a machine having the Acrobat Pro DC software, this makes it difficult to access Acrobat PDF documents using Chrome. We would need to have one machine dedicated to generating the PDFs and another machine dedicated to accessing them, no? References 1. https://helpx.adobe.com/acrobat/kb/change-in-support-for-acrobat-and-reader-plug-ins-in-modern-web-.html _______________________________________________ This message is from the Framers mailing list Send messages to [email protected] Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to [email protected]
