From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: printing-architecture@lists.linux-foundation.org,
James Cloos <cloos@jhcloos.com>
Subject: Re: [Printing-architecture] On the Continued Need for PostScript Workflows
Date: Wed, 26 Jun 2013 00:05:19 +0200 [thread overview]
Message-ID: <51CA141F.2060609@gmail.com> (raw)
In-Reply-To: <55D4A897-5D56-4ADB-B183-379512FB2631@apple.com>
On 06/20/2013 03:29 PM, Michael Sweet wrote:
> James,
>
> Please file a bug against the OpenPrinting filters:
>
> https://bugs.launchpad.net/ubuntu/+source/cups-filters
>
> When submitting a PostScript file to a PostScript printer, the preferred filter should be pstops. The PDF filters should only get involved for non-PostScript print jobs.
>
James has filed it as
https://bugs.linuxfoundation.org/show_bug.cgi?id=1138
and I have fixed it now in the BZR repo. Will be included in
cups-filters 1.0.35.
>
> Till,
>
> Can you update the OpenPrinting landing page to provide some common links near the top, including things like:
>
> Reporting Bugs
> Downloading the current version
> Documentation
> Mailing lists
>
> Right now everything is pretty buried and I can't even say whether the link I've provided above is correct for reporting bugs...
>
Done:
https://www.linuxfoundation.org/collaborate/workgroups/openprinting/cups-filters
and linked from appropriate places on the front page
http://www.openprinting.org/
Till
next prev parent reply other threads:[~2013-06-25 22:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 0:14 [Printing-architecture] On the Continued Need for PostScript Workflows James Cloos
2013-06-18 0:45 ` Ira McDonald
2013-06-18 0:55 ` James Cloos
2013-06-18 12:13 ` Michael Sweet
2013-06-18 11:49 ` Michael Sweet
2013-06-19 22:49 ` James Cloos
2013-06-20 13:29 ` Michael Sweet
2013-06-23 22:00 ` James Cloos
2013-06-25 22:05 ` Till Kamppeter [this message]
2013-06-26 0:48 ` Michael Sweet
2013-06-20 14:45 ` Alex Korobkin
2013-06-23 22:05 ` James Cloos
2013-06-19 23:00 ` James Cloos
2013-06-20 1:39 ` Michael Sweet
2013-06-20 6:23 ` James Cloos
2013-06-20 13:53 ` 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=51CA141F.2060609@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=cloos@jhcloos.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.