Hi Antoine,
Now that I am no longer with Adobe, I feel more able to express certain
opinions. Regarding SVG Print:
1) Yes indeed, try to partner with how PDF/Mars is using SVG. As you
probably know, PDF is very, very big in the world of printing. An
initiative around SVG for print workflows that was incompatible with
PDF/Mars probably would not be taken seriously by the major players in the
print industry. The print industry already has to support PDF because it
has so much industry momentum (and addresses most of their needs). It would
be much easier for them to add support for the XML version of PDF, with SVG
inside, then take on a whole new "SVG Print" thing. (Especially since MS is
very aggressively pushing the MS-controlled XML Paper Specification into
the print industry.) Thus, the standards world should try to make the page
images for "SVG Print" and the page images for PDF/Mars be one and the
same.
2) But beyond that, given that PDF/Mars is based on open standards,
including SVG, why is there an industry requirement for "SVG Print" as a
separate thing at all? The only viable reason for "SVG Print" that I can
see would be if Adobe decides to keep all of Mars as an Adobe-controlled
thing, which would be contrary to the W3C goals of promoting truly open
technologies (i.e., not controlled by a single vendor). But if Adobe hands
off the SVG parts of Mars to a legitimate standards process, such as the
SVG WG or AIIM (which manages the PDF/A ISO standard), then instead of
inventing a different "SVG Print" thing, the SVG WG should work with the
community to define a *single* industry-wide definition of how to use SVG
within print workflows.
Jon
Jon Ferraiolo <[EMAIL PROTECTED]>
Web Architect, Emerging Technologies
IBM, Menlo Park, CA
Mobile: +1-650-926-5865
Antoine Quint
<[EMAIL PROTECTED]
m> To
Sent by: [email protected]
[EMAIL PROTECTED] cc
hoogroups.com
Subject
Re: [svg-developers] Mars and svg
12/12/2006 08:47 specifications
AM
Please respond to
[EMAIL PROTECTED]
hoogroups.com
On 12 déc. 2006, at 06:08, Leonard Rosenthol wrote:
> There are a few places that we had to extend SVG to support
> features in PDF,
> including in the areas of colorspaces, transparency and prepress
> functionality. All of our "extensions" are documented and should
> also be
> namespaced.
Good to hear Leonard. Are there any plans to sync with W3C and the
SVG Print effort to make sure that some of these extensions could be
considered for standardization?
Antoine
--
Blog — http://the.fuchsia-design.com
-----
To unsubscribe send a message to:
[EMAIL PROTECTED]
-or-
visit http://groups.yahoo.com/group/svg-developers and click "edit my
membership"
----
Yahoo! Groups Links
[Non-text portions of this message have been removed]
-----
To unsubscribe send a message to: [EMAIL PROTECTED]
-or-
visit http://groups.yahoo.com/group/svg-developers and click "edit my
membership"
----
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/svg-developers/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/svg-developers/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
