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 Rich Quist <Ri...@mathworks.com> on 2007/08/22 19:55:40 UTC

Invalid postscript generated with PSTranscoder in batik 1.7beta1

I'm seeing multiple instances of "page setup" blocks within the
postscript generated using PSTranscoder in batik 1.7beta1. Attempting to
view the postscript file using GSView 4.8 causes multiple DSC warnings
to appear, one for each of the extra page setup blocks, saying that the
%%Page: 1 1  l  ine is incorrect. The problem blocks look like: 
 
   %%Page: 1 1
   %%PageBoundingBox: 0 0 0 0
   %%BeginPageSetup
   <<
   /PageSize [0 0]
   /ImagingBBox null
   >> setpagedevice
   FOPFonts begin
   [1 0 0 -1 0 0] concat
   %%EndPageSetup
 
The same application when run with Batik 1.6 generates valid postscript.

 
The java application prints into an SVGGraphics2D instance to generate
SVG, and then uses a StringReader on the generated SVG to create a
TranscoderInput instance used by the transcode function of the
PSTrancoder instance.
 
Any thoughts?
 
Thanks in advance