>>>>> "MS" == Maring, Steve <[EMAIL PROTECTED]> writes:
MS> Looking at the following svg with the SVG Browser from Batik
MS> 1.1rc1 I get the proper 12cm wide display with a circle in the
MS> middle that I expect. When I try to diplay the svg as a PDF
MS> document using the XSL-FO below, I get what looks like the viewBox
MS> dimensions calculated against 72dpi. (i.e. a 1200/72 = 16.67in
MS> instead of 12cm wide) Looking through the code it looked like FOP
MS> was using the Transcoder API to rasterize the image, but the
MS> quality of the circle edges on the resulting PDF is certainly much
MS> better than a raster image at 72dpi!
FOP will directly transcode most graphics primitives to PDF (not
rasterizing them) thus your circle remains a circle. If you use
features that can not be transcoded to PDF - like complicated
transparency, filter effects, etc, then the content is rasterized.
It looks like there may be a bug in FOP for handling the SVG
element from an external Graphic element. Incidentally I have always
use something like the following to import SVG into an fo document.
Sometimes I use the 'use' element sometimes I use 'image' element.
<fo:instream-foreign-object>
<svg:svg width="18cm" height="14cm">
<svg:use transform="scale(0.7)"
xlink:href="CDUPDF.svg#slideshowCover" />
</svg:svg>
</fo:instream-foreign-object>
MS> Can somebody PLEASE explain to me what is going on? I'd like to
MS> diplay an svg like this at the stated width (12cm) in pdf with a
MS> 600dpi resolution quality.
I think that currently FOP always rasterizes things that need
rasterization at 72dpi, but you should ask them to make sure.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
