Hi Christoffer,
The PDF transcoder tends to use 72dpi for 'userspace' units not 96dpi. The best way to fix this would be to provide a width and height with units (like pt) and a viewBox that covers the document area. This will ensure whatever the default user->device transform is that area of userspace is mapped to the same physical area:
<svg width="144pt" height="144pt" viewBox="0 0 144 144">
Will ensure that 1 userspace unit === 1pt.
[EMAIL PROTECTED] wrote:
I have a problem using Batik and FOP together in a reporting application. I use Batik to create a SVG as a DOM-document with some database queries and pass this document to a JSVGCanvas, where it look like want it to (actually the document layout was created to look good there). With the canvas the user has the possibility to change some text, then I use FOP via XSL-FO, i.e. I use Transformer to create a XSL-FO file -which basically only contains the SVG-Code- and then I make use of Driver to render the FO as PDF. When I look at the PDF the position of my charts - which are given without units in the SVG - has changed, while the position of other elements - that have been positioned using metric units - remains the same. I assume that it has something to do with dpi and/or viewbox, but I can't figure it out.
Thanks in advance, Chris
________________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
