From: Michael Sweet <mike@easysw.com>
To: Till Kamppeter <till.kamppeter@gmx.net>
Cc: TORATANI Yasumasa <toratani.yasumasa@canon.co.jp>,
printing-architecture <printing-architecture@freestandards.org>,
"desktop_printing@osdl.org" <desktop_printing@osdl.org>
Subject: [Printing-architecture] Re: [Desktop_printing] Deprecate IJS? GhostScript with only "opvp" as output device?
Date: Mon, 15 May 2006 16:45:39 -0400 [thread overview]
Message-ID: <4468E873.7050902@easysw.com> (raw)
In-Reply-To: <4468E039.5000304@gmx.net>
Till Kamppeter wrote:
> ...
> IJS is separate-process-only, raster-only, and not under active
> development any more. There are also only three projects using it:
> HPLIP, Gutenprint, and the Epson-EPL-"L"-series driver. So I think it
> can be deprecated soon and be replaced by the OpenPrinting vector
> interface. Or are there things which IJS provides but OpenPrinting
> vector not.
Both Gutenprint and HPLIP have CUPS native interfaces that are better
suited to pure-raster printing.
> And with the OpenPrinting vector interface one would even be able to
> modularize out all the GhostScript output devices and leave GhostScript
> with "opvp" as the only output device. So also the problem of the X11
> output drivers in the GhostScript implementation of distributions and
> using GhostScript on X-less servers would get nicely solved.
>
> WDYT?
We still need to ensure that the new interface is compatible on all
of the current operating systems; for us that means: AIX, HP-UX, IRIX,
Linux, MacOS X, Solaris, and *BSD.
Also, the X11 problem is already solved by the dynamic module support,
right?
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Document Software http://www.easysw.com
next prev parent reply other threads:[~2006-05-15 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44664EAA.2030508@gmx.net>
[not found] ` <20060515113357.A61C.TORATANI.YASUMASA@canon.co.jp>
2006-05-15 11:19 ` [Printing-architecture] Re: [Desktop_printing] Trying out sample implementation of japanese OpenPrinting efforts TORATANI Yasumasa
[not found] ` <4468D32D.40005@gmx.net>
2006-05-15 19:41 ` [Printing-architecture] Re: [Desktop_printing] " Michael Sweet
[not found] ` <4468EF42.8060502@gmx.net>
2006-05-16 3:22 ` TORATANI Yasumasa
2006-05-16 10:54 ` Michael Sweet
[not found] ` <4467B9FD.6030005@gmx.net>
[not found] ` <20060515183801.A638.TORATANI.YASUMASA@canon.co.jp>
[not found] ` <4468CAFA.9030408@gmx.net>
[not found] ` <4468E039.5000304@gmx.net>
2006-05-15 20:45 ` Michael Sweet [this message]
[not found] ` <4468ECB9.5060507@gmx.net>
2006-05-16 0:16 ` [Printing-architecture] Re: [Desktop_printing] Deprecate IJS? GhostScript with only "opvp" as output device? Michael Sweet
[not found] ` <4468BEE7.80501@gmx.net>
2006-05-16 5:26 ` [Printing-architecture] Re: [Desktop_printing] Re: Trying out sample implementation of japanese OpenPrinting efforts TORATANI Yasumasa
[not found] ` <4469922E.9060301@gmx.net>
2006-05-16 8:56 ` TORATANI Yasumasa
[not found] <54FC073FD525F643838BA51F30EDAD5E029A9887@cacexc07.americas.cpqcorp.net>
[not found] ` <44690EA5.1040106@gmx.net>
2006-05-16 0:24 ` [Printing-architecture] Re: [Desktop_printing] Deprecate IJS? GhostScript with only "opvp" as output device? 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=4468E873.7050902@easysw.com \
--to=mike@easysw.com \
--cc=desktop_printing@osdl.org \
--cc=printing-architecture@freestandards.org \
--cc=till.kamppeter@gmx.net \
--cc=toratani.yasumasa@canon.co.jp \
/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.