![]() UPDATE (1/2/18): This is Adobe's support article describing a different issue but the same proposed registry change for avoiding text rasterization. It continues to create PostScript for my set of virtual printers. In the meantime, I've found that Foxit's most-recent PDF Reader does NOT have this same issue. It's creating quite a headache otherwise. I am hoping that Adobe sees a bug here to be fixed soon. and some applications, like Chrome, seem to always do this, nevermind the type of printer. My guess: like many Windows applications, when Adobe Reader prints to a device that it thinks is NOT PostScript-capable, Reader will choose to rasterize the PDF's text into image/vector data, rather than expressing it as text-and-font information. With the recent Reader release, these options are now disabled for all of my PostScript-capable printers, except when using the "Adobe PDF Printer". A tell-tale sign is that Adobe Reader, when printing, has 'Advanced' options that would typically let someone designate some PostScript options/preferences. The issue seems to be that the new release of Adobe Reader is no longer recognizing these PostScript printers as such. ![]() Examples: Foxit's PDF Printer, as well as an HP PostScript Driver I've been using whenever I need to redirect a printstream to a file. Like the poster, I'm working with a few virtual print drivers and have noted this change of behavior from Adobe Reader 2018.009.20050 is impacting them. I do not have an answer but I wish to comment and follow the topic. Voted Best Answer Click Start > Control Panel > Devices and Printers Select Add a printer Select Add a local printer Check Use an existing port and select. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |