All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>,
	Marek Kasik <mkasik@redhat.com>
Subject: Re: [Printing-architecture] Some suggestions for the DNS-SD (Bonjour) printer support in the dialog
Date: Thu, 13 Jun 2013 14:49:33 +0200	[thread overview]
Message-ID: <51B9BFDD.50305@gmail.com> (raw)
In-Reply-To: <2E6F3E0A-2BC0-42E6-83E9-FFB185353242@apple.com>

On 06/13/2013 01:39 PM, Michael Sweet wrote:
> 
> The issue here is that the other end will need to support the file formats and options you are passing.  If you supply a local PPD then cupsd will convert into a format that the other end can handle.
> 

Here one could easily restrict the support to printers with standard
PDLs so that a handful of filters is enough. Then one sends always PDF
and tell by IPP attributes which output format and which option
settings. So what one needs is the right IPP attributes to tell CUPS the
output format (instead of needing it hard-coded in a PPD).

Would be great if CUPS is capable of this, but if not, I have an idea.
One would need a pdftoany filter which calls first pdftopdf (if pdftopdf
is installed, we could leave it out on mobile) and then one of
pdftoraster+rastertopwg, pdftops, nothing, gstopxl,
pdftoraster+rastertopcl, depending on what output format was requested
by an option (IPP attribute). Problem is how to make the queue using
this filter without having a PPD with hard-coded paper sizes (perhaps
System V interface script?).

   Till


  reply	other threads:[~2013-06-13 12:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 19:48 [Printing-architecture] Some suggestions for the DNS-SD (Bonjour) printer support in the dialog Till Kamppeter
2013-05-17  5:32 ` Michael Sweet
2013-05-17  7:21   ` Till Kamppeter
2013-05-17 14:17     ` Michael Sweet
2013-05-18 23:45       ` James Cloos
2013-05-19  6:08         ` Michael Sweet
2013-06-12 22:52           ` Till Kamppeter
2013-06-13 14:05             ` Michael Sweet
2013-05-17 10:02   ` Tim Waugh
2013-05-17 14:20     ` Michael Sweet
2013-06-13 10:01   ` Till Kamppeter
2013-06-13 11:25     ` Michael Sweet
2013-06-13 14:34       ` Till Kamppeter
2013-06-13 14:40         ` Michael Sweet
2013-06-13 11:42     ` Tim Waugh
2013-06-13 12:20       ` Till Kamppeter
2013-06-13 14:08         ` Michael Sweet
     [not found] ` <51962BA7.4030304@redhat.com>
2013-05-17 14:23   ` Michael Sweet
2013-05-17 18:14     ` Till Kamppeter
     [not found]       ` <D36BAB03-9A91-42E9-A994-DC0D3C6C254D@apple.com>
2013-06-13 10:11         ` Till Kamppeter
2013-06-13 11:39           ` Michael Sweet
2013-06-13 12:49             ` Till Kamppeter [this message]
2013-06-13 14:19               ` Michael Sweet
2013-06-13  9:58     ` Till Kamppeter
2013-06-13 11:18       ` Michael Sweet

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=51B9BFDD.50305@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=mkasik@redhat.com \
    --cc=msweet@apple.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    /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.