Practicalites of non-DSC-conformant PostScript

[Michael Sweet]

John A. Murdie wrote:
> Mike Sweet wrote:
>> You can play with the application/vnd.cups-raw MIME type definition
>> (or add your own .types file with additional rules) to flag the output
>> from the Windows clients as raw...
> 
> Umm, I don't understand that. Unless we have separate queues for the Windows and Linux systems (something I don't want to have because of the otherwise unnecessary duplication of entities), the mime.types file will be used to identify the PostScript coming from the Windows clients as PostScript, and the mime.convs file will `recommend' that it be pushed through pstops(1). If I change mime.convs to treat PostScript as raw, then PostScript coming from the Linux systems (to the Solaris print server) will be treated rawly, too, with the loss of functionality.

You can make a rule that matches on Windows PostScript output...

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Publishing Software        http://www.easysw.com