xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric SCHAEFFER" <eschaef...@posterconseil.com>
Subject Re: org.apache.fop.render.awt.AWTRenderer, again
Date Fri, 06 Oct 2000 13:48:54 GMT

----- Original Message -----
From: "Keiron Liddle" <keiron@aftexsw.com>
To: <fop-dev@xml.apache.org>
Sent: Friday, October 06, 2000 1:24 PM
Subject: Re: org.apache.fop.render.awt.AWTRenderer, again


> > About SVG and other vector formats - I would leave the rasterizing to
the
> > particular graphic engine. First of all, the most important property of
SVG
> > is that it is Scalable. You have to know the output resolution in the
moment
> > you display it, not before. In your approach, you would have to tell
> > FopImage the resolution you want every time you display the image,
otherwise
> > you would loose the advantages of SVG. We cannot abstract everything as
a
> > bitmap. Those are all graphical objects though, and can be rendered,
that's
> > true.
>
> Just thought I might point out that there already is an SVGImage thing
that can
> load an external svg image and let it be rendered. I think I have only put
the
> code so that it renders for an image inside an inline svg document.
> It shouldn't take much to add it into the pdf renderer external image and
the
> awt renderer.
>

No problem. I saw the SVGImage class when you added it. You can modify the
renderers if you want, but as it has been said, the vector image format was
a bad example.

Eric.



Mime
View raw message