From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>, Ira McDonald <blueroofmusic@gmail.com>
Cc: Smith Kennedy <smith.kennedy@hp.com>,
"printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] PDF workflow, cupsaddsmb, and Windows clients
Date: Mon, 24 Aug 2015 14:28:16 -0300 [thread overview]
Message-ID: <55DB5430.7000906@gmail.com> (raw)
In-Reply-To: <FB5CC2D9-0026-4C01-B4E3-1AEEF3474674@apple.com>
On 08/24/2015 12:59 PM, Michael Sweet wrote:
> Alex,
>
> The Windows print system is based on Microsoft's XPS format, which is functionally the same as PDF but requiring different tools/filters.
>
> I know Ghostscript and mupdf have XPS support, but I don't know of anyone that has either written the necessary CUPS filters nor the corresponding Windows drivers (which need to comply with some unfortunately strict Microsoft licensing...)
One should check how well Ghostscript performs as XPS
interpreter/converter If it does well, the needed CUPS filter would be a
simple wrapper around Ghostscript, which we would name xpstopdf and
after that we get the usual pdftopdf and then pdfto<whatever the printer
needs>.
Till
next prev parent reply other threads:[~2015-08-24 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 14:56 [Printing-architecture] PDF workflow, cupsaddsmb, and Windows clients Alex Korobkin
2015-08-24 15:36 ` Ira McDonald
2015-08-24 15:59 ` Michael Sweet
2015-08-24 17:28 ` Till Kamppeter [this message]
2015-08-24 18:11 ` Alex Korobkin
2015-08-24 18:47 ` Michael Sweet
2015-08-25 18:44 ` Alex Korobkin
2015-08-25 18:47 ` 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=55DB5430.7000906@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=blueroofmusic@gmail.com \
--cc=msweet@apple.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=smith.kennedy@hp.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.