From: Osamu MIHARA <osamu.mihara@fujixerox.co.jp>
To: printing-sc@freestandards.org, printing-japan@freestandards.org,
printing-architecture@freestandards.org
Subject: [Printing-architecture] OPVP spec RC4
Date: Fri, 15 Jun 2007 08:22:21 +0900 [thread overview]
Message-ID: <4671CDAD.6050409@fujixerox.co.jp> (raw)
In-Reply-To: <789E617C880666438EDEE30C2A3E8D10EF3A@mailsrvnt05.enet.sharplabs.com>
Hi,
Toratani-san has posted the latest update of vector driver API spec. It
is the result of big efforts of OPWG Japan members in these several months.
ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.odt
ftp://ftp.pwg.org/pub/pwg/fsg/vector/pdapi-spec-1.0rc4.pdf
Massive parts are reviewed and improved. The change list is not
attached at the end of the document, due to the time limitation, here is
the main changes since RC2/RC3.
# Toratani-san, we should make a document to describe the changes
# of spec from version 0.2 to 1.0.
- Improve English expressions.
- Rewrite introduction section.
- Raster operation (ROP) functions are removed, since it does not
directly reflect the graphics model of PDF or PostScript. Because the
mapping scheme of superposition of graphical elements from
PDF/PostScript to ROP is ambiguous in the previous spec., and it causes
some artifact problems with vector printer driver implementations. We
review the related functions carefully and confirmed that ROP is not
essential factor for our model and removing it does not cause problems
in the aspect of function and performance.
- Remove unnecessary sentences and paragraphs.
- All descriptions are rewritten to remove ambiguities, using RFC2119
definition (MUST/SHOULD/MAY...).
- Parameters for bitmaps and brushes are reviewed and rearranged.
- Some figures are added for clarification of concepts of functions.
- Etc. etc. etc.....
Please review the spec. and post the feedback to this mailing list.
Thank you!
--
Osamu Mihara // Fuji Xerox
next prev parent reply other threads:[~2007-06-14 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <789E617C880666438EDEE30C2A3E8D10EF3A@mailsrvnt05.enet.sharplabs.com>
2006-10-20 7:29 ` [Printing-architecture] [Printing-sc] OPVP notes Osamu MIHARA
2006-10-20 7:49 ` Osamu MIHARA
2007-06-14 23:22 ` Osamu MIHARA [this message]
2007-06-15 3:51 ` [Printing-architecture] OPVP spec RC4 Ira McDonald
2007-06-15 4:24 ` Osamu MIHARA
2007-06-16 1:11 ` Ira McDonald
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=4671CDAD.6050409@fujixerox.co.jp \
--to=osamu.mihara@fujixerox.co.jp \
--cc=printing-architecture@freestandards.org \
--cc=printing-japan@freestandards.org \
--cc=printing-sc@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.