|
|
Posted by dorayme on 12/21/07 03:33
In article <300b8$476b2496$40cba7ad$2850@NAXS.COM>,
"Jonathan N. Little" <lws4art@centralva.net> wrote:
> dorayme wrote:
> > In article <e0fb8$476afbf6$40cba7ad$6753@NAXS.COM>,
> > "Jonathan N. Little" <lws4art@centralva.net> wrote:
> >
> >> dorayme wrote:
> >
> >>>>> At least a .png file can often contain vector objects. I always
> >>>>> keep master files of some things I do in Fireworks in the native
> >>>>> saved format with layers, text and other vector objects. I export
> >>>>> them for the web into various formats including png. What is
> >>>>> exported are also .png files. These latter are not vector
> >>>>> carriers though.
> >
> >> I think you will find that FW rasterizes the vector object or is not a
> >> standard PNG format like my CorelDraw can have vector and bitmap
> >> composite file. The true test if FW truly embeds the object as vector
> >> then you should be able to extract the object and the result should be
> >> the original vector. But I can say with fair certainty that any PNG that
> >> is displays in a web browser is raster only.
> >
> >
> > I thought I was sort of saying something similar... put it this
> > way, in my originally made FW files that are saved (*not
> > exported* to international standard formats), the squares and
> > lines and text and other things I have made (as one does in
> > Illustrator) seem to retain their vector qualities.
> >
> > I now know that they also appear the same whether exported or not
> > in browsers (at least in Safari, FF, iCab, Opera and MacIE):
> >
> > http://netweaver.com.au/alt/png/png.html
> >
> > The pie.png was exported from pieNativeFW.png
> >
>
> It is quite obvious, raster only in both cases. Vector on enlargement
> would have not anti-aliasing blur. If I have a composite CDR I can
> select the vector part and save as any pure vector format with no
> distortion, SVG, EPS, AI, DWG, CDR...
Nothing is obvious to me. Have not got that kind of mind.
Everything is always complicated. But hang on to your shirt
Jonathan, I am not really disputing anything you say, just making
one thing clear. The original file - same one that I ftp'd up to
the server has vector in it, what the browser does with it is
something else again, it does not carry the vector info through,
that is clear but it does not act back on the poor innocent file
sitting on the server either to make it lose its vector
properties. It is just that the browser is blind to some of the
info in the file. The FW app is not.
http://netweaver.com.au/alt/png/png.html
I grabbed the original file called pieNativeFW.png, the very one
that I loaded to the server for above and reopened in FW app and
copied and pasted the object into a new file with a bigger
canvas. And just dragged the object bigger. It retained its
sharpness. And you can see it at its natural size as last item at
above.
I have never doubted that it is no longer a vector object on the
browser or when you get it. FW is an interesting app that has
objects that are not altogether one thing or another.
All the best to you.
--
dorayme
Navigation:
[Reply to this message]
|