From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <48A1E4AF.5020903@gmail.com> Date: Tue, 12 Aug 2008 21:29:51 +0200 From: Till Kamppeter MIME-Version: 1.0 References: <4896BF68.3080804@gmail.com> <48971403.9090006@easysw.com> <48A160AF.1070508@gmail.com> <48A1B133.4050408@easysw.com> In-Reply-To: <48A1B133.4050408@easysw.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Printing-architecture] Two more PDF CUPS filters: pstopdf and cpdftocps ("PostScript driver") List-Id: Printing architecture under linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Sweet Cc: OTANI Koji , Tobias Hoffmann , Printing-japan , "printing-architecture@lists.linux-foundation.org" , Hin-Tak Leung Michael Sweet wrote: > Till Kamppeter wrote: >> Michael Sweet wrote: >>> As for getting options from the PostScript data stream, today we >>> can embed page size and duplex mode in the PDF document. Supporting >>> other embedded features is not feasible, although applications can >>> use the CUPS PS job ticket comments at the top of the file: >>> >>> %!PS-Adobe-3.0 >>> %cupsJobTicket: option=value ... option=value >>> %cupsJobTicket: option=value ... option=value >>> %cupsJobTicket: option=value ... option=value >>> ... other PS comments >>> %%EndComments >>> >> >> What does CUPS exactly do when it encounters these %cupsJobTicket: >> comments? > > It adds them as job template attributes (options) for the job. > > > Which part of CUPS is handling them? > > The scheduler (cupsd) scans application/postscript files for these > comments. > > > How can one benefit from >> them in a PDF printing workflow (PostScript -> PDF -> pdftopdf -> >> pdftoraster ...)? > > We could update cupsd to do the same scan for application/pdf; > PDF supports comments just like PostScript. > Good idea, please do it. > > Do they have to be in the beginning of the PS file or >> can they be anywhere? > > They have to be in the initial comment block, after the "%!PS-Adobe" > line. The scheduler stops on the first line that does not begin > with a "%". > Thank you for the info. Did not find anything about that in the documentation. Till