From: Norm Jacobs <Norm.Jacobs@Sun.COM>
To: printing-japan@freestandards.org,
printing-architecture <printing-architecture@freestandards.org>
Subject: [Printing-architecture] OPVP notes
Date: Mon, 11 Sep 2006 18:58:29 -0500 [thread overview]
Message-ID: <4505F825.9070904@Sun.COM> (raw)
I am resending this due to mail list issues.
Here are some comments on the OPVP specification from our meeting today
-Norm
Page 9
Add FSGPD_CSPACE_DEVICEKRGB to table
Remove any references to "at this time", which talk about the reference
implementation.
Ex. Page 9, lines 7-8
Fix "this will be described later", include the descriptions or page
references.
Ex. jobInfo, page 12
Page 17, specifies Attributes of Job, Document, ...
By not specifying this in a common representation, the render(s) must
know all possible "schemes" available by all possible drivers and
generate
the appropriate format for each driver. This requires the renderers to
maintain proprietary knowledge of all drivers.
There doesn't appear to be coherence with JTAPI, PAPI, ... pick a
property set to represent this data and use it between renderer
and driver. Let the driver translate to/from any internal
representation
that it may need.
reply other threads:[~2006-09-11 23:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4505F825.9070904@Sun.COM \
--to=norm.jacobs@sun.com \
--cc=printing-architecture@freestandards.org \
--cc=printing-japan@freestandards.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.