From: Till Kamppeter <till.kamppeter@gmail.com>
To: TORATANI Yasumasa <toratani.yasumasa@canon.co.jp>,
Ralph Giles <ralph.giles@artifex.com>,
Raph Levien <raph.levien@gmail.com>
Cc: "Printing-Sc (E-mail)" <printing-sc@freestandards.org>,
Jim Zemlin <jzemlin@freestandards.org>,
printing-japan@lists.freestandards.org,
Ralph Giles <giles@ghostscript.com>,
printing-architecture@lists.freestandards.org,
Ian Murdock <imurdock@imurdock.com>
Subject: Re: [Printing-architecture] [Printing-sc] Application of OpenPrinting as Mentoring Organization for the Google Summer of Code 2007
Date: Mon, 12 Mar 2007 20:14:10 +0000 [thread overview]
Message-ID: <45F5B492.9080808@gmail.com> (raw)
In-Reply-To: <20070312102307.5EB4.TORATANI.YASUMASA@canon.co.jp>
TORATANI Yasumasa wrote:
> Hi,
>
> Some of the Japan side opvp developer know;
> - OPVP interface
> - "opvp" implementation as the Ghostscript driver
> - Some OPVP complianced modularized driver for a few PDLs.
> So, they will be able to make suggestions for OPVP specific issues.
>
> On the other hand, there are few engineers who know the Ghostscript
> inside code in detail, or other type of many Ghostscript built in drivers,
> such as x11*, tiff*, png*, pswrite, pdfwrite, and many drivers for seveal
> printer vendor's PDL., such as dj*, lp*, lex*, pcx*, etc.
>
> If we ask someone to modify these drivers as modularized, I think we
> need volunteers who know these driver's code in dtail.
>
> BTW, do we need to modify all the Ghostscript built-in drivers as
> modularized? If we do not have to, the priority list of the drivers that
> we need to modularize might be helpful for asking someone to be
> volunteers.
>
One thing I thought about was making an interface between OPVP and the
internal API of GhostScript so that it can be compiled with any
GhostScript built-in driver, to convert them all with one effort. I
though t that you could probably mentor such a thing as you have written
the opvp device for GhostScript.
Perhaps we need someone of GhostScript as co-mentor for that. Raph,
Ralph, would you volunteer for that? If so, please tell today, as we
have to submit the application of the Google Summer of Code today (and
supply a Google user names as it is required for the application).
Another thing would be to write new, more flexible and modern drivers
for common languages like PCL-5e, PCL-5c, PCL-XL. This would be a new
project idea to post on our project ideas Wiki.
Till
next prev parent reply other threads:[~2007-03-12 20:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 19:53 [Printing-architecture] Application of OpenPrinting as Mentoring Organization for the Google Summer of Code 2007 Till Kamppeter
2007-03-09 19:53 ` McDonald, Ira
2007-03-09 21:25 ` Till Kamppeter
2007-03-09 21:33 ` Till Kamppeter
2007-03-10 19:30 ` McDonald, Ira
2007-03-10 19:41 ` Till Kamppeter
2007-03-11 0:15 ` Till Kamppeter
2007-03-11 0:57 ` Till Kamppeter
2007-03-12 3:28 ` [Printing-architecture] [Printing-sc] " TORATANI Yasumasa
2007-03-12 20:14 ` Till Kamppeter [this message]
[not found] ` <20070312210511.GA30314@ghostscript.com>
2007-03-12 21:12 ` Till Kamppeter
2007-03-11 1:33 ` [Printing-architecture] " Till Kamppeter
2007-03-12 22:31 ` Till Kamppeter
2007-03-12 22:54 ` [Printing-architecture] [Printing-sc] " TORATANI Yasumasa
2007-03-12 23:01 ` Till Kamppeter
2007-03-12 23:38 ` Norm Jacobs
2007-03-13 0:23 ` [Printing-architecture] Application of OpenPrinting as Mentoring Organization for the Google Summer of Code 2007 - Final application Till Kamppeter
2007-03-13 9:23 ` [Printing-architecture] Application of OpenPrinting at Google Summer of Code NOT accepted 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=45F5B492.9080808@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=giles@ghostscript.com \
--cc=imurdock@imurdock.com \
--cc=jzemlin@freestandards.org \
--cc=printing-architecture@lists.freestandards.org \
--cc=printing-japan@lists.freestandards.org \
--cc=printing-sc@freestandards.org \
--cc=ralph.giles@artifex.com \
--cc=raph.levien@gmail.com \
--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.