All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: "printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Useful utility: cups-filter-check
Date: Mon, 16 Dec 2013 17:26:58 +0000	[thread overview]
Message-ID: <1387214818.12274.33.camel@rubik> (raw)
In-Reply-To: <52AF35A2.6060804@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 803 bytes --]

On Mon, 2013-12-16 at 18:17 +0100, Till Kamppeter wrote:
> Should we perhaps make this part of cups-filters?

Yes, sure -- or Michael Sweet's suggestion of enhancing cupsfilter would
also be fine. It's quite nice to be able to loop over all of the
configured MIME types though. I guess it can be done in a shell script
(reading *.types)... it just might not be very pretty:

grep '^[^[:space:]#]' /usr/share/cups/mime/mime.types | (while read t;
do set $t; echo $1; done) | sort

Incidentally, while playing around with it I noticed the only route from
application/vnd.adobe-reader-postscript -> application/vnd.cups-pdf is
via image/tiff. Is that intentional? I expect any printer capable of
handling PDF can also handle PostScript, and that path works fine at
less cost.

Tim.
*/


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 482 bytes --]

  parent reply	other threads:[~2013-12-16 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 17:10 [Printing-architecture] Useful utility: cups-filter-check Tim Waugh
2013-12-16 17:17 ` Till Kamppeter
2013-12-16 17:19   ` Michael Sweet
2013-12-16 17:26   ` Tim Waugh [this message]
2013-12-16 17:54     ` Michael Sweet
2013-12-27 15:29       ` Till Kamppeter
2013-12-27 19:55 ` Alex Korobkin
2014-01-02  2:34   ` 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=1387214818.12274.33.camel@rubik \
    --to=twaugh@redhat.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=till.kamppeter@gmail.com \
    /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.