You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-users@xmlgraphics.apache.org by th...@kodak.com on 2006/01/03 20:55:15 UTC
Re: Problem when printing SVG
André Ávila <as...@nextech.com.br> wrote on 12/30/2005 09:27:37 AM:
> > > TranscoderInput ti = new
TranscoderInput(svgCanvas.getSVGDocument());
> >
> > This is bad, this will break your SVGCanvas display if your
> > document is in any way dynamic.
>
> I don't plan to support dynamic documents at this time, so this should
not
> be a problem. However I'd like to know what's the alternative way to do
it
> as to leave that possibility opened. Could you point me any directions?
You would either have to clone the document or borrow code from
the transcoders and use the GVT tree from the Canvas directly.
> I didn't have a good impression of PDFTranscoder. The output looks
great,
> but it seems to increase the memory usage of Batik by an unacceptable
> amount. It actually looks like there's a leak, since the used memory
keeps
> rising all the time. When I removed it from my distribution, memory
usage
> became much more sensible. Do other people have the same experience?
Well if you can reproduce the memory leak I'd be interested in looking
at it...
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org