All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <mike@easysw.com>
Cc: OTANI Koji <sho@bbr.jp>, Tobias Hoffmann <th55@gmx.de>,
	Printing-japan <printing-japan@lists.linux-foundation.org>,
	"printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>,
	Hin-Tak Leung <hintak_leung@yahoo.co.uk>
Subject: Re: [Printing-architecture] Two more PDF CUPS filters: pstopdf and cpdftocps ("PostScript driver")
Date: Tue, 12 Aug 2008 12:06:39 +0200	[thread overview]
Message-ID: <48A160AF.1070508@gmail.com> (raw)
In-Reply-To: <48971403.9090006@easysw.com>

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? Which part of CUPS is handling them? How can one benefit from 
them in a PDF printing workflow (PostScript -> PDF -> pdftopdf -> 
pdftoraster ...)? Do they have to be in the beginning of the PS file or 
can they be anywhere?

    Till


  parent reply	other threads:[~2008-08-12 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04  8:35 [Printing-architecture] Two more PDF CUPS filters: pstopdf and cpdftocps ("PostScript driver") Till Kamppeter
     [not found] ` <48971403.9090006@easysw.com>
2008-08-04 17:01   ` Till Kamppeter
2008-08-12 10:06   ` Till Kamppeter [this message]
     [not found]     ` <48A1B133.4050408@easysw.com>
2008-08-12 19:29       ` Till Kamppeter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48A160AF.1070508@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=hintak_leung@yahoo.co.uk \
    --cc=mike@easysw.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=printing-japan@lists.linux-foundation.org \
    --cc=sho@bbr.jp \
    --cc=th55@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.