RE: XML from Visio and the validity of a $3 bill

[Dov Isaacs <isaacs@xxxxxxxxx>]

Again, there are really a bunch of issues here:

(1) Currently, SVG import into FrameMaker loses its scalability
and vector properties, i.e. it is lossy. This could change in
the future but currently your PDF and printed results could be
rather dismal from imported SVG.

(2) SVG import into other main-line publishing programs and
word processors is even spottier.

(3) Ability to print SVG for publishing purposes is very
limited.

There is no question that SVG currently has some interesting
applications, but for typical print and PDF publishing workflows,
it does not currently have the attributes that allow it to
be anything like a universal format.

        - Dov

At 2/3/2003 09:44 AM, Sean Brierley wrote:
>SVG support in FrameMaker would make it a bunch easier
>for me to get my output to HTML. That is, I could use
>SVG for all of my vector output--print and online.
>
>As it is,  I gotta rasterize or maintain different
>graphics for print and online.
>
>Cheers,
>
>Sean
>
>
>--- eric.dunn@ca.transport.bombardier.com wrote:
>> 
>> 
>> <<The "trouble" is that a "all-SVG-native workflow" > is of very
>> dubious utility AT THIS TIME for publishing
>> workflows.
>> 
>>         - Dov>>
>> 
>> Don't know about anyone else but the utility seems
>> quite obvious to me. I
>> certainly wouldn't qualify it as dubious. If you're
>> going to use any graphic
>> format, it's best that only one format be required
>> for the entire process.


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **