From: Till Kamppeter <till.kamppeter@gmail.com>
To: gs-devel@ghostscript.com
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>,
Helge Blischke <HelgeBlischke@web.de>
Subject: [Printing-architecture] Driver for native XPS printers urgently needed
Date: Sun, 11 Oct 2015 19:58:12 +0100 [thread overview]
Message-ID: <561AB144.3080203@gmail.com> (raw)
Hi,
in the segment of high-end laser printers there is a trend to XPS-only
printers and this is a well-known protocol/PDL (Ghostscript/GhostPDL can
be used with it, as both input and output format). Therefore it should
be possible to develop a working generic XPS printer driver soon.
I got aware of this by this thread on the CUPS user mailing list:
Printing to native XPS printers using CUPS
on
http://www.cups.org/pipermail/cups/2015-October/thread.html
or
http://www.cups.org/pipermail/cups/2015-October/027167.html
http://www.cups.org/pipermail/cups/2015-October/027168.html
http://www.cups.org/pipermail/cups/2015-October/027171.html
http://www.cups.org/pipermail/cups/2015-October/027172.html
http://www.cups.org/pipermail/cups/2015-October/027173.html
Ghostscript has already an "xpswrite" output device, but the device is
missing the needed flexibility. Pages are converted to Tiff with 96 dpi
for sending, Only RGB color is available as color space, ...
I want to request as a new feature for GS 9.19 that Ghostscript's
"xpswrite" device gets a real printer driver where you can choose a
resolution, color/bw, ...
Then I would add a gstoxps filter to cups-filters and a PPD for a
"Generic XPS printer" to not need to list such printers as Paperweight
and make it difficult for users to print from Linux on modern printers.
WDYT?
Till
next reply other threads:[~2015-10-11 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 18:58 Till Kamppeter [this message]
[not found] ` <2E3F6574-2E2F-4906-9DCA-FA283EC0E729@web.de>
2015-11-03 21:14 ` [Printing-architecture] Driver for native XPS printers urgently needed 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=561AB144.3080203@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=HelgeBlischke@web.de \
--cc=gs-devel@ghostscript.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.