![]() ![]() You just place the PPD in a directory and it's becomes available to the application with no need to install a printer driver. Not meaning to start a Mac/Windows holy war but this is so easy to do on a Mac. I know that comes as a shock that an aspect of expensive software might not work correctly and we have to use a work-around but trust me, it happens. Sometimes it's a more complex issue of flattening transparency when the export function is supposed to do it but doesn't work correctly. Many times we need to write a PostScript file to disk and distill it as opposed to exporting a PDF directly because either the application has no PDF export or we need controlls for the file creation that are not in the export dialogs. We create a file and then "SUBMIT" it to a "RIP" that lets us preview the file or or we pre-process it with additional software that might do something like imposition or color separating or whatever. Why do we do it? Because we don't "PRINT" to a printer. We in printing have been writing PostScript files to disk since it was possible to do so. ![]() Why someone needs to do that comes under the category of "If you have to ask then you really don't understand the issue so you're probably not ready to receive the explanation."īut I'll try to explain it. We don't need or want a printer driver in this case because we are not actually printing to any particular device. What is needed is a simple way to place a PPD file on Windows 7 so the user can select the option of writing a PostScript file to disk and referencing that particular PPD. It's either Windows users never use PostScript or some other reason I can't understand. It's always amazing to me how discussions of PostScript bog down with Windows users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |