|
|
All,
Forgive my ignorance of PDF but I would like to ask a couple of
high-level questions about the transcoder...
The SVG2PDF transcoder that is included with Batik, this is actually
produced by the FOP project right?
In what sense is the SVG 'transcoded' into PDF? Is an SVG <circle>
element converted into a relevant PDF element (I don't think PDF is
XML)? Or is the SVG image placed as a rasterized bitmap in the PDF? If
so what format (PNG/TIFF)? What happens to script elements? Is the FOP
transcoder essentially for static SVG images.
The reason I am asking is because I recently ran Kevin Lindsays'
svg2pdf.pl script. What it seems to me is that the SVG has been inserted
as some low-level object, much like using the <object>/<embed> tag in
HTML. When you view the document in Reader then the SVG Viewer renders
the SVG and still retains all its interactivity etc. Is this just a
totally Adobe solution, or could the same thing be achieved by creating
the PDF through the FOP transcoder?
Once again sorry for my PDF ignorance. But I have a use case where I
would like to embed a dynamic SVG graph into a predominantly textual PDF
and still retain the ability to "drill-down" through the data.
This whole thing is a bit confusing anyway, I mean how does printing
relate to dynamic documents, when print is a static medium?
TIA
Jamie Browning
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xxxxxxxxxxxxxx
For additional commands, e-mail: batik-users-help@xxxxxxxxxxxxxx
|
|